An issues is usually a bug report or similar, not a feature discussion etc. Depending on the outcome of the discussion you then create an issue or a PR/feature branch.
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.
Issues are supposed to be like tickets. They come from issue tracking systems. They have a clearly defined life cycle of opening and closing them.
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.
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.
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.
An issues is usually a bug report or similar, not a feature discussion etc. Depending on the outcome of the discussion you then create an issue or a PR/feature branch.
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.
You don’t seem to be a developer :)
Issues are supposed to be like tickets. They come from issue tracking systems. They have a clearly defined life cycle of opening and closing them.
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 have been a developer for over 10 years now.
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.
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.
@musicmatze @poVoq
The Github Discusions is relatively new feature they added. I did not see many projects yet that are very actively using it.