[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: stable vs. testing: same versions, different status



On Sun, 28 Jun 2009 23:14:20 -0400 Michael S. Gilbert wrote:

> On Sun, 28 Jun 2009 18:48:17 +0200 Francesco Poli wrote:
> > That's why I am trying to figure out how the manpower issue can be
> > solved: because I would love to see DTSAs and all the full security
> > support for Debian testing, even when it is apparently harder (i.e.:
> > immediately after a release).
> 
> the issue is not necessarily manpower itself, but rather the value of
> volunteers' time.  it makes little sense to duplicate work for testing
> and unstable when unstable will eventually overwrite testing.

The same reasoning (on a larger scale) could be applied to stable and
would lead to the conclusion that security updates make little sense,
since a new stable release will eventually replace the current stable on
end-users' boxes (e.g.: etch replaced sarge, lenny replaced etch, and
so forth).

I am not convinced that this would be a reasonable conclusion...

[...]
> > I think it should be done automatically at archive level.
> > 
> > An automatic stable-update --> testing,unstable migration mechanism is
> > already in place for point releases, as stated by Nico Golde in
> > http://lists.debian.org/debian-security-tracker/2009/06/msg00009.html
> > 
> > A similar automatic stable-security --> testing-security migration
> > mechanism should be implemented, IMHO.
> 
> even though there is an existing solution, my argument for it as the
> only option is counter-productive; and i do not wish to say no just to
> say no.  i would suggest talking to the ftp-masters and the security
> team (team@security.debian.org) about whether they would be interested
> in implementing your idea.

I've just sent a message to the FTP Masters and to the Security Team.
I am looking forward to reading their response.


-- 
 New location for my website! Update your bookmarks!
 http://www.inventati.org/frx
..................................................... Francesco Poli .
 GnuPG key fpr == C979 F34B 27CE 5CD8 DC12  31B5 78F4 279B DD6D FCF4

Attachment: pgpcd38LBYAKz.pgp
Description: PGP signature


Reply to: