Ubuntu releases are hardcoded in the script

If one were to use launchpadlib something like this would work:

In [2]: u = launchpad.projects['ubuntu']

In [4]: u.current_series.name
Out[4]: u'lucid'

Current series is the current development series of the distribution.

Using anonymous access is probably the best idea here too.

http://blog.launchpad.net/general/anonymous-access-to-the-launchpad-web-service-api

Brian: I was somewhat leery of pulling the current release out of launchpad, not wanting yet another network dependency that might be susceptible to bandwidth issues.

Steve, how are you getting on with this issue?
I think Brian's solution is good enough. The bandwidth used for launchpad is minimal, compared to sync a CD.
We need to try to get this done (and uploaded to Lucid) before RC, or we are going to miss this release as well.

Ara, I just committed a fix that updates the current release from launchpad if it differs from the script's notion of what the current development release. As we'll have lucid point releases to test eventually, the script should not rely wholly on what launchpad thinks is current. I tested it by converting all references from lucid to karmic and letting it run; it correctly attempted to pull both karmic and lucid after querying launchpad.

I also added a flag to skip the launchpad check if so desired.

I've added a couple more fixes to trunk that (a) automatically skip the check if launchpadlib isn't available (e.g. on Hardy) and (b) falls back to non-anonymous querying of launchpad when the anonymous methods aren't available (e.g. on Karmic).

This bug was fixed in the package ubuntu-qa-tools - 0.1.4.4

---------------
ubuntu-qa-tools (0.1.4.4) lucid; urgency=low

  * Make dl-ubuntu-test-iso work from behind a transparent proxy.
    (LP: #512691)
  * dl-ubuntu-test-iso now supports authentication. (LP: #541725)
  * Ubuntu releases are no longer hardcoded in dl-ubuntu-test-iso.
    (LP: #541729)
 -- James Westby <email address hidden> Wed, 14 Apr 2010 11:27:00 +0100