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

Re: -= PROPOSAL =- Release sarge with amd64



On Wed, Jul 14, 2004 at 08:09:21PM +0200, Bartosz Fenski aka fEnIo wrote:
> On Wed, Jul 14, 2004 at 08:17:14PM +0300, Antti-Juhani Kaijanaho wrote:
> > Am I the only one who's smelling an incoming project fork?  I'd like
> > it if it didn't come to that.
> 
> Don't even say things like that. 
> 
> Not forking is one of the greatest thing in Debian, and gives it 
> strenght to exist and grow up.
> 
> Please don't be childish. If there is something which you think is not
> working properly then try to change that in civilized manner and not by
> personal flamewars.

Discussing things in a civilized manner has already been shown not to
work. Certain groups in Debian refuse to communicate no matter how you
approach them.

> I thought we're all volunteers. Everybody wants to do his/her best for
> the project, so personal charges won't help us. 
> 
> As far as I was wathing this thread the best featured way was IMHO
> releasing Sarge without Amd64 support. 
> After release there is always time to prepare r1 revision and then
> include Amd64 with it. I think that if someone really wants Amd64 port 
> then it doesn't matter for him if it will be r0 or r1 release.
> But most our users are using i386 arch, and they're waiting for release
> for almost two years now. 

Who has ever said or even thought a XrY release can have more than
security fixes? It never has in the past and with the fixes we need to
commit to various packages is not even likely to happen. The only person
who can decide this is the RM and I have not seen any comment from him
about letting new archs into a Debian point release. In 2-3 years
when sarge+1 is released the situation wrt i386 users vs amd64 users
will be reversed. Or perhaps it won't have since most of the amd64 users
will have switched to another dist by then.

> Please do not add Amd64 arch to Sid before Sarge release. Even if it won't 
> be released with Sarge it could potentially only take developers time 
> to fix their Amd64 bugs instead of RC bugs for another architectures.

Almost all of the known amd64 bugs are already fixed with patches in
bts. Of course there are still various 64bit issues, but most of these
also bite the alpha and ia64 archs. There is not much left needed to be
done at this point other than have someone apply the patches and upload.
This could be done via the maintainers themselves, by the amd64 team
NMUing them, or with the regular bug squashing parties that are being
held. People will work on what they want regardless of if amd64 is in
the archive or not, adding it will not pull more people off other RC
bugs. If amd64 port has too many port specific rc bugs it simply won't
get released with sarge. It won't significantly prolong the sarge
release if at all.

Chris

Attachment: signature.asc
Description: Digital signature


Reply to: