Closed Bug 506230 Opened 15 years ago Closed 15 years ago

new version is not offered to beta users automatically or via "check for updates"

Categories

(Mozilla Messaging Graveyard :: Release Engineering, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: junk, Unassigned)

References

Details

Attachments

(2 files, 2 obsolete files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1) Gecko/20090715 Firefox/3.5.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2

Beta users are the ones doing the testing so what's the point of not giving them the new version when it comes out? People are commenting on the forums that they have to uninstall, download the new version and reinstall.

Today is the 24th; I still don't have b3 update available so I've gone and downloaded it myself.

Reproducible: Always

Steps to Reproduce:
1. Use the beta
2. new version is released
3. wait for automatic notice or "check for updates" manually
Actual Results:  
No update available.

Expected Results:  
I get the update so I can continue helping test!
This was in progress, not quite sure what the status of it is.
Status: UNCONFIRMED → NEW
Component: General → Release Engineering
Ever confirmed: true
Product: Thunderbird → Mozilla Messaging
QA Contact: general → release
Version: unspecified → other
The updates are available in the betatest channel, and QA has signed off on them. It's just a matter of getting approval to move them to the 'beta' channel to have them offered to users.
It's a beta release so why hold it back at all from current beta users? They're already on the beta testing bandwagon and know the deal, not on stable releases.
(In reply to comment #3)
> It's a beta release so why hold it back at all from current beta users? They're
> already on the beta testing bandwagon and know the deal, not on stable
> releases.

We have to verify that the updates work correctly. Would you really like us to provide an upgrade and just break your Thunderbird beta build completely?
Comment on attachment 390820 [details] [diff] [review]
Patcher configuration for Thunderbird 3.0 Beta 3

http://hg.mozilla.org/comm-central/file/THUNDERBIRD_3_0b3_RELEASE/mail/locales/shipped-locales says 'is' was shipped, but I don't see it here.
Attachment #390820 - Flags: review?(bhearsum) → review-
Previous patch included unrelated changes
Attachment #390835 - Attachment is obsolete: true
Attachment #390837 - Flags: review?(bhearsum)
Attachment #390835 - Flags: review?(bhearsum)
(In reply to comment #6)
> (From update of attachment 390820 [details] [diff] [review])
> http://hg.mozilla.org/comm-central/file/THUNDERBIRD_3_0b3_RELEASE/mail/locales/shipped-locales
> says 'is' was shipped, but I don't see it here.

That's absolutely correct, it somehow slipped thru the cracks.
Attachment #390820 - Attachment is obsolete: true
Attachment #390838 - Flags: review?(bhearsum)
Attachment #390837 - Flags: review?(bhearsum) → review-
Comment on attachment 390837 [details] [diff] [review]
[checked in] update-verify patch for Thunderbird 3 Beta 3 v2

You've included ja in the mac file and ja-JP-mac in the others. r=bhearsum with those removed.
Attachment #390838 - Flags: review?(bhearsum) → review+
There are 4 locales with issues, ca, en-GB, ko and sq. The problem is that at some point in the past, there was a release they were not part of, creating a gap.

ca:3.0a3 (3.0b1) 3.0b2 3.0b3
en-GB:3.0b1 (3.0b2) 3.0b3
ko:3.0a2 (3.0a3) 3.0b1 3.0b2 3.0b3
sq:3.0b1 (3.0b2) 3.0b3

And when that's the case, releases prior to the gap will not get an update offered to 3.0b3. Looks like a patcher bug/feature I need to track down.
Clarification, only locales that were not included in 3.0b2 are having this problem, so that's:

en-GB:3.0b1 (3.0b2) 3.0b3
sq:3.0b1 (3.0b2) 3.0b3
With a helpful suggestion by bhearsum on #build, I was able to generate partial+complete updates for the 2 misbehaving locales successfully.

They are also published in the betatest update channel now.

I've completed running the update verification scripts for all platforms, and the only complaints are for the locales that are genuinely missing.

That makes this bug r=Standard8 based on a conversation on irc.
Depends on: 504145
Attachment #390837 - Attachment description: update-verify patch for Thunderbird 3 Beta 3 v2 → [checked in] update-verify patch for Thunderbird 3 Beta 3 v2
Comment on attachment 390838 [details] [diff] [review]
[checked in] Patcher configuration for Thunderbird 3.0 Beta 3 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.2; previous revision: 1.1
done
Attachment #390838 - Attachment description: Patcher configuration for Thunderbird 3.0 Beta 3 v2 → [checked in] Patcher configuration for Thunderbird 3.0 Beta 3 v2
Updates are ready to go and will be pushed to aus2.mozilla.org tomorrow, Thursday July 30th at 10am EDT.
(In reply to comment #15)
> Updates are ready to go and will be pushed to aus2.mozilla.org tomorrow,
> Thursday July 30th at 10am EDT.

Updates have been pushed out.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: