Re: Suggestion: Skip Slink!
On Sun, 3 Jan 1999, John Goerzen wrote:
> I propose that Debian skip slink, and have a freeze of potato soon.
> This comes for several reasons:
My reasons are interlaced.
> 1. Slink is already seriously obsolete, since it has been frozen for
> about as long as we are supposed to go between releases.
I'd prefer slink to hamm.
> 2. Slink release is some time off, and is complicated by the fact
> that most developers now run potato.
I don't feel it is far off. The boot-floppies are looking good, debian-cd
has some working scripts that handle the multi-cd problem, and the release
critical bug list isn't as bad as I thought. I've also heard good reports
> 3. Slink freeze has not (yet) been done properly on some archs.
I didn't think releasing all arch's in unison was required. They can
sync up and go stable when they are ready.
> If we go with potato, we can:
> 1. Include X 3.3.3 (YAY!)
> 2. Include Linux 2.2.0 (YAY!) (well, maybe.)
> 3. Include current versions of other programs (do I smell Perl5.005?)
And spend a lot of time fixing all the new bugs we just introduced. Major
bugs cause major change, at least from what I've seen in the past.
> And, if we freeze it quickly, it may not be any later than a slink release.
> It appears that a slink release is at least a few months off anyway.
I'm optimistically hoping for the end of this month, maybe only a few
> Slink is looking like a big mass of obsolete stuff to me.
Maybe I don't stay on the cutting edge, but it looks pretty good to me
(this coming from someone who still uses fvwm, programs in C, but enjoys
1) is Brian White around, what was that about the release manager being
2) are important bugs release critical? It's been too long since I've had
to think about this.
Thanks for reading this far and don't worry, it will happen soon enough,
| Brandon Mitchell * firstname.lastname@example.org * http://bhmit1.home.ml.org/ |
| Sometimes you have to release software with bugs. - MS Recruiter |