diff options
author | Joey Hess <joeyh> | 1999-11-09 23:44:16 +0000 |
---|---|---|
committer | Joey Hess <joeyh> | 1999-11-09 23:44:16 +0000 |
commit | 691e0441bb51d3ae14922e29ccf3653a9938ac6e (patch) | |
tree | 8f54e2105bdafcdb54729812880fd1a4a1cd224f | |
parent | a97875254850117be2ea6d5869d96b25deacf8c3 (diff) |
added messages
CVS version numbers
english/News/weekly/1999/43/mail.wml: 1.1 -> 1.2
-rw-r--r-- | english/News/weekly/1999/43/mail.wml | 108 |
1 files changed, 108 insertions, 0 deletions
diff --git a/english/News/weekly/1999/43/mail.wml b/english/News/weekly/1999/43/mail.wml index acca966f1f0..a16fd26b7fc 100644 --- a/english/News/weekly/1999/43/mail.wml +++ b/english/News/weekly/1999/43/mail.wml @@ -140,4 +140,112 @@ indifferent, especially to the criticisms regaring frequency of release and the quality of the boot-floppies. </pre> +<hr> + +<a name=3> +<pre> +Date: Tue, 9 Nov 1999 07:23:23 +1100 +From: Chris Leishman <masklin@debian.org> +To: debian-devel@lists.debian.org +Subject: Partial freeze? + +Ok, + +Here is another thought (probably one that has come up before - gotta love +going around in circles. Let me know if I am). + +The problem at the moment is that no-one wants to freeze, because we don't +know how long we will be frozen for - and in that time things get stale and +old. And why don't we know how long we will be frozen for? Because some +"critical to release" packages (like boot-floppies) are not stable and we don't +know how long they will take to become so. + +However - IMHO if we don't freeze, then we are in the same position as +unstable always is - at any point there can be an update that will cause a +different "critical to release" package to fail. Who knows - in a month when +we have boot-floppies working, some other new or updated package might (or +new policy) might still prevent us from freezing for the same reasons.. + +Bit of a catch 22 really. If we freeze, then things can stabilise, but they +might also get stale. If we don't, then things won't get stale, but they may +not stabilise quickly. + +How about this then: We identify those packages which are considered +"critical to release". This would include packages like boot-floppies and +policy. Then we declare a _freeze on those packages_. The same freeze rules +apply - only bug fixes to these packages allowed. + +However, new uploads can continue while this stuff stabilises - as long as +they don't cause problems with the "critical to release" packages. If they +do, then the freeze rules apply to that upload (no new code). + +Eventually we freeze the whole distribution for a very short time to clean +release critical bugs in non-core packages. We should take a fairly hard line +on these, and basically say that if there was a version without _new code_ +that didn't exhibit the problem, we backdate to it rather than bugfix. + +Ok..conclusions from this idea... This _may_ lengthen the freeze time, since +we are effectively doing 2 freezes. But the second phase (the phase that can +introduce stagnation) will be much shorter than it is in our current situation. + +Another conclusion may be that this just sounds like common sence, and there +is no need to make it official...but I've always found these things work much +better when they are enforced. + +The last remaining question is how workable this concept is.... + + +Best regards, + +Chris + +(wish me well for my macroeconomics exam in...oh...1 1/2 hours :) + +-- +---------------------------------------------------------------------- + Linux, because I'd like to *get there* today +---------------------------------------------------------------------- +Reply with subject 'request key' for GPG public key. KeyID 0xB4E24219 +</pre> + +<hr> + +<a name=4> +<pre> +To: debian-devel-announce@lists.debian.org +Cc: ftpmaster@debian.org +Reply-To: ftpmaster@debian.org +Subject: New members of the archive maintenance team +From: James Troup <james@nocrew.org> +Date: 09 Nov 1999 00:41:51 +0000 + +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA1 + +[ Please don't reply to debian-devel-announce ] + +Hi, + +I'd like to publicly welcome Gergely Madarasz and Antti-Juhani +Kaijanaho who are joining Guy, Richard and I as members of the archive +maintenance team. + +Even though we originally only asked for one person to help, we +decided to take on two new members due to the number of NEW packages +being uploaded every day. + +Thank you to everyone else who kindly volunteered their help. + +- -- +James +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.0.0 (GNU/Linux) +Comment: Processed by Mailcrypt 3.5.4 and Gnu Privacy Guard <http://www.gnupg.org/> + +iD8DBQE4J22rgD/uEicUG7ARAlWcAKCSLTKJG76UArnF7ZN9TeQonVGinACg3XPM +A9RkFdHOQK7Kluwp9KEwi0A= +=C8iF +-----END PGP SIGNATURE----- +</pre> + #use wml::debian::weeklynews::footer |