Re: [UDD] Suggested table: release_order
On Wed, Feb 03, 2010 at 01:12:38PM +0100, Lucas Nussbaum wrote:
> If we are going this way, it would make more sense to provide the
> release date as the value to sort on. And use a specific date in the
> future for releases which haven't happened yet.
That's a really good idea and I think I'll going to implement this.
CREATE TABLE releases (
releasename text,
releasedate date,
PRIMARY KEY (releasename)
);
INSERT INTO releases VALUES ( 'etch', '2007-04-08' );
INSERT INTO releases VALUES ( 'etch-security', '2007-04-09' );
INSERT INTO releases VALUES ( 'etch-proposed-updates', '2007-04-10' );
INSERT INTO releases VALUES ( 'lenny', '2009-02-14' );
INSERT INTO releases VALUES ( 'lenny-security', '2009-02-15' );
INSERT INTO releases VALUES ( 'lenny-proposed-updates', '2009-02-14' );
INSERT INTO releases VALUES ( 'squeeze', '2015-01-01' );
INSERT INTO releases VALUES ( 'squeeze-security', '2015-01-02' );
INSERT INTO releases VALUES ( 'squeeze-proposed-updates', '2015-01-03' );
INSERT INTO releases VALUES ( 'sid', '3000-01-01' );
INSERT INTO releases VALUES ( 'experimental', '4000-01-01' );
I had the idea in mind that we first have a release, next day started
security support and at the following day we proposed updates. Squeeze
will hopefully be released before 2015 and sid and experimental are far
enough away for any reader of this list.
Comments?
> > handle releases of Ubuntu which reside in UDD as well and SkoleLinux
> > which I plan to add sooner or later.
>
> Well, release dates would apply as well.
Yes. Would anybody care for injecting the dates?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: