Security release needed

J. Paul Reed preed at
Mon Jan 3 19:21:36 UTC 2005

On 03 Jan 2005 at 19:08:36, Gervase Markham arranged the bits on my disk to say:

> David Miller wrote:
> >Gervase Markham wrote:
> >
> >>2.16.8 is ready to go - there are two security patches to check in.
> >>2.18.0 has the blocker list we all know about. See Jake's weblog.
> >>2.19.2 could go at any time, really - it's just a development release.
> >
> >There will be no 2.19.2.  We're releasing 2.20rc1 concurrently with 2.18 
> >final, at which point we branch.
> In an ideal world, we would definitely do that. However, given that the 
> bug in question is public knowledge, we need to get a security release 
> out ASAP, as in "today or tomorrow". 

You *JUST* said "2.19.2 could go at any time, really - it's just a
development release."

And now, it has to go out "today or tomorrow?"

Which is it?

And if it is "just a development release," why does it have to go out
"today or tomorrow?"

J. Paul Reed -- 0xDF8708F8 || preed at ||
Math, my dear boy, is nothing more than the lesbian sister of biology.
                                            -- Peter Griffin, Family Guy

I use PGP; you should use PGP too... if only to piss off John Ashcroft

More information about the developers mailing list