Quantal open for development

[Bryce Harrington]

On Tue, May 01, 2012 at 09:27:33AM -0400, Barry Warsaw wrote:
> On May 01, 2012, at 03:14 PM, Benjamin Drung wrote:
> 
> >Am Montag, den 30.04.2012, 12:16 -0400 schrieb Barry Warsaw:
> >> (Hint: you need to install debootstrap explicitly from precise-backports
> >> first.)
> >
> >Can't we have a SRU this instead?
> 
> I think that would be better, but I don't know why it was backported instead
> of SRUd.  Over in #ubuntu-devel, Stefano discovered that it was handled
> differently for Oneric->Precise because we knew the code name early enough to
> make the change before the release.  This time, we didn't know Quantal's code
> name until the rc's were being spun.
> 
> So I'd like to understand the rationale for backporting it before going
> through the SRU process.  Maybe we need A Policy for the future too.

By the way, this information can be queried from launchpad via the API.
Scripts to do this are included in the python-launchpadlib-toolkit
package:

$ current-ubuntu-development-codename 
quantal

$ current-ubuntu-release-codename 
precise

$ current-ubuntu-supported-releases 
oneiric
natty
lucid
hardy

These run as read-only so the user doesn't need to log in to launchpad.
And the data is cached (under /tmp) to avoid (slow) lookups, and so you
can call them frequently.

I suspect the distro-info script is a better solution for this use case,
but the lpltk scripts at least have the benefit of not requiring
SRUs/backports.

Bryce