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: Why were there many releases after rex was frozen

Lars Wirzenius <liw@iki.fi> writes:

> Does anyone have any logs for what changes happened during the
> freeze, and preferably the relevant .changes files as well?
> 
> I'm not sure I agree that we shouldn't fix minor bugs. However,
> we might want to make a rule that during the final seven days of
> the freeze only critical bugs may be fixed in frozen. If anything
> in frozen changes, the seven day period starts again.
> 

Seven days is a tight schedule.  However, it is still better than what
we did for 1.2.  I agree that if *anything* changes, the test period
starts over again.  Perhaps we could make an exception for
documentation, but I'm not even sure there.

I don't see anything besides documentation installed in rex after
December 9.  I returned after a 1 1/2 week absence of SETI, I found
the 1.2 had been released.  It was impossible to install a custom
kernel under 1.2, this was added December 9.  diald had a change in
configuration which wasn't quite complete (December 9).  I'm sure that
there are other bugs.  In our rush to check the new X release, we
didn't check enough else.  I'm sure that there are other changes as
well.

During the entire four weeks of frozen, I suggest that we actively
discourage new releases.  Whether we allow other than critical fixes
or not, the developers should not be made to feel irresponsible for
letting a non-critical bug fix wait until the next release.


> The development cycle would then be:
> 
> 	* experimental: if it is likely to cause trouble
> 	* unstable: anything goes, as long as it probably works
> 	* unstable if frozen four weeks before release
> 	* first three weeks of frozen: only bug fixes (no new
> 	  packages, no new versions)
> 	* last week of frozen: only fixes to critical bugs; if
> 	  any are needed, however slight, the last week starts again
> 	* release is made
> 


-- 
Kevin Dalley
kevin@aimnet.com


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