Gentoo Archives: gentoo-dev

From: james <garftd@×××××××.net>
To: gentoo-dev@l.g.o
Subject: Re: #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree)
Date: Mon, 15 Aug 2016 12:22:13
In Reply to: Re: #wg-stable: Reservations about a "STABLE" & "NeedsStable" bugzilla keywords (re: [gentoo-dev] New Working Group established to evaluate the stable tree) by Kent Fredric
1 On 08/15/2016 12:37 AM, Kent Fredric wrote:
2 > On Mon, 15 Aug 2016 16:29:43 +1200
3 > Kent Fredric <kentnl@g.o> wrote:
4 >
5 >>> * The b.g.o workflow, bugs should not be considered fixed until the
6 >>> fix has reached the stable tree. Today the InVCS keyword exists for
7 >>> this purpose, but it is used to varying degree amongst developers.
8 >>> Will a workflow change to introduce a new status, e.g RESOLVED
9 >>> NeedsStable (name for illustration purpose only) incentivize
10 >>> developers to not close bugs before it is fixed?
11 >
12 > Also, if its already stable, the fix may go directly into stable.
13 >
14 > Does this need to also spend time in "NeedsStable" state?
15 >
16 > I'd assume not. But this is going to need clear definitions and lots of usecase
17 > writeups.
18 >
20 As a user, on the pathway to dev level comprehension and gentoo-skills,
21 *documentation is king*. So put what is universal (on the processes)
22 into a master document and the slight project variations, is a
23 subordinate "group" or "project" document, so that flexibility is
24 afforded to the collectives. Some devs do not like this level of
25 organization, but, it is for the good of the entire gentoo community, so
26 when one wants/needs to know, they can just read about it. Perhaps those
27 in proxy-maint in a given project, could be the front line maintainers
28 of these subordinate documents, as they are the ones most sensitive to
29 the accuracy needs for these documents.
32 This effort would drastically 'settle the peace' because devs, for what
33 ever reason, that need to attend to codes in areas they normally do not
34 work on, can quickly refresh the main points of culture and guidance
35 on a given project and thus function more cohesively as an extended if
36 not transient team member. I.E. less ruffled feathers, imho. These
37 efforts will greatly facility the ability of gentoo to expand the number
38 of dev, working in a productive manner, by avoiding conflict and yet
39 letting the smaller collectives tune the rules, to their liking and
40 under the tutelage of the Lead(s) on that (project) collective. This
41 also empowers folks to 'take ownership' which leads to better quality
42 and increases in productivity, imho.
45 The ability for other members of the gentoo community to read and learn,
46 at their own pace:: *priceless*.
49 ymmv,
50 James