Closed
Bug 584679
Opened 14 years ago
Closed 14 years ago
Release notes link in update snippets should support beta periods
Categories
(Mozilla Messaging Graveyard :: Release Engineering, defect)
Mozilla Messaging Graveyard
Release Engineering
Tracking
(blocking-thunderbird3.1 .5+, thunderbird3.1 .5-fixed)
RESOLVED
FIXED
People
(Reporter: standard8, Assigned: gozer)
References
Details
(Whiteboard: [non-code])
Attachments
(3 files, 2 obsolete files)
2.15 KB,
patch
|
standard8
:
review+
|
Details | Diff | Splinter Review |
1.67 KB,
patch
|
standard8
:
review+
|
Details | Diff | Splinter Review |
1.22 KB,
patch
|
bhearsum
:
review+
nthomas
:
review+
|
Details | Diff | Splinter Review |
We keep getting complaints about this every time we do a beta period on a maintenance release, so it is time we should do something about it. The update snippets contain a URL that points to the release notes for the final release e.g. http://www.mozillamessaging.com/%locale%/thunderbird/3.1.2/releasenotes/ So when we push to beta channel, the person gets a link to "View more information about this update" and this is then 404 and they get confused. The code is at: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/tools/patcher-configs/moz192-thunderbird-branch-patcher2.cfg&rev=1.15&mark=14 I assume the release patching code is the bit that updates the version. Could we change this to a live url, so that we can redirect to the beta pages during the beta period and then to the actual release once we've released? For its Help -> Release Notes menu option, Thunderbird currently uses: http://live.mozillamessaging.com/%APP%/releasenotes?locale=%LOCALE%&version=%VERSION%&os=%OS%&buildid=%APPBUILDID% Could we use something like: http://live.mozillamessaging.com/thunderbird/releasenotes?locale=%locale%&version=3.1.2 It looks like we can't use OS or buildid parameters as Thunderbird doesn't support in-app replacements for this url - the %locale% is replaced by the patcher tool or aus.
Assignee | ||
Comment 1•14 years ago
|
||
(In reply to comment #0) > We keep getting complaints about this every time we do a beta period on a > maintenance release, so it is time we should do something about it. < [...] > > Could we use something like: > > http://live.mozillamessaging.com/thunderbird/releasenotes?locale=%locale%&version=3.1.2 Absolutely! > It looks like we can't use OS or buildid parameters as Thunderbird doesn't > support in-app replacements for this url - the %locale% is replaced by the > patcher tool or aus. Looking at the patcher source in MozAUSLib.pm, looks like it can substibute %platform% too, but not buildid. So might want to at least include that platform, if only for tracking.
Assignee: nobody → gozer
Status: NEW → ASSIGNED
Reporter | ||
Comment 3•14 years ago
|
||
gozer: ping, can you get this fixed for the next please?
blocking-thunderbird3.0: --- → .8+
blocking-thunderbird3.1: --- → .4+
Assignee | ||
Comment 4•14 years ago
|
||
Attachment #470842 -
Flags: review?(bugzilla)
Assignee | ||
Comment 5•14 years ago
|
||
Attachment #470842 -
Attachment is obsolete: true
Attachment #470843 -
Flags: review?(bugzilla)
Attachment #470842 -
Flags: review?(bugzilla)
Assignee | ||
Comment 6•14 years ago
|
||
Attachment #470844 -
Flags: review?(bugzilla)
Assignee | ||
Comment 7•14 years ago
|
||
We'd like our detail urls in update offers to include the buildid, and currently, patcher doesn't support %buildid% substitution in these urls.
Attachment #470845 -
Flags: review?(bhearsum)
Assignee | ||
Comment 8•14 years ago
|
||
Sorry, wrong patch. s/buildid/platform/ in the previous comment. We want *platform* in the detail url.
Attachment #470845 -
Attachment is obsolete: true
Attachment #470848 -
Flags: review?(bhearsum)
Attachment #470845 -
Flags: review?(bhearsum)
Reporter | ||
Comment 9•14 years ago
|
||
Comment on attachment 470843 [details] [diff] [review] [checked in] Update our existing patcher configs to use the new URLs v2 r=Standard8 (though I'm also happy for a non-%platform% version if we don't get the platform patch in for next time we need this).
Attachment #470843 -
Flags: review?(bugzilla) → review+
Reporter | ||
Comment 10•14 years ago
|
||
Comment on attachment 470844 [details] [diff] [review] [checked-in] Update release configuration to specify our new detail URL r=Standard8 (though I'm also happy for a non-%platform% version if we don't get the platform patch in for next time we need this).
Attachment #470844 -
Flags: review?(bugzilla) → review+
Comment 11•14 years ago
|
||
Comment on attachment 470848 [details] [diff] [review] Add %platform% substitution to patcher in detail urls Seems fine. You're going to have to deal with an UPDATE_PACKAGING tag change, though. I'm OK with just moving the UPDATE_PACKAGING_R12 tag on patcher2.pl to include this. Nick, what do you think?
Attachment #470848 -
Flags: review?(nrthomas)
Attachment #470848 -
Flags: review?(bhearsum)
Attachment #470848 -
Flags: review+
Assignee | ||
Comment 12•14 years ago
|
||
Comment on attachment 470843 [details] [diff] [review] [checked in] Update our existing patcher configs to use the new URLs v2 Checking in moz19-thunderbird-branch-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/moz19-thunderbird-branch-patcher2.cfg,v <-- moz19-thunderbird-branch-patcher2.cfg new revision: 1.28; previous revision: 1.27 done Checking in moz192-thunderbird-branch-patcher2.cfg; /cvsroot/mozilla/tools/patcher-configs/moz192-thunderbird-branch-patcher2.cfg,v <-- moz192-thunderbird-branch-patcher2.cfg new revision: 1.17; previous revision: 1.16 done
Attachment #470843 -
Attachment description: Update our existing patcher configs to use the new URLs v2 → [checked in] Update our existing patcher configs to use the new URLs v2
Assignee | ||
Comment 13•14 years ago
|
||
Comment on attachment 470844 [details] [diff] [review] [checked-in] Update release configuration to specify our new detail URL comparing with ssh://hg.mozilla.org/build/buildbot-configs searching for changes changeset: 2929:9188c151ca2e tag: tip user: Philippe M. Chiasson <gozer@mozillamessaging.com> date: Wed Sep 01 16:35:47 2010 -0400 summary: Bug 584679 - Update release configuration to specify our new detail URL r=Standard8
Attachment #470844 -
Attachment description: Update release configuration to specify our new detail URL → [checked-in] Update release configuration to specify our new detail URL
Comment 14•14 years ago
|
||
Comment on attachment 470848 [details] [diff] [review] Add %platform% substitution to patcher in detail urls That's OK for a small change like this. One of these years we'll make it easier to version all changes properly by breaking out patcher (or whatever replaces it) from the main code base.
Attachment #470848 -
Flags: review?(nrthomas) → review+
Reporter | ||
Updated•14 years ago
|
blocking-thunderbird3.0: .8+ → .9+
blocking-thunderbird3.1: .4+ → .5+
Reporter | ||
Comment 15•14 years ago
|
||
So can we get the core patch landed into patcher please?
Reporter | ||
Updated•14 years ago
|
Whiteboard: [non-code]
Comment 16•14 years ago
|
||
Comment on attachment 470848 [details] [diff] [review] Add %platform% substitution to patcher in detail urls Checking in patcher2.pl; /cvsroot/mozilla/tools/patcher/patcher2.pl,v <-- patcher2.pl new revision: 1.40; previous revision: 1.39 done cvs tag UPDATE_PACKAGING_R12 patcher2.pl W patcher2.pl : UPDATE_PACKAGING_R12 already exists on version 1.39 : NOT MOVING tag to version 1.40 cvs tag -F UPDATE_PACKAGING_R12 patcher2.pl T patcher2.pl
Assignee | ||
Comment 17•14 years ago
|
||
Reminder: We need to update our release configuration to UPDATE_PACKAGING_R12 if we want to benefit from this.
Assignee | ||
Comment 18•14 years ago
|
||
changeset: 3064:6217ca5c40ef tag: tip user: Philippe M. Chiasson <gozer@mozillamessaging.com> date: Mon Oct 04 13:15:30 2010 -0400 summary: Bug 584679 - Update to UPDATE_PACKAGING_R12 for patcher to expand %platform% in snippets
Assignee | ||
Updated•14 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Updated•14 years ago
|
blocking-thunderbird3.0: .9+ → ---
status-thunderbird3.1:
--- → .5-fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•