Skip to Content.
Sympa Menu

sm-discuss - Re: [SM-Discuss] process for getting bugfixes and security updates into stable grimoire

sm-discuss AT lists.ibiblio.org

Subject: Public SourceMage Discussion List

List archive

Chronological Thread  
  • From: Arwed von Merkatz <v.merkatz AT gmx.net>
  • To: sm-discuss AT lists.ibiblio.org
  • Subject: Re: [SM-Discuss] process for getting bugfixes and security updates into stable grimoire
  • Date: Fri, 5 May 2006 22:47:39 +0200

On Fri, May 05, 2006 at 01:03:43PM -0700, Andrew wrote:
> On Fri, May 05, 2006 at 08:33:25PM +0200, Arwed von Merkatz wrote:
> > Hi everyone,
> >
> > as the process of how to get fixes into stable(-rc) grimoire apparently
> > isn't clear to everyone, here's how I think the process should be.
> > This is mostly a draft to get comments, but we definitely need some
> > policy like this to ensure stable is as stable as we can get it.
> > This isn't really anything new, just a clarification of how the process
> > is supposed to work, extending it to security updates.
> >
> > - a new flag "integrate to stable-rc" will get added to bugzilla
> > - bugs get filed against the highest grimoire in the stability range
> > that they apply to, i.e. first to stable, then stable-rc, then test
> > - bugs get fixed _only_ in test grimoire as usual
> > - once they're fixed in test, the "fixed in lesser branch" flag is set
> > to "+", and the "integrate to $BRANCH" flags are set to "?" for the
> > branches they apply to
> > - one of the gatekeepers (currently Eric Sandall, Seth Woolley and
> > myself) approves or denies the request(s) for integration, if it's
> > denied, an explanation of the reasons is added to the bug
>
> I think there needs to be a clarification that the person requesting
> the integration and the gatekeeper be different people. So a gatekeeper
> can't approve their own request.

Thanks, I forgot that when transcribing from my irc notes.

--
Arwed v. Merkatz Source Mage GNU/Linux developer
http://www.sourcemage.org




Archive powered by MHonArc 2.6.24.

Top of Page