New bug tracker status no-release?

[Bernhard Reiter]

Am Montag, 9. Mai 2016 20:52:07 schrieb Werner Koch:
> with more people actively closing bugs I too often look at bugs set to
> "testing" which are kept at that status to remind about about a missing
> release.  Thus I ponder with the idea to add a new status "no-release"
> for such cases.  This would also allow to decide whether it makes sense
> to do a new maintenance release of 1.4 or 2.0.
>
> Any opinions against this or a better term for such a status?

"no-release" could be missunderstood as not being scheduled
for a release. So what about

"release-ready"
"waiting-for-release"



-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20160510/3e82e06c/attachment.sig>