On Thu, 16 Jun 2016 15:14:44 +0200 Kristian Fiskerstrand <k...@gentoo.org> wrote:
> > What I'd like to introduce instead is a new STABILIZED state. It > > would -- like VERIFIED now -- be only available for bugs already > > RESOLVED, and it could be used to signify that the fix has made it > > into stable. > > > > While this wouldn't be really obligatory, it would be meaningful for > > trackers that need to ensure that fixes in packages have made it to > > stable -- like the functions.sh use tracker. > > The description of InVCS keyword in bugzilla is: > InVCS Fix has been added to a VCS(either CVS, SVN, Git, ...) > repository. Will be closed when fixes are applied to a stable level > package. > > A bug isn't resolved until it is fixed in a stable package (for > packages ever in stable to begin with), but InVCS keyword can be used > by developers to filter out the bugs for issues to work with. I > oppose a change to that behavior, although I would like to see it > being used more consistently as it seems quite a few developers are > neglecting the stable tree. I currently set InVCS for pending-stable fixes in conjunction with the IN_PROGRESS state. I would like to keep InVCS at least. -- James Le Cuirot (chewi) Gentoo Linux Developer