Agreed, "closed" is the right state once a fix is committed. I think what I'm missing is a "pending release" indicator that makes it obvious to a user that an issue they've encountered is a bug that's been fixed and awaiting release, rather than a new bug that looks similar to an old one.
Perhaps using milestone tags on issues would fill that gap? On Mon, 23 Nov 2020 at 10:10, Philipp Mueller via Hydrogen-devel < hydrogen-devel@lists.sourceforge.net> wrote: > How would you suggest to handle issues instead? As far as I can see the > current policy is to close an issue as soon as it is fixed in Master. > This way all developers and contributors can tell it already has been > fixed. > > All the best, > > Phil > > On 22.11.20 12:21, Colin McEwan wrote: > > which raises another question about when to close issues! > > > _______________________________________________ > Hydrogen-devel mailing list > Hydrogen-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/hydrogen-devel > -- C.
_______________________________________________ Hydrogen-devel mailing list Hydrogen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
