Gentoo Archives: gentoo-dev

From: Chris Reffett <creffett@g.o>
To: gentoo-dev@l.g.o
Cc: qa@g.o
Subject: Re: [gentoo-dev] January 2014 QA Policy Updates
Date: Thu, 30 Jan 2014 21:32:52
Message-Id: 52EAC4E6.4070906@gentoo.org
On 01/30/2014 03:10 PM, William Hubbs wrote:
> On Thu, Jan 30, 2014 at 12:47:01AM -0500, Chris Reffett wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Hello all, >> The new QA team has completed its first meeting, and so I would like >> to announce policy changes agreed upon during the meeting which are >> relevant to the developer community. In the future, when a meeting >> results in changed or amended policy, we will notify the community via >> - -dev and -dev-announce, so there will probably be a summary email like >> this coming out about once a month. Changes to policy from this meeting: >> >> - -USE-controlled optional RDEPENDs policy clarified to say that those >> dependencies are not allowed, but QA will grant exceptions for certain >> circumstances (such as a package not working unless one of a set of >> optional deps is installed) >> >> - -The QA team policymaking workflow will look like the following: >> * User/dev/team member brings us an issue >> * Team investigates >> * Team discusses at the next meeting >> ** If the person is violating policy, we inform them of that and >> request that they stop violating policy >> ** If the existing policy is unclear, we update it >> ** If there is no existing policy, make one >> If we think a developer's actions are causing problems, we may ask >> them to stop/undo pending discussion by the QA team at the next meeting. >> >> - -Rules for the QA team editing peoples' packages: >> *For trivial fixes, such as repoman errors, we fix the issue and send >> the developer a friendly reminder >> *For large but non-critical fixes, we open a bug, wait 2 weeks, and if >> it is not fixed within that time frame we make the change. >> *For critical fixes, such as a problem that breaks the tree or a >> package, we fix the issue and send the developer a notice about our change >> >> - -The QA team will communicate changes to policy via emails to >> gentoo-dev and gentoo-dev-announce and by updating the QA policy page >> on the Gentoo Wiki. >> >> For anyone interested, the summary of the meeting can be found at >> https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Meeting_Summaries >> and the current set of QA policies can be found at >> https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Policies. If >> you have any questions or concerns about these policies, feel free to >> discuss them with us in #gentoo-qa or by emailing qa@g.o. > > I have one. > > The way I read that email, we are saying that our only policies are on > the wiki. > > Is that right, or is the DevManual stil relevant? > > If it is, I would suggest that on the wiki we make it clear that our > technical policies are all in the devmanual. Along that line, I would > suggest moving the stabilization policy to the devmanual. I'll look for > a place for a patch. > > William >
That's my mistake, the devmanual is still relevant. My idea is to use the wiki page for smaller or more specific items which probably don't go in the devmanual (for example, policy which is about specific packages or USE flags, or policies which just affect the QA team). Stabilization should go to the devmanual, then. Chris Reffett

Attachments

File name MIME type
signature.asc application/pgp-signature