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]

Re: Modest proposal for successful releases

On Tue, 14 Jan 1997, Dale Scheetz wrote:

dwarf >I have been thinking about this for some time, and have a modest proposal
dwarf >which doesn't involve eating our young.
dwarf >
dwarf >First: Put less change into the release goals. A simpler set of goals
dwarf >takes less time for development and provides more space for testing.

I think the release goals do not need to determine when a distribution is
released. If those goals are not met but other goals have been
accomplished then some goals have to be postphoned and the release should
go ahead. We need frequent releases to get used to the process and improve
it as we go along. 2 releases a year do not cut it.

dwarf >Second: Set an "internal" release date far in advance of the "public"
dwarf >release. This will let developers know that they must meet an earlier
dwarf >target and so, bump their schedules to succeed.

We tried that. The problem was that people in high places decided to get
some pieces changed in the last days before the release time. We made
Brian responsible for managing the release and then pushed him into things
he did not want.

There was barely any testing done during the frozen period. I got news of
some big problems in some of my packages only when Debian 1.2 was
released.

dwarf >Third: Cultivate a set of users, as beta test sites, who span the range of
dwarf >"strange" machines and "difficult" system configurations, who will be
dwarf >willing to "fully" test the installation of the new release.

Very important! Any ideas how to organize such a group?

dwarf >We currently have no testing groups, either official or unofficial.

And the problem is that all developers probably are already running 1.3.
We ourselves do not run our stable releases! I have begun running our
mission critical servers with 1.3 since I have made the experience that
what we run is more "stable" than what we call "stable"!

dwarf >3. Pick one or two major areas of improvement to complete.
dwarf >	a. Shadow password support

This needs to go into unstable immediately! Why is not there?

dwarf >	b. Impliment the new web server standard

I am wary of that standard. I would like to have simplicity and not that
symlink tree adventure.

What is the procedure on new policies by the way? There seems some changes
that I have never seen discussed (too much traffic on debian-devel?). Who
decides the policies?

--- +++ --- +++ --- +++ --- +++ --- +++ --- +++ --- +++ ---
Please always CC me when replying to posts on mailing lists.


--
Please respect the confidentiality of material on the debian-private list.
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-private-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com