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)

Bruce Perens <Bruce@pixar.com> wrote:
> > By the schedule I've been keeping, the end of January will mark
> > the end of month 1 with Bo being frozen at the end of month 2.
> 
> 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.
> 
> You don't want to release on April 1, obviously. I feel a 1-month
> public beta is essential. You don't need a CD-writer to test the beta
> ISO images, any raw disk partition will do.

I agree with the 1 month public beta and I like the idea of having
some time of "private" beta (which I previously not had).

Perhaps we should do a 4-month release schedule (5 months including
the one month overlap with the previous public beta) instead of the
3-month currently planned?  Once we can manage that okay we could
increase the frequency of our releases.

It would the look something like...

Month 0: (overlap with public-beta of previous release)
 - everybody should be using the "frozen" release
 - start uploading of packages into "unstable"

Month 1:
 - previous distribution is released; developers start using "unstable"
 - free-for-all (upload of anything)

Month 2:
 - major package upgrades are avoided, minor ones okay

Month 3: "private-beta"
 - A "frozen" distribution is created
 - Bugfixes and minor code enhancements are allowed

Month 4: "public-beta"
 - "frozen" is announced to the public
 - Nothing but "bugfixes" is allowed into the distribution
   (enhancements allowed only with explicit permission form dist manager)

Release!

                                          Brian
                                 ( bcwhite@verisim.com )
                                             
-------------------------------------------------------------------------------
   Give others some insight into YOUR pages!  http://www.verisim.com/insite/


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