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

Re: post-release package update policy

Steve Byrne: "Re: post-release package update policy" (Oct 21, 13:00):
> debian/
>        debian-0.93R6/
>                      binary/
>                      msdos/
>                      source/
>     	    	     {etc}
>        stable -> debian-0.93R6
>        latest/
>               binary/
>     	    	     ...
>                      net/
>                          ppp-2.2.deb -> ../../../stable/binary/net/ppp-2.2.deb
>                      ...
>               msdos/
>               source/
>               {etc}

My suggestion is similar (I use names that I prefer :-):

		-- a frozen version; _no_ changes are made here after the
		-- version has been updated
		-- R6 + any new or modified packages; a complete distribution
		-- (i.e., it is enough to download just this directory for
		-- the latest and greatest)
		-- only new or modified packages since the last frozen
		-- version (this should be the change from the above
		-- suggestion)

The idea is to have a clearly defined release version in debian-release.
That version is announced.  People wanting to use a stable version download and install this directory.  All packages in this directory are guaranteed to
work together (this is assured by a testing period before the release).

The current development version is in debian-current.  Initially, it contains
the same stuff as debian-release (using copies, symlinks, or hard links
according to local taste), but as packages are added or upgraded, they are
added to debian-current (remember, debian-release stays as it was when it
was announced).  Anyone wanting to be on the bleeding edge download and
install this directory.  There are no guarantees about how well the packages
in this directory work together.

The new or modified packages are also added to debian-updates, so that people
can easily see what existing parts of the release version have changed.

Of course, it may be interesting to archive old releases as well.  So
what the directory actually looks like is:

		-- the 0.93R5 release
		-- the 0.93R6 release
	debian-release -> debian-0.93R6
		-- a symlink to the current release

Incidentally, I'd prefer a two level version numbering scheme for Debian
releases.  I don't think there is much reason to have three levels,
as in 0.93R6; wouldn't 0.94 be better?

Lars Wirzenius <liw@iki.fi> <wirzeniu@kruuna.helsinki.fi>
MIME and PGP mail welcome.  Key: finger @kruuna, or check keyservers.
Publib 0.5: ftp://ftp.cs.helsinki.fi/pub/Software/Local/Publib/

Reply to: