Re: Freeze

[Chris <chris@ormond.unimelb.edu.au>]

On Mon, Nov 08, 1999 at 03:44:20AM -0500, Branden Robinson wrote:
> On Sat, Nov 06, 1999 at 10:20:56AM +1100, Chris Leishman wrote:
> > This is a valid point, but there is still no reason not to include the current
> > incoming directory.  Even if something cant be fixed before we want to
> > release, then we can always backdate the package - its been done before (IIRC
> > slink had to backdate X during its freeze to the last working version before 
> > release).
> 
> Huh?  What are you talking about?
> 
> I released XFree86 3.3.2.3a-2 right before slink froze last October.  It
> saw many revisions before settling on 3.3.2.3a-11 for the release in March.
> 
> While slink was frozen, XFree86 3.3.3 (and then 3.3.3.1) came out upstream.
> I did not package a version of XFree86 newer than 3.3.2.3 until after slink
> was released.
> 
> I'm not sure what you mean by "backdating", but it doesn't sound like
> that's what I did.  If you're saying I meant to ship 3.3.3 or 3.3.3.1 with
> slink but reverted to 3.3.2.3a because of problems, you're wrong.


Hmm..my memory is probably failing me :)  (I might have actually been for 
the freeze before slink, and it may not have even been X....my brain isn't
functioning too well ATM - too much macroeconomic study...)

What I meant be backdating was that some stuff was put in before we froze,
then when it became apparant that making it stable was going to be really
hard, we went back to a previous maintainer version that did work ok - rather
than hold things up.

So in this situation - we add the stuff currently in Incoming, and if it
proves to cause too many headaches (such that it will hold up the release),
then we go back to a version before the freeze date that didn't exhibit those
problems (or if its a new package - kick it out).

*shrug*

Chris



-- 
----------------------------------------------------------------------
            Linux, because I'd like to *get there* today
----------------------------------------------------------------------
Reply with subject 'request key' for GPG public key.  KeyID 0xB4E24219