Closed Bug 768576 Opened 12 years ago Closed 12 years ago

Please create custom 12.0->13.0.1 partial updates to help with uptake rate

Categories

(Release Engineering :: Release Requests, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: akeybl, Assigned: nthomas)

References

Details

Attachments

(3 files, 2 obsolete files)

Please create custom 12.0->13.0.1 partial updates to help with uptake rate. QA will test on releasetest once prepared. Thanks!
Assignee: nobody → nrthomas
Priority: -- → P2
Attached file patcher config
This is based on rev 1.33 from the 13.0.1 release, with 
* 13.0 -> 12.0 in <current-update>
* dropping unwanted past-update lines and unrelated release blocks
* leaving out linux as the user counts are very low and it makes everything take twice as long
Attached file working notes (obsolete) —
This is what I did to generate the partials, more complicated than expected.

Still to do
* QA to check betatest
* me to look at the update verify output
* run the code here to regenerate the checksums (mostly tested)
* add product and locations to bouncer
* push to mirrors
* wait for uptake, QA verifies releastest
* push to release channel

I'd like to be involved in that so please wait for me, thanks.
(In reply to Nick Thomas [:nthomas] from comment #3)
> Still to do
> * QA to check betatest

I think we need to test this by automation so we can get a wide locale/platform coverage. Our automation can cover all platforms and 6 locales in a couple of hours -- the same testing manually will take a few days. Unfortunately our couchDB instance (where we publish results) is currently down. I've filed bug 769004 to get that resolved ASAP. I'm hoping we can get this back up today.

I apologize for the delay.
Depends on: 769004
(In reply to Nick Thomas [:nthomas] from comment #3)
> Still to do
> * QA to check betatest

Automation has completed successfully on betatest:
https://wiki.mozilla.org/Releases/Firefox_13/Test_Plan#12.0_to_13.0.1_Partial_Updates

Locales checked:
en-US, de, es-ES, fr, it, ja-JP, ko, pt-BR, ro, ru, zh-TW

Note that I have not done any additional spotchecking like automatic updates, what's new pages, add-on compatibility, etc. Please let me know if you think this is necessary. Otherwise, I think we are good to move forward.
Our automated checks look good too, so I'll move ahead with the final staging (checksums, bouncer etc)
Depends on: 769090
Attached file working notes, v2 (obsolete) —
Updated notes. At this point the files are on the mirrors and we have uptake. QA has bug 769090 to figure out before signing off on releasetest.

Still need to regenerate the *SUMS files + sign (which isn't working because the builder keeps running with FIREFOX_13_0_2_RELEASE), push that out to the mirrors, backupsnip and pushsnip for the release snippets.
Attachment #637094 - Attachment is obsolete: true
No longer depends on: 769090
Depends on: 769156
Snippets on releasetest now look good:
http://mozmill-ondemand.blargon7.com/#/update/detail?branch=13.0&channel=releasetest&from=2012-06-28&to=2012-06-28&target=13.0.1

Note that the failures are from earlier testing around bug 769156. There is no easy way to filter these out without deleting each result from the DB by hand. We can push these to release.
Updates on release channel look good -- sending the final sign-off email now.
Attached file Final notes
With the fixed process for regenerating the checksum files. That will be massively easier normally because we won't have the next release hanging around.
Attachment #637373 - Attachment is obsolete: true
All done.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: