Debian Developers - Re: Bits (Nybbles?) from the Vancouver release team meeting

This is Interesting: Free IT Magazines  
Home > Archive > Debian Developers > March 2005 > Re: Bits (Nybbles?) from the Vancouver release team meeting





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author Re: Bits (Nybbles?) from the Vancouver release team meeting
Karsten Merker

2005-03-15, 6:00 pm

On Tue, Mar 15, 2005 at 05:12:07PM -0500, Stephen Gran wrote:

> If there is a basically doorstop architecture, say a Wang word
> processor, that someone wants to run Debian on, then feel free. Just


We are not talking about doorstops.

> don't expect the release team to coordinate security uploads,
> continuously massage buildd's and testing runs and so forth for you, was
> my interpretation. It seems like the people who came up with this
> proposal have been saying over and over that if the porter teams have
> their act together, they can release like everyone else, and they use
> amd64 of what they would like to see over and over. If the amd64 crew
> can pull it off, I think an established port should have an easier time
> maintaining itself.


There is one major point you miss with this: security updates. I
use Debian on powerpc, mips, mipsel, sparc and i386 production
systems. Yes, I am actually one of the people who run Woody
despite the fact that it is old. I need a working security
infrastructure. Running unstable as is laid out in the proposal
is not an option.

With the proposal we would end up in one of two positions for
the SCC architectures:

a) Run unstable
This is not an option on production systems

b) Have a seperate security team for each architure which must
fight with different versions of many packages and therefore
multiply the ressources needed for that in comparison to
having all architectures released together.

Both are not sensible solutions. Besides that I still fail to see
that the number of architectures is *THE* showstopper for the
release. Yes, we have had problems which caused delays due to
hardware failures and toolchain issues, but there have been
lots of RC bugs which are not arch dependent and which took
long to be resolved - or are still open.

AMD64 does not yet have a release and AFAICS the security support
is not yet established, so taking AMD64 is a bad example.

Regards,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.


--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com