Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Status on Next Version?
37 views
Skip to first unread message
David E. Ross
May 29, 2013, 8:45:11 PM5/29/13
to
Would it be possible to post a message at least weekly in
mozilla.support.seamonkey regarding the current status of efforts to
resume development of SeaMonkey versions? It is been over a week since
I have seen anything about your hardware failure.
Followup-to set to mozilla.support.seamonkey.
--
David E. Ross
<http://www.rossde.com/>
Are taxes too high in the U.S.? Check the bar graph
at <http://www.rossde.com/taxes/trickling.html> to see.
mozilla.support.seamonkey regarding the current status of efforts to
resume development of SeaMonkey versions? It is been over a week since
I have seen anything about your hardware failure.
Followup-to set to mozilla.support.seamonkey.
--
David E. Ross
<http://www.rossde.com/>
Are taxes too high in the U.S.? Check the bar graph
at <http://www.rossde.com/taxes/trickling.html> to see.
Justin Wood (Callek)
Jun 17, 2013, 12:57:14 PM6/17/13
to
Justin Wood (Callek) wrote:
>
> * I'm still working on this.
> * Timing of the machine issue came at one of the worst possible times
> overall
> ** Our helper-release-engineer is in charge of a massive office colo
> move for his paid-job and can't really devote any time this/last week week.
> ** I was traveling for work last week
> ** I was sick for a few days the week before
> ** I had a close family member pass away today, and was on her way the
> past few days.
> * We have to juggle all this fixup time for our *free* time since we all
> have day jobs.
>
> It pains us to have this type of delay in getting any new version (beta
> or otherwise) out to you, but I will send more information along when we
> have things to share about progress.
>
STATUS UPDATE:
-DONE:
* the buildbot master has been imaged with the base os.
* We have gotten puppet working
-TODO:
* We have to bring up the buildbot master and set it up properly
<-----If we cut a few corners...
<-----at this point we can start spinning beta(s)/Releases
* We have to bring up clobberer (which the machines use to know when a
clobber is needed
* We have to tell our buildapi to report to the clobberer server so that
tbpl can report builds
After the last part is done I can reopen the trees, and I expect to be
building a beta as of tomorrow.
At this point the planned release date is AT RISK. Which means depending
on how smooth this beta goes, and how many users grab it and start
testing, as well as what, if any, reports of problems we get, we may
slip past the release date of the 24'th.
We however can be sure to not entirely skip this release, and will do a
release based on this train even if its late.
Thank You,
--
~Justin Wood (Callek)
> David E. Ross wrote:
>> Would it be possible to post a message at least weekly in
>> mozilla.support.seamonkey regarding the current status of efforts to
>> resume development of SeaMonkey versions? It is been over a week since
>> I have seen anything about your hardware failure.
>>
>> Followup-to set to mozilla.support.seamonkey.
>>
>
> Ok, not much status to share but I don't want to keep you guys in the dark.
>> Would it be possible to post a message at least weekly in
>> mozilla.support.seamonkey regarding the current status of efforts to
>> resume development of SeaMonkey versions? It is been over a week since
>> I have seen anything about your hardware failure.
>>
>> Followup-to set to mozilla.support.seamonkey.
>>
>
>
> * I'm still working on this.
> * Timing of the machine issue came at one of the worst possible times
> overall
> ** Our helper-release-engineer is in charge of a massive office colo
> move for his paid-job and can't really devote any time this/last week week.
> ** I was traveling for work last week
> ** I was sick for a few days the week before
> ** I had a close family member pass away today, and was on her way the
> past few days.
> * We have to juggle all this fixup time for our *free* time since we all
> have day jobs.
>
> It pains us to have this type of delay in getting any new version (beta
> or otherwise) out to you, but I will send more information along when we
> have things to share about progress.
>
STATUS UPDATE:
-DONE:
* the buildbot master has been imaged with the base os.
* We have gotten puppet working
-TODO:
* We have to bring up the buildbot master and set it up properly
<-----If we cut a few corners...
<-----at this point we can start spinning beta(s)/Releases
* We have to bring up clobberer (which the machines use to know when a
clobber is needed
* We have to tell our buildapi to report to the clobberer server so that
tbpl can report builds
After the last part is done I can reopen the trees, and I expect to be
building a beta as of tomorrow.
At this point the planned release date is AT RISK. Which means depending
on how smooth this beta goes, and how many users grab it and start
testing, as well as what, if any, reports of problems we get, we may
slip past the release date of the 24'th.
We however can be sure to not entirely skip this release, and will do a
release based on this train even if its late.
Thank You,
--
~Justin Wood (Callek)
David E. Ross
Jun 17, 2013, 1:23:46 PM6/17/13
to
Concerned about someone (e.g., the government)
snooping into your E-mail? Use PGP.
See my <http://www.rossde.com/PGP/>
Daniel
Jun 18, 2013, 5:24:58 AM6/18/13
to
I'm sure the SeaMonkey supporters will be glad for a new SM whenever
it's hot-to-trot!!
On a related point, for a couple of weeks or so, I've been using my Win7
SM beta, but, over the week-end, I switched back to using my Linux
version, and each night I've been told there is a SM 2.18b4 available
and offering to download the update, and it spins and it spins and it
spins!!
Is there some pref set for when the next Beta should be available?? If
not, any guess why I've been getting these update available screens??
--
Daniel
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:21.0) Gecko/20100101
Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130502201647
or
User agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:21.0)
Gecko/20100101 Firefox/21.0 SeaMonkey/2.18 Build identifier: 20130403022815
Justin Wood (Callek)
Jun 19, 2013, 12:02:08 AM6/19/13
to
> <-----If we cut a few corners...
> <-----at this point we can start spinning beta(s)/Releases
> * We have to bring up clobberer (which the machines use to know when a
> clobber is needed
> * We have to tell our buildapi to report to the clobberer server so that
> tbpl can report builds
the amount I got done was less than I was hoping, so I didn't do any of
those corner cuts that will allow me to spin a beta, and I have no idea
yet on how much further (if anything) I'll get tonight.
HOWEVER the master is up, and running, and running jobs (we did a
blocklist update which pushed to the tree already!) so there is a
*chance* you'll get nightlies as of now.
There is also a good chance you won't, since clobberer is not working
atm, at all!.
You can follow along for further progress in:
* Bug 845843 - for the master itself
* Bug 883470 - for our beta timing/information.
I'll continue to post updates here until we're back on our normal schedule.
--
~Justin Wood (Callek)
0 new messages