Diff for "LaunchpadReleases"

Not logged in - Log In / Register

Differences between revisions 39 and 40
Revision 39 as of 2010-01-28 13:08:08
Size: 6221
Editor: cpc3-wolv12-0-0-cust183
Comment:
Revision 40 as of 2010-01-28 15:59:28
Size: 6240
Editor: cpc3-wolv12-0-0-cust183
Comment:
Deletions are marked like this. Additions are marked like this.
Line 33: Line 33:
If you discover a bug in the Edge version of Launchpad, providing the build number in your bug report may help the Launchpad team.
Line 34: Line 35:
== Release numbering ==
Line 36: Line 36:
Our release numbers are easy to understand and follow a format you're likely to have seen elsewhere. = Release numbering =

Our release numbers are easy to understand and follow a ''similar'' format to Ubuntu release numbers. The first part of the number is the year in which the release was made and the second part of the number is the number of releases so far that year.
Line 39: Line 41:

||<tablestyle="font-size: 0.8em; width:30%; background:#F1F1ED; margin: 1em 1em 1em 0;" style="padding:0.5em;">{{attachment:new-numbering.png}}||
||<style="text-align: center;">'''Understanding Launchpad release numbers'''||

== The older style of release numbering ==

Previously, Launchpad releases were numbered using a different scheme.
Line 43: Line 52:
 * '''Major release:''' this is the first integer in the release number. We increase this number when there's a significant change in functionality or the underlying structure.  * '''Major release:''' this is the first integer in the old-style release number. This number increased at each major new version of Launchpad, particularly when there was a significant change in functionality or the underlying structure.
Line 47: Line 56:
 * '''Individual release:''' the third integer. This changes with each roll-out of new Launchpad code. Right now, we release a new version once a month, although this number doesn't necessarily tie up with number of the month.

We don't use release candidate numbers.

== Build numbering ==

If you need to know which version of Launchpad you're using, you can take a look at the release number.

However, if you're using our [[BetaTesting|Edge environment]], it may be helpful to know the exact build you're using. On Edge, the build number changes almost every day. On standard Launchpad, it rarely changes more than once per release.

If you discover a bug in the Edge version of Launchpad, providing the build number in your bug report may help the Launchpad team.
 * '''Individual release:''' the third integer. This changed with each roll-out of new Launchpad code.

Introduction

Almost every month we release a new version of Launchpad with the latest features and bug fixes.

We use Launchpad milestones to target work for these releases. You can see what we have planned for each release by visiting the milestones page for the Launchpad project group and viewing one of the upcoming milestones.

Finding the current release and build numbers

Depending on which Launchpad environment you're using, there are two ways to find out which version number and build is running.

On production Launchpad, you need to view the source code of the page. At the very end, you'll find the version and build numbers.

source-code-showing-release-and-build-numbers.png

Finding the release number on production

If you're using edge or staging, the version and build numbers are show in the footer of each page.

edge-footer.png

Finding the release number on Edge

In the screen shot, you can see that release 10.01, build 8939 is running on Edge.

The difference between build and release numbers

Each release represents a certain set of features and fixes that the Launchpad community have worked on and made available in Launchpad production. In effect, a release number is a collective reference for all the features and fixes that the community hope to release at that time.

The build number is taken from the number of the most recent commit to the Launchpad code base running in that environment (e.g. production or edge). This number is more tied to the implementation of the features and fixes. So, while the release number may stay the same, if there's an urgent bug fix or similar, the build number could feasibly change between releases.

If you discover a bug in the Edge version of Launchpad, providing the build number in your bug report may help the Launchpad team.

Release numbering

Our release numbers are easy to understand and follow a similar format to Ubuntu release numbers. The first part of the number is the year in which the release was made and the second part of the number is the number of releases so far that year.

Let's take a look at an example:

new-numbering.png

Understanding Launchpad release numbers

The older style of release numbering

Previously, Launchpad releases were numbered using a different scheme.

release-numbering.png

Understanding Launchpad release numbers

  • Major release: this is the first integer in the old-style release number. This number increased at each major new version of Launchpad, particularly when there was a significant change in functionality or the underlying structure.

  • Minor release: the second integer. This represents an incremental change in functionality or structure. For example: we moved from 1.1.x to 1.2.x with our January 2008 release.

  • Individual release: the third integer. This changed with each roll-out of new Launchpad code.

Release announcements

With every release, we tell you what's new in a release announcement posted to the launchpad-users mailing list and the Launchpad News blog.

2010

  • 10.01: 27th January 2010

2009

  • 3.1.12: 17th December 2009

  • 3.1.11: 2nd December 2009

  • 3.0: 23rd September 2009

  • 2.2.7: 22nd July 2009

  • 2.2.6: 24th June 2009

  • 2.2.5: 26th May 2009

  • 2.2.4: 29th April 2009

  • 2.2.3: 1st April 2009

  • 2.2.2: 26th February 2009

  • 2.2.1: 28th January 2009

2008

2007

LaunchpadReleases (last edited 2010-12-10 14:34:55 by host81-152-147-180)