On Fri, Jun 17, 2016 at 9:52 AM, Michał Górny <mgo...@gentoo.org> wrote: > On Thu, 16 Jun 2016 15:14:44 +0200 > Kristian Fiskerstrand <k...@gentoo.org> wrote: > >> On 06/16/2016 03:02 PM, Michał Górny wrote: >> > Hello, everyone. >> > >> >> >> >> > >> > 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. > > How would that work for Portage? There 'InVCS' indicates that the fix > has landed in git (i.e. in -9999, not yet released). >
That could actually be generalized. I could see many types of bugs where the issue is with upstream, and we might want to track the progress as upstream implements a fix, releases it, and then it is stabilized on Gentoo. So, maybe we need another state to track in upstream's VCS vs the Gentoo repo. Another approach would be to distinguish between portage as a Gentoo-hosted upstream, and portage as a package in the Gentoo repo. The same could apply to any Gentoo-hosted project. -- Rich
