As discussed, we will be releasing Lightning 1.0b4 from comm-central and will branch as soon as Thunderbird branches for 3.3. We will be skipping 1.0b3 so we have a free version number for the rare case that we want to also do a comm-1.9.2 branched release. Doing this will likely wreak havoc, so lets try to avoid that.
Changed version number in comm-central rev 19ab09dcea55
We are now running comm-miramar for the release. l10n builds are also working. The dashboard is being set up in bug 657314. Posted final string freeze at: http://groups.google.com/group/mozilla.dev.l10n/browse_thread/thread/3f4af96c3a624353#
Depends on: 657314
Shipped locales for 1.0b4: <http://hg.mozilla.org/releases/comm-miramar/file/653d6c77512a/calendar/locales/shipped-locales> l10n changesets: ca f01206d74820 cs 3aa855272e32 da 61cc55d17eae de f06a9f522157 en-GB 2c0fb16c8821 es-AR 79346ac83286 es-ES 930a2b7c71d5 et 41de8d2e6e80 eu aeaf879f25b5 fi db62ab7faf7f fr c728b98373f6 fy-NL f3e561fb0f7a ga-IE 708a97e7e7cb gd 31ee16942213 hu 5addeb4bfa61 id 52f65aad6c6a is dc5ff4fec014 it a4f8ace82bca ja 0bb679534816 ja-JP-mac 737544b3f92a lt 2110a7714e60 nb-NO 238fd2381f4a nl 8438d6ec5f7e nn-NO db33369d0262 pa-IN 145f8e6e4646 pl 4301c5770f79 pt-PT 635d25e11720 ru 025f10cc21d0 sk 24b78c23e0f2 sq cf1567bc7371 sr 995d77b43109 sv-SE 696dedde0283 tr a2c412ac02ce uk 7a24c8c63062 zh-CN 2565bbbde7b9 zh-TW 9930477ffe6e
We are using COMM50_20110620_RELBRANCH for our release.
Tagged CALENDAR_1_0b4_BUILD1: changeset: 7840:05be4111ee60 branch: COMM50_20110620_RELBRANCH tag: tip user: Philipp Kewisch <email@example.com> date: Tue Jun 21 12:58:00 2011 +0300 summary: Added tag CALENDAR_1_0b4_BUILD1 for changeset 653d6c77512a. CLOSED TREE, a=release
Tagged buildbot-configs and modified the config, but just for reference since we are doing things manually: changeset: 4335:9ebe3b0f4b46 tag: tip user: Philipp Kewisch <firstname.lastname@example.org> date: Tue Jun 21 14:16:23 2011 +0300 summary: Update l10n changesets for Lightning 1.0b4 CLOSED TREE changeset: 4336:1b8e613145d0 tag: tip user: Philipp Kewisch <email@example.com> date: Tue Jun 21 14:17:29 2011 +0300 summary: Added tag CALENDAR_1_0b4_BUILD1 for changeset 9ebe3b0f4b46
New l10n revs, the old ones were broken (thanks, l10n-dashboard!) ca ea7edaa3f814 cs 3aa855272e32 da 89c65297da4f de d581cb3d737d en-GB 2c0fb16c8821 es-AR 79346ac83286 es-ES d503376761e4 et 41de8d2e6e80 eu a2e95277661c fi db62ab7faf7f fr c728b98373f6 fy-NL f3e561fb0f7a ga-IE 4907c67875c0 gd 31ee16942213 hu 5addeb4bfa61 id 227656bbcf83 is dc5ff4fec014 it a4f8ace82bca ja 4e6be3dd5d38 ja-JP-mac c068da2f2b69 lt 2110a7714e60 nb-NO 1bb60e21a94e nl 8438d6ec5f7e nn-NO da6e8b87cda7 pa-IN 145f8e6e4646 pl 0c3004bb7369 pt-PT 635d25e11720 ru 025f10cc21d0 sk 24b78c23e0f2 sq cf1567bc7371 sr 995d77b43109 sv-SE 696dedde0283 tr 8cbeb54677fe uk 7a24c8c63062 zh-CN 2565bbbde7b9 zh-TW 9930477ffe6e
nn-NO is now ba012a1913e2
Will Bug 656350 be considered when creating the release package?
Linux32 is done mac32/64, win32 and linux64 is building I'll manually merge the linux builds this time, in the future I'm going to invest some time in the build system so we don't have these annoyances again.
Enough for today. Unfortunately, linux32 debug symbols seem to not be in the build I created. Need to investigate if this happens for the other builds too.
All platforms are ready, rc1 is released: http://weblogs.mozillazine.org/calendar/2011/06/lightning_10b4_release_candida.html I have debug symbols and I deeply hope that they are compatible with the builds I produced. I wish there was an easy way to test this!
Pushed a few bugfixes, now spinning 1.0b4rc2, which will be the final release. Lets hope there's nothing major!
Changed version numbers for seamonkey and gdata: Our release seems binary compatible with Seamonkey 2.1 and 2.2 ! changeset: 7856:0155ba75a323 branch: COMM50_20110620_RELBRANCH tag: tip parent: 7854:ec401a096a8c user: Philipp Kewisch <firstname.lastname@example.org> date: Mon Jun 27 20:37:27 2011 +0200 summary: Bug 639866 - Update version numbers for Lightning 1.0b4 release
Tagged: CALENDAR_1_0b4_BUILD2 and CALENDAR_1_0b4_RELEASE
linux and win32 builds are done and seem to work (thanks jhopkins, Lenni). Mac 32 bit is ready, 64 bit is building. The first files are being uploaded to AMO, lets hope there are no review/version number issues.
Lightning 1.0b4 is released! Unfortunately a previous crash is now exposed more, we've had a very high number of windows crashes (bug 603416). Also, I have a bad feeling about the alarms. Release notes are not uploaded yet, therefore not closing the bug yet.
(In reply to comment #17) > Release notes are not uploaded yet, therefore not closing the bug yet. The link to the release notes is apparently everywhere. We've gotten a number of people filing 404 bugs. They've all been duplicated to bug 668478, which I've now marked as blocking this bug.
Depends on: 668478
Release notes have been uploaded to the website. I've decided to not upload the release notes to AMO since I will release 1.0b5 with a few urgent bugfixes and thats more important right now. I'll upload the notes for both versions when 1.0b5 is released.
Lightning 1.0b4 and Lightning 1.0b5 have been released last month.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Target Milestone: --- → 1.0b4
You need to log in before you can comment on or make changes to this bug.