The debian-private mailing list leak, part 1. Volunteers have complained about Blackmail. Lynchings. Character assassination. Defamation. Cyberbullying. Volunteers who gave many years of their lives are picked out at random for cruel social experiments. The former DPL's girlfriend Molly de Blanc is given volunteers to experiment on for her crazy talks. These volunteers never consented to be used like lab rats. We don't either. debian-private can no longer be a safe space for the cabal. Let these monsters have nowhere to hide. Volunteers are not disposable. We stand with the victims.
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RFC: Debian Service Team

Hi folks!

I was thinking once more about our "unstable is more stable than stable"
problem :-) I think the main problem is that no Debian developer is
responsible for the stable release nor does someone have the possibility
to introduce any changes (bug fixes) in a simple way.

However, most of the Debian users out there use our stable releases and
would probably prefer if we'd better maintain it.

This is would be nice if the "code freeze" we had in the last weeks would
continue until Debian 2.0 is released. I mean, that all bug fixes that are
being put into "hamm" now should also go into "bo". (I wouldn't like to
introduce new upstream versions into "bo" unless the fix serious bugs.
Thus I'm not talking about new stable releases with new features but about
more _stable_ releases.)

I know that all "stable uploads" have always been risky (for example,
1.2.17 includes a packages depending on a package only available in "bo"!)
and I also know that only few of us have "stable" systems available for
compiling packages.

That's why I suggest forming a "Debian Service Team". This team should
"maintain" the stable release and coordinate the 1.3.x releases just the
way we are now handling the 1.3 release: Say way agree that we want to
have a 1.3.x release every four weeks, then the first two weeks of 1.3.x
development are for introducing bug fixes and the second two weeks are for
freezing the distribution.

Whenever a package maintainer uploads a new package into unstable which
fixes a few old bugs, someone from the Service Team should introduce the
bug fix into the corresponding stable package. 

The Service Team would also a good institution for following debian-user
and for maintaining the FAQ and a "Debian Release Notes" document.

And after all we could probably enhance our handling of security
notifications. Recall that whenever we get an advisory at
security@debian.org the fixed package was uploaded within a day most of
the time, but when the official notification was presented to the public
through the security mailing lists, Red Hat was always the only
distribution which was listed in the Linux section. 

(I hope this all doesn't sound to negative. I'll really impressed about
the stability of "bo" now. I'm just searching for a way how we can
improve the system in the 1.3.x releases.)


My $0.02,

Chris

--                 Christian Schwarz
Do you know         schwarz@monet.m.isar.de, schwarz@schwarz-online.com,
Debian GNU/Linux?    schwarz@debian.org, schwarz@mathematik.tu-muenchen.de
      
Visit                  PGP-fp: 8F 61 EB 6D CF 23 CA D7  34 05 14 5C C8 DC 22 BA
http://www.debian.org   http://fatman.mathematik.tu-muenchen.de/~schwarz/


--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-request@lists.debian.org . 
Trouble?  e-mail to templin@bucknell.edu .