On Sun, Aug 14, 2016 at 11:35:58PM +0200, Kristian Fiskerstrand wrote: > During the latest Council meeting it was determined to set up a new > Working Group to come up with recommendations for improving the state of > the stable tree at a later Council meeting.
Sign me up! > > Some initial items it was suggested the WG look into is > * The b.g.o workflow, bugs should not be considered fixed until the > fix has reached the stable tree. Today the InVCS keyword exists for > this purpose, but it is used to varying degree amongst developers. > Will a workflow change to introduce a new status, e.g RESOLVED > NeedsStable (name for illustration purpose only) incentivize > developers to not close bugs before it is fixed? In selinux we do: UNCONFIRMED/CONFIRMED == not fixed yet IN_PROGRESS == we've put the fix in the git repo RESO/TESTREQ == new release and in ~arch RESO/FIXED == the fix is stable now Both Swift and I use stable so having things stabilized is important and we dont close bugs till they are actually stable lest we forget later. Our saved search for selinux bugs lists all bugs that are not RESO/FIXED or VERIFIED, so RESO/TESTREQ still shows up. -- Jason > * Are there ways to reduce the stabilization lag of packages > - looking into the effectiveness of ALLARCHES and its use > - possibility for maintainer to stabilize packages themselves for > architectures they have access to (including whether there might > be a need for changes to gentoo infrastructure to facilitate > this) > - Tinderboxing / Automatic tools build test packages and reverse > dependencies in order to assist in stabilization Toralf runs one. Zorry is working on an auto tinderbox too. -- Jason > Other suggestions are up to the WG to come up with and write up a final > report to the council with the summary of these discussions. > > I've volunteered to chair such as working group. If you want to > participate in it please respond to this thread. Additionally I've set > up #gentoo-wg-stable as a place of coordination. > > -- > Kristian Fiskerstrand > OpenPGP certificate reachable at hkp://pool.sks-keyservers.net > fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 >
