SeaMonkey/StatusMeetings/2016-03-15: Difference between revisions

(→‎Feature List, Planning: updated counts)
Line 58: Line 58:
<br/>
<br/>
* SeaMonkey 2.39 was released November 8th, 2015.
* SeaMonkey 2.39 was released November 8th, 2015.
* '''SeaMonkey 2.40 final (tracking {{bug|1233615}}) was released March 14, 2016'''
* '''SeaMonkey 2.40 final (tracking {{bug|1233615}}) was partially released March 14, 2016'''
<!-- I leave it up to Ratty and ewong to update the rest on the 2.40 release -->
<!-- I leave it up to Ratty and ewong to update the rest on the 2.40 release -->
** 2.40 is currently mired in a swamp so deep it makes the Marianna Trenches look like a shallow pool.
** Updating failed due to PEBKACCurrently rectifying this issue.
*** Uploading is not the problem.  It's the problem of the following facts:
 
**** The S3 migration did away with our stage.mo site. (It is gone)
**** Our stage.mo site scripts depended entirely on stage.mo. 
**** We need to redo our scripts to play 'pass the bucket' on the S3 server, which requires some S3 figuring out.
** Without Callek, we are stuck.
** build #4 are up for all platforms and locales
** Build #5 was tagged February 16th, but no candidate builds yet
*** Build #5 was manually taggedNot sure there'll be a build 5.
** Windows builds for #4 are signed now
** apparently there is an issue with uploading those builds to the new S3 infrastructure [https://blog.seamonkey-project.org/2016/02/04/update-on-2-40/] See {{bug|1223633}} and {{bug|1213721}}
* Merges were performed as scheduled on March 7:
* Merges were performed as scheduled on March 7:
** comm-release default is now on SM 2.42.
** comm-release default is now on SM 2.42.
Confirmed users
2,078

edits