Closed Bug 685528 Opened 9 years ago Closed 9 years ago

Sort out nightly version numbers and remove links to latest miramar

Categories

(Calendar :: Build Config, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Fallen, Assigned: Fallen)

Details

I have read we have nightly builds with the same version number. I haven't actually verified this, but in any case we should

1) Make sure our nightly builds have differing versions
2) Remove the latest-comm-miramar softlink from stage.m.o.
Current version on comm-beta: 1.0b6pre, comm-aurora: 1.1a1pre, comm-central: 1.1a1pre.

As long as 1.0 is not released I would suggest to use 1.0bXpre with X matching the current Mozilla / Thunderbird version. For example 1.0b7pre, 1.0b8pre, 1.0b9pre for the current development branches.
OS: Mac OS X → All
Hardware: x86 → All
So comm-aurora = 1.0b7pre comm-central = 1.0b8pre ? Or should we add one to match tb versions? (comm-beta = 1.0b7pre, comm-aurora = 1.0b8pre, comm-central = 1.0b9pre)

On the one hand, this would be good for merges and I don't think moving from 1.1a1pre to 1.0b9pre should be much of an issue, but on the other hand, we don't want to stay with betas longer than needed, so if all goes well the current beta or aurora will be 1.0 and central could stay 1.1a1pre. This way we don't have to tell users to "downgrade".

Stefan, what do you think?
I'd go with comm-beta = 1.0b7pre, comm-aurora = 1.0b8pre, comm-central = 1.0b9pre for now. If we decide to relabel one of the next releases to 1.0 during release we can just raise the versions on all newer branches. I don't think that we have to tell comm-central users to downgrade, they will just download the comm-central nightly as usual and probably don't recognize the new number at all.
Ok, lets do it:

comm-central rev a848392254ef
comm-aurora rev 7e2d74761334
comm-beta rev b55ae861a766

and comm-miramar links removed. Also filed bug 685696 to add/change bugzilla fields.
Assignee: nobody → philipp
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b6
You need to log in before you can comment on or make changes to this bug.