Merge lp:~bladernr/ubuntu-qa-tools/dl-ubuntu-test-iso-maverick into lp:ubuntu-qa-tools

Proposed by Jeff Lane 
Status: Merged
Merged at revision: 373
Proposed branch: lp:~bladernr/ubuntu-qa-tools/dl-ubuntu-test-iso-maverick
Merge into: lp:ubuntu-qa-tools
Diff against target: 28 lines (+3/-3)
1 file modified
dl-ubuntu-test-iso/dl-ubuntu-test-iso (+3/-3)
To merge this branch: bzr merge lp:~bladernr/ubuntu-qa-tools/dl-ubuntu-test-iso-maverick
Reviewer Review Type Date Requested Status
James Westby (community) Needs Information
Review via email: mp+26493@code.launchpad.net

Description of the change

added bits to include maverick in dl-ubuntu-test-iso script.

To post a comment you must log in.
Revision history for this message
James Westby (james-w) wrote :

Hi,

What effect does

25 -default['releases'] = ['hardy', 'lucid']
26 +default['releases'] = ['lucid', 'maverick']

have?

Hardy is still a supported release, is that supposed to be "latest LTS + development release"?

Thanks

James

review: Needs Information
Revision history for this message
Steve Beattie (sbeattie) wrote :

On Tue, Jun 01, 2010 at 03:48:36PM -0000, James Westby wrote:
> What effect does
>
> 25 -default['releases'] = ['hardy', 'lucid']
> 26 +default['releases'] = ['lucid', 'maverick']
>
> have?
>
> Hardy is still a supported release,

Hardy is still a supported release (so is Dapper); however, unless
plans have changed, we will not be spinning more Hardy isos (i.e. no
more Hardy point releases).

> is that supposed to be "latest LTS + development release"?

Yes. If you're aware of a way we can query launchpad or the archive
to determine this at runtime, I'd appreciate hearing about it. (We
already query launchpad if possible to update the name of the current
development release dynamically).

--
Steve Beattie
<email address hidden>
http://NxNW.org/~steve/

Revision history for this message
James Westby (james-w) wrote :

On Tue, 01 Jun 2010 16:12:36 -0000, Steve Beattie <email address hidden> wrote:
> On Tue, Jun 01, 2010 at 03:48:36PM -0000, James Westby wrote:
> > What effect does
> >
> > 25 -default['releases'] = ['hardy', 'lucid']
> > 26 +default['releases'] = ['lucid', 'maverick']
> >
> > have?
> >
> > Hardy is still a supported release,
>
> Hardy is still a supported release (so is Dapper); however, unless
> plans have changed, we will not be spinning more Hardy isos (i.e. no
> more Hardy point releases).
>
> > is that supposed to be "latest LTS + development release"?
>
> Yes. If you're aware of a way we can query launchpad or the archive
> to determine this at runtime, I'd appreciate hearing about it. (We
> already query launchpad if possible to update the name of the current
> development release dynamically).

You can iterate over the series to get the listing of what is LTS. It
won't help you to know if any further point releases are planned though.

Thanks,

James

Revision history for this message
Steve Beattie (sbeattie) wrote :

On Tue, Jun 01, 2010 at 05:09:28PM -0000, James Westby wrote:
> You can iterate over the series to get the listing of what is LTS. It
> won't help you to know if any further point releases are planned though.

Care to explain how? Given:

  In [1]: from launchpadlib.launchpad import Launchpad
  In [2]: lp = Launchpad.login_anonymously("my client", "edge")
  In [3]: ubuntu = lp.distributions['ubuntu']

doing:

  In [21]: for s in ubuntu.series:
     ....: if s.active:
     ....: print s.fullseriesname, s.displayname, s.status, s.summary

gives:

  Ubuntu Maverick Maverick Active Development See http://wiki.ubuntu.com/MaverickMeerkat
  Ubuntu Lucid Lucid Current Stable Release See http://wiki.ubuntu.com/LucidLynx
  Ubuntu Karmic Karmic Supported See http://wiki.ubuntu.com/KarmicKoala
  Ubuntu Jaunty Jaunty Supported See http://wiki.ubuntu.com/JauntyJackalope
  Ubuntu Hardy Hardy Supported Hardy is the second Long Term Support ("LTS") release of Ubuntu, with a strong emphasis on supportability for long term deployments on both the desktop and the server.
  Ubuntu Dapper Dapper Supported Ubuntu 6.06 LTS (The Dapper Drake Release) is the first long-term-supported release of Ubuntu. Dapper features a GUI installer optimised for simplicity and speed and official support for a new server architecture: SPARC.

Nothing in https://edge.launchpad.net/+apidoc/1.0.html#distro_series
gives any indication where or how an LTS release would be annotated
differently. The 'status' field doesn't appear to be it, 'Current
Stable Release' is the only value that indicates the current release,
LTS or not.

Unless, that is, you're suggesting a regex out through the description
field, which seems brittle and for lucid, doesn't even mention LTS:

  Ubuntu Lucid Lucid Current Stable Release Lucid will be delivered
  in April 2010 on the normal six-month Ubuntu cycle. It will be
  designated 10.04

