MozillaZine

SeaMonkey 2.18 release has been cancelled

Discussion of general topics about Seamonkey
rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 14th, 2013, 6:28 am

Bad news: Due to a catastrophic hardware failure, the buildmaster (i.e., the "thing" that controls the buildbots doing the actual release builds) for SeaMonkey is down, thus it is not possible at the moment to do any releases (or nightly builds, for that matter). The virtual machine is an older architecture, thus cannot be easily transplanted onto a different physical machine.

From today's meeting minutes:
  • Due to hardware failure, SeaMonkey 2.18b5 and SeaMonkey 2.18 are cancelled.
  • Instead will go directly to 2.19 series of betas and by the 24th June, the 2.19 final. This means that users of 2.17.1 will be going directly to 2.19.
  • If Firefox decides to do a dot release, we might go for a 2.18 later.

Meaning, you'll have to stick with 2.17.1 for the time being. An alternative may be 2.18 beta 4, which was released early May, but may not have all the security patches that went into the Gecko 21.0 branch.

xed

User avatar
 
Posts: 669
Joined: February 11th, 2007, 12:04 pm

Post Posted May 14th, 2013, 9:51 am

Okay, glad to know this. I have no problem not updating for a while.
"Doin' right ain't got no end." Cap'n Red Legs

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 14th, 2013, 11:45 am

Here the list of security fixes missing since 2.17.1, which were supposed to be fixed by 2.18:
  • MFSA 2013-48* Memory corruption found using Address Sanitizer
  • MFSA 2013-47 Uninitialized functions in DOMSVGZoomEvent
  • MFSA 2013-46* Use-after-free with video and onresize event
  • MFSA 2013-45 Mozilla Updater fails to update some Windows Registry entries
  • MFSA 2013-44 Local privilege escalation through Mozilla Maintenance Service
  • MFSA 2013-43 File input control has access to full path
  • MFSA 2013-42 Privileged access for content level constructor
  • MFSA 2013-41* Miscellaneous memory safety hazards (rv:21.0 / rv:17.0.6)
*(critical)

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 15th, 2013, 4:42 am

http://blog.drapostles.org/archives/95 wrote:SeaMonkey 2.18 – Where are you?
Posted on May 14, 2013 by Callek

Hey Everyone,

So SeaMonkey 2.18 was supposed to be out today, so where is it?

We have had a hardware error in the systems that allow us to reliably generate the release — Without these systems anything we create will be of unknown quality/stability.

In order to meet our own quality and stability requirements we are NOT releasing SeaMonkey 2.18.

While there is a chance we could have these systems back up in time to do an intermediate release (say something corresponding to a possible Gecko 21.0.1) we can not promise nor plan for it at this time.

We are actively working on repairing the system and its data, once that is complete we will go forth with a new BETA based on the SeaMonkey 2.19 train, and we expect to release SeaMonkey 2.19 on time, on June 25′th.

We thank you for your understanding.

CMonkeyBloke

User avatar
 
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Post Posted May 15th, 2013, 8:48 am

Yeah, suits me fine as well. I'm in no hurry.

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 15th, 2013, 8:58 am

Seems you guys like to stick with security holes? ;-)

Let's hope it won't take 6 weeks to get the new build system up and running...
Relevant action can be followed in bug 827079 (I guess).

CatThief

User avatar
 
Posts: 1854
Joined: January 19th, 2004, 12:19 am
Location: Northeast USA

Post Posted May 15th, 2013, 6:46 pm

Seriously? No fallback in place anywhere? Hardware always fails eventually. Best wishes with the recovery! :shock:
Still passionate for Mozilla themes and extensions, just not actively developing them for public release anymore.

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 15th, 2013, 8:15 pm

Yes, I was surprised too. Apparently moving the Parallels VMs from one machine to another isn't trivial (in contrast to the VMware ones which you can just copy), and they can't be used for the newer ESX-based systems. Anyway, one would assume that Mozilla has spare Macs around, but it's not clear to me what the allocation for the individual projects is (and the lack of hardware has been a problem for the SeaMonkey project in the past, such as getting official 64-bit builds running). The "recovery" will be setting up the buildmaster from scratch in the new VM environment (which will hopefully make issues like this more flexible in the future).

Disclaimer: Nothing I write here is "official" except for the verbatim quotes (I have no clue how the build system works, just my personal impression and thoughts from following the discussion).

vazhavandan
 
Posts: 739
Joined: December 10th, 2007, 8:27 am

Post Posted May 15th, 2013, 8:41 pm

HW failure is number one problem for software projects :( This happened to openSUSE 12.2 and the release got postponed by probably a couple of months.

xed

User avatar
 
Posts: 669
Joined: February 11th, 2007, 12:04 pm

Post Posted May 16th, 2013, 12:41 am

rsx11m wrote:Seems you guys like to stick with security holes? ;-)

Let's hope it won't take 6 weeks to get the new build system up and running...
Relevant action can be followed in bug 827079 (I guess).

I'll use SeaMonkey for all my trusted browsing and if I need to, I'll break out Firefox.

No big deal to me.
"Doin' right ain't got no end." Cap'n Red Legs

Philip Chee

User avatar
 
Posts: 6475
Joined: March 1st, 2005, 3:03 pm

Post Posted May 16th, 2013, 3:32 am

MoCo has lots and lots of machines including Mac Minis. However we are not MoCo we are a small project hosted on Community machines maintained by Mozilla.

Phil

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 16th, 2013, 5:10 am

Yeah, they seem to be picky when it comes to hardware allocation...

CMonkeyBloke

User avatar
 
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Post Posted May 19th, 2013, 8:26 am

rsx11m wrote:Seems you guys like to stick with security holes? ;-)

Let's hope it won't take 6 weeks to get the new build system up and running...
Relevant action can be followed in bug 827079 (I guess).


There's security holes? :shock:

rsx11m
Moderator
 
Posts: 14412
Joined: May 3rd, 2007, 7:40 am
Location: US

Post Posted May 19th, 2013, 10:42 am

Sure, there always are and new ones keep cropping up... :?

I've posted a list in viewtopic.php?f=3&t=2704469#p12858839 above with the fixes that 2.17.1 is missing over the 2.18 no-show.

As said, I don't know which ones of those (if any) were fixed already in the last 2.18 beta 4 release before the build system broke.

CMonkeyBloke

User avatar
 
Posts: 677
Joined: June 10th, 2011, 11:35 am
Location: Annwn

Post Posted May 19th, 2013, 12:04 pm

rsx11m wrote:Sure, there always are and new ones keep cropping up... :?

I've posted a list in viewtopic.php?f=3&t=2704469#p12858839 above with the fixes that 2.17.1 is missing over the 2.18 no-show.

As said, I don't know which ones of those (if any) were fixed already in the last 2.18 beta 4 release before the build system broke.


OK thanks.

Return to SeaMonkey General


Who is online

Users browsing this forum: No registered users and 1 guest