SeaMonkey:First Release: Difference between revisions

m
add SeaMonkey category
(add a bit about XPrint)
m (add SeaMonkey category)
 
(10 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{SeaMonkey-Resources}}
{{SeaMonkey-Resources}}
Ship happens.  [http://www.mozilla.org/projects/seamonkey/news.html#2006-01-30 SeaMonkey 1.0] was released on January 30th, 2006.


== SeaMonkey 1.0 release plan ==
== SeaMonkey 1.0 release plan ==


SeaMonkey 1.0, the first release of our new project, will be what a "Mozilla 1.8" application suite was meant to be. As such, it will be released from the Gecko 1.8 base, which it will share with the Mozilla Firefox 1.5 and Thunderbird 1.5 releases.
SeaMonkey 1.0, the first release of our new project, is what a "Mozilla 1.8" application suite was meant to be. As such, it was released from the Gecko 1.8.0 base, which it shares with the Mozilla Firefox 1.5 and Thunderbird 1.5 releases.


The current plan is to release an Alpha and a Beta release from the Mozilla 1.8 branch on the way to that 1.0 release:
We released an Alpha and a Beta release from the Mozilla 1.8.0 branch on the way to that 1.0 release:
* [http://www.mozilla.org/projects/seamonkey/releases/1.0a.html SeaMonkey 1.0 Alpha] was released from Gecko 1.8b4, paralleling the Firefox and Thunderbird 1.5 Beta1 releases done by Mozilla Foundation. While the basic codebase may be more beta than alpha quality, our new release process is not completely settled, we don't have our final [http://www.mozilla.org/projects/seamonkey/artwork.html Artwork] yet and we have no dedicated release machines in place, so it's better to call this an early testing release or "Alpha".
* [http://www.mozilla.org/projects/seamonkey/releases/1.0a.html SeaMonkey 1.0 Alpha] was released from Gecko 1.8b4, paralleling the Firefox and Thunderbird 1.5 Beta1 releases done by Mozilla Foundation. While the basic codebase may be more beta than alpha quality, our new release process is not completely settled, we don't have our final [http://www.mozilla.org/projects/seamonkey/artwork.html Artwork] yet and we have no dedicated release machines in place, so it's better to call this an early testing release or "Alpha".
* [http://www.mozilla.org/projects/seamonkey/releases/#1.0b SeaMonkey 1.0 Beta] was released from Gecko 1.8, like the Firefox 1.5 release. This testing release also incorporates our new [http://www.mozilla.org/projects/seamonkey/artwork.html Logo Artwork] for the first time.
* [http://www.mozilla.org/projects/seamonkey/releases/1.0b.html SeaMonkey 1.0 Beta] was released from Gecko 1.8, like the Firefox 1.5 release. This testing release also incorporated our new [http://www.mozilla.org/projects/seamonkey/artwork.html Logo Artwork] for the first time. A sample userAgent/About string for it is <tt>Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8) Gecko/20051219 SeaMonkey/1.0b</tt>
* SeaMonkey 1.0 is planned to be shipped off the Gecko 1.8.0 branch, which might get a few security/stability fixes, but no big changes from what we shipped with beta. ''We now have [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/contrib/latest-mozilla1.8.0/ 1.0 nightly builds]; please help us testing them!''
* [http://www.mozilla.org/projects/seamonkey/releases/ SeaMonkey 1.0] was shipped January 30th 2006 off the Gecko 1.8.0 branch, which might get a few security/stability fixes, but no big changes from what we shipped with beta. A sample userAgent/About string for it is <tt>Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0</tt>
 
''We have [http://ftp.mozilla.org/pub/mozilla.org/seamonkey/nightly/latest-mozilla1.8.0/ 1.0.x nightly builds]; please help us testing them!''


The release processes are managed by the SeaMonkey Council, Chris Thomas is the release engineer in charge of that process.
The release processes are managed by the SeaMonkey Council, Chris Thomas is the release engineer in charge of that process.


The QA work needed for releases is overseen by our QA lead Andrew Schultz.
The [[SeaMonkey:QA|QA work]] needed for releases is overseen by our QA lead Andrew Schultz.


== Release Checklist(s) ==
== Release Checklist(s) ==
Line 50: Line 54:
         remaining bugs, you can kick off the final release process.  
         remaining bugs, you can kick off the final release process.  
  <Callek> ben_ 5. Deal with bugs that arise, manage the  ...??? (cut off)
  <Callek> ben_ 5. Deal with bugs that arise, manage the  ...??? (cut off)
  <ben_> the final release process involves things like documenting changes (release noets,
  <ben_> the final release process involves things like documenting changes (release notes,
         product pages, etc).  
         product pages, etc).  
  <ben_> er, "manage them using bugzilla flags, etc. prioritize them and have people  
  <ben_> er, "manage them using bugzilla flags, etc. prioritize them and have people  
Line 61: Line 65:
  <ben_> you need to identify the work involved in that task then
  <ben_> you need to identify the work involved in that task then
  <ben_> break it down into pieces
  <ben_> break it down into pieces
  <ben_> findpeople to help and get estimates.
  <ben_> find people to help and get estimates.


[[MozillaReleaseChecklist]]
[[MozillaReleaseChecklist]]
Line 71: Line 75:


== Features ==
== Features ==
* Current Gecko - many improvements since Mozilla 1.7
* Current Gecko - many improvements since Mozilla 1.7
* Ship a final release with the various UI improvements since Mozilla 1.7
* Ship a final release with the various UI improvements since Mozilla 1.7
Line 84: Line 89:
** done
** done


For SeaMonkey 1.5:
[[Talk:SeaMonkey:First_Release|Talk about this]]


* Enable calendar ([https://bugzilla.mozilla.org/show_bug.cgi?id=182076 Bug 182076])
[[category:SeaMonkey|f]]
** still too unstable to enable
** You may use the [http://www.mozilla.org/projects/calendar/download.html#download_appsuite Calendar extension] for nightly SeaMonkey 1.0 builds on Windows
* Enable MNG again ([https://bugzilla.mozilla.org/show_bug.cgi?id=18574 Bug 18574])
** this can only be done when the source is in mozilla.org tree, which hasn't happened yet
** we will likely have contributed builds with MNG support from Alexander Opitz
* Port to toolkit ([https://bugzilla.mozilla.org/show_bug.cgi?id=255807 Bug 255807])
* Extension Manager ([https://bugzilla.mozilla.org/show_bug.cgi?id=272429 Bug 272429])
* Unattended install for corporate deployment ([https://bugzilla.mozilla.org/show_bug.cgi?id=268740 bug 268740])
* SPNEGO support ([https://bugzilla.mozilla.org/show_bug.cgi?id=246861 Bug 246861])
* Use 7-zip compression for builds ([https://bugzilla.mozilla.org/show_bug.cgi?id=154965 Bug 154965])
* Allow to easily migrate from/to Firefox/Thunderbird ([https://bugzilla.mozilla.org/show_bug.cgi?id=63389 Bug 63389])
* Port Thunderbird RSS/Atom reader to SeaMonkey ([https://bugzilla.mozilla.org/show_bug.cgi?id=255834 Bug 255834]])
* Port Live Bookmarks to SeaMonkey ([https://bugzilla.mozilla.org/show_bug.cgi?id=240393 Bug 240393])
* Enable XForms ([https://bugzilla.mozilla.org/show_bug.cgi?id=305395 Bug 305395 ])
* Improve the default theme (e.g. perhaps make Modern the default theme, see [https://bugzilla.mozilla.org/show_bug.cgi?id=218329 Bug 218329])
* Backout bug [https://bugzilla.mozilla.org/show_bug.cgi?id=281402 Bug 281402](or part of it) to re-enable Xprint under GTK2+ builds
** biesi: can't xprint still be enabled? should be as simple as --enable-xprint, right?
** ajschult: Yes.  The biggest issue there is that Red Hat / Fedora no longer install libXp.so by default ([https://bugzilla.mozilla.org/show_bug.cgi?id=284444 bug 284444]).  It'd need to be dynamically loaded.
* Improve CSS rules for Message Grouping. Something like [https://bugzilla.mozilla.org/show_bug.cgi?id=263255 Bug 263255]
* Disable IM button or add IM capability ([https://bugzilla.mozilla.org/show_bug.cgi?id=214223 Bug 214223] and [https://bugzilla.mozilla.org/show_bug.cgi?id=218714 Bug 218714])
 
...feel free to fill in more...
 
[[Talk:SeaMonkey:First_Release|Talk about this]]
213

edits