Fw: Re: Proposed change to development Process was Fw: [Bug 650598] Cannot Enter Nth Day of Month Scheduled Transactions

Colin Law clanlaw at googlemail.com
Thu Feb 7 11:12:01 EST 2013


On 7 February 2013 15:41, David Carlson <carlson.dl at sbcglobal.net> wrote:
> Then is there some other way to show the bug unresolved (because it has not been released) but the code is in the queue?

Could one use a Status of Resolved to mean that the fix has been
committed but not yet released, and then close the bug when it is
released?

Colin

>
> David C
>
> --- On Thu, 2/7/13, John Ralls <jralls at ceridwen.us> wrote:
>
> From: John Ralls <jralls at 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.dl at sbcglobal.net>
> Cc: "gnucash-devel" <gnucash-devel at gnucash.org>, david.carlson.417 at gmail.com
> Date: Thursday, February 7, 2013, 9:35 AM
>
>
> On Feb 7, 2013, at 7:21 AM, David Carlson <carlson.dl at 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 at gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel


More information about the gnucash-devel mailing list