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: Quality: some thoughts on achieving it (long)



David Engel wrote:
> 
> > Bruce Perens <Bruce@pixar.com> wrote:
> > > 1.2 was screwed up enough that we should go with 1.3 on schedule, and
> > > try for little more than _stability_ and the availability of an
> > > official ISO image that is trouble-free to install for most users. One
> > > reason for this is that 2.0 might take longer than 3 months to get
> > > together, so 1.3 could be out there for a while. I suggest this
> > > schedule:
> > >
> > >         Freeze: March 1.
> > >         Start Private Beta: March 3
> > >         Public Beta On All Mirrors and Announced: March 15
> > >         Beta Official ISO Image on Selected Mirrors: March 17
> > >         Release of FTP archive and Official ISO Image: April 15.
> 
> Bruce is probably right about 2.0 possibly taking longer than 3
> months.  This is why I'm going to suggest that we move UP the release
> of 1.3 to as soon as possible or cancel it all together so we can
> start on 2.0 and give ourselves as much time as possible.  Glibc is
> here now and converting to it will cause the same type of developer
> chaos we had when converting to libc5, though hopefully not as bad.

2.0 implies some relatively large technical goals.  Moving on to 2.0
immediately means biting off more tech than usual, as well as biting off
more release procedure than usual.  I think that's a pretty "unideal"
combination.

It is imperative that we shelve (relatively speaking) technical goals
for the time being, long enough to get our release procedures working.

I firmly believe we should cut a 1.3 release, taking as long as is
required to do it well (trying to keep the release date but refusing to
release something before it's ready), and use that experience to combine
tech and decent release procedure on 2.0.


--
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