Closed
Bug 917966
Opened 11 years ago
Closed 11 years ago
Lightning 2.6 release packages advertise wrong version number
Categories
(Calendar :: Build Config, defect)
Calendar
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
2.6.1
People
(Reporter: Fallen, Assigned: Fallen)
References
Details
(Whiteboard: [wanted-2.6.x])
When I manually changed the version in install.rdf, I forgot to do so in application.ini and the useragent pref.
> $ grep -r 2.6b3 *
> application.ini:Version=2.6b3
> defaults/preferences/lightning.js:pref("calendar.useragent.extra",
This needs fixing for 2.6.1
Comment 1•11 years ago
|
||
Could you please bump the version number on comm-esr24 to ensure that 2.6.* test builds are not updated 'back' to 2.6 by Thunderbird?
Assignee | ||
Comment 2•11 years ago
|
||
Ah the builds have already started on Thunderbird infra, didn't think to check the version number in the repo, I though this would be more of an issue of me making sure that if I need to change the version number for any reason, I do so in all locations.
Assignee | ||
Comment 3•11 years ago
|
||
I've changed my script to accommodate the remaining files. No more traces of 2.6b3.
oskar:release kewisch$ changeversion.sh lightning-win32.xpi 2.6.1
Changing 2.6b3 to 2.6.1
install.rdf
application.ini
defaults/preferences/lightning.js
Saved to lightning-win32.xpi
oskar:release kewisch$ mkdir ttt
oskar:release kewisch$ cd ttt
oskar:ttt kewisch$ unzip -q ../lightning-mac.xpi
oskar:ttt kewisch$ grep -r 2.6b3 *
oskar:ttt kewisch$
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2.6.1
Comment 4•11 years ago
|
||
Nevertheless please update comm-esr24 to ensure that users who pull the source or download the source code tarball will get the proper version and build.
Assignee | ||
Comment 5•11 years ago
|
||
I've done so for the next possible release in https://hg.mozilla.org/releases/comm-esr24/rev/059874c5f58b
Mark, would it be ok to also change the version on the relbranch for 24.0.1 and retag _BUILD1 and _RELEASE?
You need to log in
before you can comment on or make changes to this bug.
Description
•