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: Continuous Releases?

On Fri, 31 Jan 1997, Lars Wirzenius wrote:

> [ Please don't Cc: me when replying to my message on a mailing list. ]
> 
> Craig Sanders:
> > However, I think that "frozen" should MEAN "frozen".
> 
> Substituting "rex" for "frozen", it is. Stable isn't -- it
> gets fixed when there are problems (and there always will be,
> regardless of the amount of testing).

To be honest, I would like to see debian NOT do so many point
releases.  A point release should be reserved for changing
something in an otherwise frozen release.  The updates and fixed
links should remain for convenience, but Debian-1.3 should _not_
include updates put in place after its initial release.  I would
also like to see updates split up into updates and
security-updates.  That would clearly identify fixes to security
issues.

That would leave us with:

Debian-1.3 as a link to frozen.
stable as a link to bo-fixed
bo-fixed as a mixed bag of links to frozen and bo-updates 
	+ bo-security-updates
bo-updates would be newer packages than in frozen that fix bugs
	we think can't wait for the next release.
bo-security-updates would be newer packages than in forzen that
	fix security problems.

Point releases would be reserved for significant changes in the
release, such as a library update that effects many packages.  If
there winds up being a large number of updates, then a point
release to consolidate them may be in order as well.  If there
are so many changes, it probably looks like a different release
anyway, so a point release is more honest than just having the
<name>-updates and links in <name>-fixed.

I also think that point releases could be scheduled.  If we have
a set of goals that we come just short of for a release date, we
should make an initial release that's stable and issue a point
release with the additional functionality intended for the
original release.

> 
> We have rex, rex-updates, and rex-fixed, with stable pointing
> at rex-fixed. We need all three.

See above for my thoughts on adding <name>-security-updates

> > Users should be referred to "live" aka "unstable" for any updates.
> 
> No.

Agreed.

Richard G. Roberto
richr@bear.com
011-81-3-3437-7967 - Tokyo, Japan


--
*******************************************************************************
Bear Stearns is not responsible for any recommendation, solicitation, offer or
agreement or any information about any transaction, customer account or account
activity contained in this communication.
*******************************************************************************


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