After looking at the status choices, how about creating a bogus person named something like "BugReleaseAgent" to assign the bug report to when the code is written, then leaving it in his hands until it reaches the actual program release?
Just a suggestion. --- On Thu, 2/7/13, David Carlson <carlson...@sbcglobal.net> wrote: From: David Carlson <carlson...@sbcglobal.net> Subject: Fw: Re: Proposed change to development Process was Fw: [Bug 650598] Cannot Enter Nth Day of Month Scheduled Transactions To: "gnucash-devel" <gnucash-devel@gnucash.org> Date: Thursday, February 7, 2013, 9:41 AM Then is there some other way to show the bug unresolved (because it has not been released) but the code is in the queue? David C --- On Thu, 2/7/13, John Ralls <jra...@ceridwen.us> wrote: From: John Ralls <jra...@ceridwen.us> Subject: Re: Proposed change to development Process was Fw: [Bug 650598] Cannot Enter Nth Day of Month Scheduled Transactions To: "David Carlson" <carlson...@sbcglobal.net> Cc: "gnucash-devel" <gnucash-devel@gnucash.org>, david.carlson....@gmail.com Date: Thursday, February 7, 2013, 9:35 AM On Feb 7, 2013, at 7:21 AM, David Carlson <carlson...@sbcglobal.net> wrote: > As I requested in this closed bug, which is not in the current program > release and may not be in the current release for many more months, how about > adding a status "Awaiting next Program Release" so the bug can be found in a > search for unresolved bugs? > > This should reduce duplicate bug reports. > It might, but we don't control bugzilla, gnome.org's "Bug Squad" [1] does. We don't have the privs to modify the workflow. Regards, John Ralls [1] https://live.gnome.org/Bugsquad/ _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list gnucash-devel@gnucash.org https://lists.gnucash.org/mailman/listinfo/gnucash-devel
