Closed
Bug 530100
Opened 15 years ago
Closed 15 years ago
Bump version numbers for 1.0b1 release
Categories
(Calendar :: Build Config, defect)
Calendar
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
1.0b1
People
(Reporter: Fallen, Assigned: Fallen)
References
Details
Attachments
(3 files)
860 bytes,
patch
|
mschroeder
:
review+
|
Details | Diff | Splinter Review |
867 bytes,
patch
|
mschroeder
:
review+
|
Details | Diff | Splinter Review |
1.67 KB,
patch
|
mschroeder
:
review+
|
Details | Diff | Splinter Review |
We need to bump version numbers for the release. Last I remember, we decided on 1.0b1 for Lightning and 1.0a1 for Sunbird. If this is still the case, then we need to also change some build files so that Lightning gets its dedicated version number.
Assignee | ||
Comment 1•15 years ago
|
||
Assignee | ||
Updated•15 years ago
|
Summary: Bump version numbers for 1.0[ab]1 release → Bump version numbers for 1.0b1 release
Comment 2•15 years ago
|
||
Comment on attachment 414511 [details] [diff] [review]
Fix - v1
r=mschroeder
Attachment #414511 -
Flags: review?(bugzilla) → review+
Assignee | ||
Comment 3•15 years ago
|
||
Pushed to comm-1.9.1 ONLY
<http://hg.mozilla.org/releases/comm-1.9.1/rev/1a5cbd27a100>
-> FIXED
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0
Comment 4•15 years ago
|
||
Shouldn't the version number be lowered on the release branch only and stay the same on the comm-1.9.1 branch?
Assignee | ||
Comment 5•15 years ago
|
||
Back when this was first checked in, we didn't have the relbranch. To me this makes sense too, not sure if it will cause problems with release automation. Should we give it a try?
Comment 6•15 years ago
|
||
Actually, release branch should be 1.0b1 and comm-1.9.1 should be 1.0b2pre
Comment 7•15 years ago
|
||
Attachment #416562 -
Flags: review?(philipp)
Comment 8•15 years ago
|
||
Comment on attachment 416562 [details] [diff] [review]
After beta1 cut
r=Fallen via IRC
Attachment #416562 -
Flags: review?(philipp) → review+
Comment 9•15 years ago
|
||
Comment on attachment 416562 [details] [diff] [review]
After beta1 cut
Pushed to comm-1.9.1 ONLY: http://hg.mozilla.org/releases/comm-1.9.1/rev/ceb149ba5a05
Assignee | ||
Comment 10•15 years ago
|
||
We need to modify the lightning versions on COMM1915_20091204_RELBRANCH, thanks to ssitter and mschroeder for the hint!
Attachment #416731 -
Flags: review?(mschroeder)
Comment 11•15 years ago
|
||
Comment on attachment 416731 [details] [diff] [review]
Lightning Versions for release branch
r=mschroeder
Attachment #416731 -
Flags: review?(mschroeder) → review+
Comment 12•15 years ago
|
||
Comment on attachment 416731 [details] [diff] [review]
Lightning Versions for release branch
Pushed to COMM1915_20091204_RELBRANCH on comm-1.9.1 ONLY: http://hg.mozilla.org/releases/comm-1.9.1/rev/268043de2ad1
Assignee | ||
Comment 13•13 years ago
|
||
These bugs are likely targeted at Lightning 1.0b1, not Lightning 1.0. If this change was done in error, please adjust the target milestone to its correct value. To filter on this bugspam, you can use "lightning-10-target-move".
Target Milestone: 1.0 → 1.0b1
You need to log in
before you can comment on or make changes to this bug.
Description
•