forgefriends. forges united. coders befriend.
  • musicmatze
    2•2 years ago

    it seems to make sense to separate issue tracking from general development discussions.

    How? Isn’t general development discussion actually an issue? If a discussion comes to a point and gets implemented, it is essentially an issue,…

    • @poVoq
      2•1 year ago

      deleted by creator

      • musicmatze
        1•2 years ago

        An issues is usually a bug report or similar

        Usually? And when it is not?

        See, I don’t see any reasons why a feature discussion shouldn’t be an issue. “Issue” is just a fancy name for “Discussion”, isn’t it? So basically, these are all some kind of linear or tree-style discussion of some specific topic. There’s nothing more to it, is there?

        So I don’t see why they should be seperate at all. Differentiation can be done via tags, labels, … or whatever you’d like to call it. That’s there already of course.

        • @poVoq
          1•1 year ago

          deleted by creator

          • musicmatze
            1•2 years ago

            You don’t seem to be a developer :)

            I have been a developer for over 10 years now.

            If you mix them with general discussions your entire project cycle management system breaks as you can’t have clear milestones etc. with forever open “issues” that are not issues but discussions.

            I don’t see why an issue must be assigned to a milestone, so I don’t see how an issue can break any lifecycle.

            • smallcirclesOPM
              1•2 years ago

              How an issue is used in a development project is “it depends”. Whatever the chosen and preferred method of the maintainers is. If you really want a concise backlog with concrete stuff, and no “pie in the sky” musings on future major extensions, then Discussion section can be very handy. If you don’t use discussions, you may end in a situation where off-topic’ish issues sit in the backlog like forever, and pile up.