What is wrong with Joey's proposal? We need a Y2K release NOW.

[Rob Browning <rlb@cs.utexas.edu>]

(I'm behind on debian-devel, so apologies if this has already been
 beaten to death.)

I didn't realize that this was an issue, but if Joey is right, then
why aren't we paying more attention?  If we're not going to get the
current unstable out the door in the next couple of weeks (in time for
people to notice and upgrade), and I suspect we're not, then what are
we going to say to our users?

Unless there's something I'm overlooking, I think we should give Joey
support in getting a Y2K update for stable out *soon*, especially
since he's not just tring to dictate, he's willing to do the work.
This is IMO substantially more important than getting unstable out a
week or two sooner, presuming that that still means sometime after the
beginning of December.

Joey Hess <joeyh@debian.org> writes:

> One thing that no-one has pointed out yet is that stable has known y2k
> problems in it. Not releasing an update of some kind to fix these problems
> before y2k is going to make us look like fools.
> 
> I would like to bring back up the idea of releasing a major update to slink.
> I have the majority of the work done, it has been done for months and has
> received a fair amount of testing [1]. This would include kernel 2.2.13, y2k
> fixes, security fixes, an updated X, and little else.
> 
> If certian parties had not prevented me from doing this several months ago,
> we would have released this about 1 month ago, and this delay of the freeze
> would not be such a big deal. Please don't make the same mistake again
> folks, I'm volenteering to do most of the work, and I work on debian full
> time..
> 
> -- 
> see shy jo
> 
> [1] You'll find it in the back of the O'Reilly book, for example.
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 
> 

-- 
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930