Re: How freeze breakage works in general ("time to teach the newbie")



On Mon, 2005-02-07 at 17:58 -0700, Elijah Newren wrote:
> On Mon, 7 Feb 2005 19:25:32 -0500, Luis Villa <luis villa gmail com> wrote:
> > On Tue, 08 Feb 2005 01:20:18 +0100, Murray Cumming <murrayc murrayc com> wrote:
> > > On Mon, 2005-02-07 at 19:15 -0500, Luis Villa wrote:
> > > > Murray, is there anyone else appropriate on the team right now to
> > > > approve this?
> > >
> > > Some one else who has designed an API in a high-level language, I
> > > suppose.
> > 
> > Right, but does anyone that you know of match that criteria? i can't
> > think of anyone, which is why i ask you :)
> 
> Cool, a chance to jump in with some questions and learn.  Or at least
> a chance to make a complete fool of myself as the newbie.  :-)  This
> thread comes across as very odd to me.  Now, there aren't any
> guidelines anywhere on how patch approval for freeze breaks work other
> than "you need two approvals from the release team".  So, I tried to
> watch for a while and figure out how things worked.  Then I eventually
> jumped in and made a couple comments/choices on ones that looked
> fairly safe, figuring that if I really blew things I could learn and
> hopefully not a lot of harm would be done.  Okay, so with this
> background...
> 
> This thread makes it appear that the release team approvals are
> technical reviews.

It's more like due diligence. If they can answer the standard questions
then the request should probably be approved. If they haven't considered
them then it shouldn't. That covers most requests.

Other than that we do our best, and try to avoid making technical
decisions.

> aren't most if not all members
> of the release-team qualified to give a second approval (or partial
> approval considering the additions that look less important)? 

When I'm not sure, I wait a day for someone smarter to reply. When
nobody has replied, I guess that my opinion is better than nothing.

-- 
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]