SeaMonkey 2.28 release delayed

[therube]

[2014-08-06]
> <Callek> hogarth: we're having build automation issues atm, and working on them
> <Callek> I'm *hoping* to have a 2.28 beta out ASAP
> <Callek> (yes I know we're a few weeks past the corresponding Firefox release at this time)
> <Callek> but I expect ASAP may even be this week or early next at this rate

[WaltS48]

From yesterday's meeting notes.

Callek plans to have at least one 2.28 beta as soon as we get the Linux builders up.

SeaMonkey 2.28 beta 1 and final are intended to follow within two weeks after last merge (i.e., by the time of this meeting), otherwise another 2.26.x update will follow

SeaMonkey: 2014-08-05 « Meeting Notes

So which is it going to be a 2.26.2 or indefinite wait for a 2.28?

Looks to me like a 2.26.2 should be soon.

[groze5858]

rsx11m is using SeaMonkey/2.29a2

a2 means it is a build on the Aurora development channel. Nightly would be a1 and Beta is b#. Nightly, Aurora, Beta and Release are the main development channels.

The Nightly builds of Firefox (like I am using) had a1 on end but they removed that sometime back and locked the build date in their attempt to make the useragent less unique like they did with the Releases. This of course makes it harder to do support.

I knew that James. Since the release of SeaMonkey is talking longer than normal, wouldn't it be better to use SeaMonkey Aurora 2.29a2 since it would have security update patches then 2.26.1 release version? I realize the Aurora version could be buggy. Also, there is no beta to download-yet.

[4td8s]

Looks to me like a 2.26.2 should be soon.

maybe. if SM 2.28 isn't going to be released on Tue. 8/12, that would be 3 weeks after FF 31 was released.
clock is ticking again...

[Buzzrr]

TICK, TOCK, TICK, TOCK...the clock is ticking! what is the latest status on SM 2.28 (if any)?

Yes, I feel like we're sitting on a time bomb here!

Seems to be three critical vulnerabilities in version 2.26.1. Are these something that common users would encounter?
Microsoft has just patched Windows and Adobe with Flash. What is the hold up for the next version of Sea Monkey

[4td8s]

TICK, TOCK, TICK, TOCK...the clock is ticking! what is the latest status on SM 2.28 (if any)?

Yes, I feel like we're sitting on a time bomb here!

Seems to be three critical vulnerabilities in version 2.26.1. Are these something that common users would encounter?
Microsoft has just patched Windows and Adobe with Flash. What is the hold up for the next version of Sea Monkey

seems like the "build" machines that make the SM releases (for linux & windows) aren't working lately or at least aren't working correctly. truly disappointing that 2.28 won't be released on time and the next release of Firefox (which is FF32) is about two weeks away. oh well. ticky tock, ticky tock (clock is ticking again).

[WaltS48]

Release Train

The plan will to concentrate on delivering 2.29 and potentially a security release for 2.26.
Callek / ewong will post / blog about it soon.

REF: SeaMonkey/StatusMeetings/2014-08-19 - MozillaWiki

[Buzzrr]

SeaMonkey 2.28 Changelog

[patrickjdempsey]

FYI, there will be no 2.28. It's being skipped to make time for a final 2.29 release, which will likely be somewhat late. Also any l10n string changes since 2.26.1 are being skipped to ease the build process:
http://codeverge.com/mozilla.dev.apps.s ... -s/1997934

[4td8s]

thanks for the info patrickjdempsey.

marking this SM 2.28 thread as RESOLVED WONTFIX (failure to launch) as SM 2.28 is cancelled - hee hee!
I'll go on beta testing the 2.29 betas now.

[JodyThornton]

A wee bit off topic, but related.
Is a v3.0 on the horizon? What changes would be expected when that happens?

[therube]

Sure, right after 2.99.
Changes? If everything goes as planned, all will look as it does now, though whats under the hood will be all new.
Though we've got some time before we get there. So if you're finding this (now) 2.29 a long time comin' ...

[JodyThornton]

Well there doesn't have to necessarily be that many 2.x releases. Didn't Seamonkey turn over from v1.19 to v2.0? It didn't go to v1.99. And that was nearly five years ago. Despite my hating the Firefox rapid release cycle, I am looking forward to something new in Seamonkey sometime soon.

[James]

Well SeaMonkey 2.1 was on same Gecko 2.0.1 as Firefox 4.0.1 and since Firefox 5.0 was the start of the rapid release scheme I guess SeaMonkey just continued using the 2.X.x version since as SM 2.2 was on same 5.0 Gecko as Fx 5.0, SM 2.3 was on 6.0.

[truffle]

Well there doesn't have to necessarily be that many 2.x releases. Didn't Seamonkey turn over from v1.19 to v2.0? It didn't go to v1.99. And that was nearly five years ago. Despite my hating the Firefox rapid release cycle, I am looking forward to something new in Seamonkey sometime soon.

That is true, but it is exactly when you have "something new" that you do 3.x while just by going to version 3.x doesn't give you "something new".
The real question you are asking should be: when will we see "something new" in Seamonkey?
And the answer is probably "when they'll have something new".

Ah and keep in mind that, although it won't likely be the case, after 2.99 there is 2.100, then 2.101, then 2.102 and so on.