On 9/28/2011 7:48 AM, Jim Taylor wrote:
Jens Hatlak wrote:
Philip TAYLOR (Webmaster, Ret'd) wrote:
Justin Wood (Callek) wrote:
> It was deemed for Firefox not to upgrade from "last beta" to
"release", I decided to follow suit.
> I will be building 2.5b1 ASAP, and our b3 will upgrade to that.
I am not a beta tester, so blissfully unaffected by this.
Right, and the fact that your are not a beta tester explains that you
don't understand the reasoning.
I am a beta user who also did not like not getting the upgrade to final
offer. I normally run the beta on my laptop (which gets the most use)
and the stable on my desktops. When I got the 2.4 upgrade notice on my
desktop, before upgrading I checked for updates on my 2.4b3 laptop and
their weren't any. Strange, so I checked the byte count and md5sum of
the b3 and release to see if per chance nothing had changed, and they
were not identical. So I downloaded 2.4 final to my laptop and installed
it which takes me off the beta channel. I don't upgrade anything on the
desktops until I've tested it because they are not backed up as often.
So by not offering the final upgrade to the beta channel you have lost
at least one beta tester until/if I explicitly download and install a
beta. And as alternate browser user going back to Mosaic I too don't
agree with many of the Mozilla developers decisions (think about
it....if splitting the suite had been a good decision there would be no
SeaMonkey) so don't think doing what they do is necessarily good.
To elaborate on the reasoning slightly:
*2.4 final is code-wise equal to 2.4b3, the compile process causes
different md5sums though, so that is why they don't binary compare equal.
*The process to create updates to the release-channel build from the
beta channel build is manual and more prone to have issues.
Given both of those, the cost/benefit of updating beta users to the
release build is low, since the largest reasons we even create a new
build on the release repo is:
* have about:buildconfig and the tag to be the final tag on the release
repo.
* Have the built-in update channel be "release".
When we build the final release build, the update channel is always
release, but that doesn't change for anyone who upgrades with a
different channel. But is a problem if beta3 is not to be our final
beta, and why we treat beta's as rc's.
Hope That Helps
--
~Justin Wood (Callek)
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