Thanks in advance for any clues you can give.

--
Steve Beattie
<email address hidden>
http://NxNW.org/~steve/

Revision history for this message
James Westby (james-w) wrote :

On Tue, 01 Jun 2010 17:43:23 -0000, Steve Beattie <email address hidden> wrote:
> Nothing in https://edge.launchpad.net/+apidoc/1.0.html#distro_series
> gives any indication where or how an LTS release would be annotated
> differently. The 'status' field doesn't appear to be it, 'Current
> Stable Release' is the only value that indicates the current release,
> LTS or not.

Yeah, sorry, I thought there was an attribute for it, but there clearly
isn't.

Thanks,

James

Revision history for this message
Jeff Lane  (bladernr) wrote :

On Tue, 2010-06-01 at 18:00 +0000, James Westby wrote:
> On Tue, 01 Jun 2010 17:43:23 -0000, Steve Beattie <email address hidden> wrote:
> > Nothing in https://edge.launchpad.net/+apidoc/1.0.html#distro_series
> > gives any indication where or how an LTS release would be annotated
> > differently. The 'status' field doesn't appear to be it, 'Current
> > Stable Release' is the only value that indicates the current release,
> > LTS or not.
>
> Yeah, sorry, I thought there was an attribute for it, but there clearly
> isn't.

I really planned on staying out of this conversation :-) but, excuse my
ignorance, which is great here, but would it be possible (maybe a
wishlist bug or something as a reminder) to add that attribute, maybe
even something as simple as a boolean for LTS?

I'm assuming that doing so is non-trivial, but I don't know enough about
the inner workings of LP and the various things that tie in to all this
to really know.

--
Jeff Lane <email address hidden>
Ubuntu Ham: W4KDH
IRC: bladernr or bladernr_
gpg: 1024D/3A14B2DD 8C88 B076 0DD7 B404 1417 C466 4ABD 3635 3A14 B2DD

Revision history for this message
Brian Murray (brian-murray) wrote :

The version attribute of the series should / could allow LTS so it'd be 10.04 LTS instead of 10.04.

Revision history for this message
James Westby (james-w) wrote :

On Tue, 01 Jun 2010 18:22:22 -0000, Jeff Lane <email address hidden> wrote:
> On Tue, 2010-06-01 at 18:00 +0000, James Westby wrote:
> > On Tue, 01 Jun 2010 17:43:23 -0000, Steve Beattie <email address hidden> wrote:
> > > Nothing in https://edge.launchpad.net/+apidoc/1.0.html#distro_series
> > > gives any indication where or how an LTS release would be annotated
> > > differently. The 'status' field doesn't appear to be it, 'Current
> > > Stable Release' is the only value that indicates the current release,
> > > LTS or not.
> >
> > Yeah, sorry, I thought there was an attribute for it, but there clearly
> > isn't.
>
> I really planned on staying out of this conversation :-) but, excuse my
> ignorance, which is great here, but would it be possible (maybe a
> wishlist bug or something as a reminder) to add that attribute, maybe
> even something as simple as a boolean for LTS?

That would be possible yes. You can file a bug against
"launchpad-registry" to discuss it with them if you like.

> I'm assuming that doing so is non-trivial, but I don't know enough about
> the inner workings of LP and the various things that tie in to all this
> to really know.

It's not too much work: a db patch to add the column, a model change to
store it, UI to tweak it, and a small change to expose it over the
API. Fairly standard for a launchpad change.

It's not something that would take 10 minutes though, and they may not
wish to have it anyway, as "LTS" is Ubuntu-specific, and they have
historically avoided putting too much Ubuntu-specific code in to
Launchpad.

Thanks,

James

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'dl-ubuntu-test-iso/dl-ubuntu-test-iso'
2--- dl-ubuntu-test-iso/dl-ubuntu-test-iso 2010-04-13 20:46:17 +0000
3+++ dl-ubuntu-test-iso/dl-ubuntu-test-iso 2010-06-01 14:20:50 +0000
4@@ -18,14 +18,14 @@
5 import signal
6 import tempfile
7
8-current_release = 'lucid'
9+current_release = 'maverick'
10 releasedict = {}
11 releasedict['hardy'] = []
12 releasedict['intrepid'] = []
13 releasedict['jaunty'] = []
14 releasedict['karmic'] = []
15 releasedict['lucid'] = []
16-
17+releasedict['maverick'] = []
18 #allreleases = ['hardy', 'intrepid']
19 allarchs = ['i386', 'amd64', 'lpia', 'armel']
20
21@@ -34,7 +34,7 @@
22 default['variants'] = ['desktop', 'alternate', 'dvd']
23 default['build'] = 'current'
24 default['host'] = 'cdimage.ubuntu.com'
25-default['releases'] = ['hardy', 'lucid']
26+default['releases'] = ['lucid', 'maverick']
27 default['isoroot'] = environ['HOME'] + '/iso/'
28 default['do_release_check'] = True
29