Closed
Bug 386195
Opened 17 years ago
Closed 17 years ago
Bump version number for Sunbird and Lightning nightly builds after release
Categories
(Calendar :: Build Config, defect)
Calendar
Build Config
Tracking
(Not tracked)
VERIFIED
FIXED
0.7
People
(Reporter: ssitter, Assigned: ssitter)
References
Details
Attachments
(1 file)
1.30 KB,
patch
|
mvl
:
review+
|
Details | Diff | Splinter Review |
Now that 0.5 is released the version number for Sunbird and Lightning nightly builds should be bumped.
Open point: What version number should be used? Recent proposals were
1.8 branch: "0.7pre" or "0.7branch"
trunk: "0.7trunk"
Comment 1•17 years ago
|
||
Given the idea that we want to keep on focussing on branch for a while, i'd say that we can keep trunk as is: 0.6a1 (or whatever it is that starts with 0.6). That makes it at least look older then the current branch builds.
Assignee | ||
Comment 2•17 years ago
|
||
Patch is for MOZILLA_1_8_BRANCH only and also contains the fix for Bug 385572.
Comment 3•17 years ago
|
||
Comment on attachment 270345 [details] [diff] [review]
switch to 0.7pre on MOZILLA_1_8_BRANCH
r=mvl
Attachment #270345 -
Flags: review?(mvl) → review+
Assignee | ||
Comment 4•17 years ago
|
||
I'd like you to checkin the patch for me please.
Now we only need to decide what to do on Trunk.
Whiteboard: [checkin needed]
Comment 5•17 years ago
|
||
Fix checked in:
Checking in app/module.ver;
/cvsroot/mozilla/calendar/sunbird/app/module.ver,v <-- module.ver
new revision: 1.7.2.10; previous revision: 1.7.2.9
done
Checking in config/version.txt;
/cvsroot/mozilla/calendar/sunbird/config/version.txt,v <-- version.txt
new revision: 1.5.2.9; previous revision: 1.5.2.8
done
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Whiteboard: [checkin needed]
Updated•17 years ago
|
Target Milestone: --- → 0.7
Assignee | ||
Comment 6•17 years ago
|
||
(In reply to comment #5)
Simon, does this also mean we have a decision for Trunk version number?
Comment 7•17 years ago
|
||
No, you're right, we have no solution for trunk right now, although I agree with mvl that staying with 0.6a1 is probably no bad idea.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 8•17 years ago
|
||
After short discussion on IRC we decided to keep 0.6a1 for trunk builds. I'll therefore add 0.7* as branch version in Bug 386420. Setting back to FIXED.
Status: REOPENED → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•17 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•