1177045 - (SM235-RELNOTE) Create/Update 2.35 Release Notes

Status: RESOLVED FIXED

(SeaMonkey :: Website, defect)

Description

[Philip Chee]

SeaMonkey 2.35 Release builds will be built soon.

These relnotes can be (begun to be) prepared ahead of the release date, but need to be out by our first release candidate.

Comment 2

[Jens Hatlak (:InvisibleSmiley)]

As requested here's a "short" guide on how I prepared the release notes in the past / what sources I used:

In general, the inclusion rule for any change candidates is whether the change in question affects end user experience in any way (if it doesn't, don't list it). Once the final list of changes has been identified, the summary of each one is adjusted so that it conforms to either the "XY has been done" or "Improved y" style (for better readability). Keep the HTML as simple and clean as possible. Finally, add a copy of the list, with links and other HTML stripped, to the release's News page entry.

Sources:

1. Firefox release notes
If you look at the Changes pages of SM releases up to 2.29, you'll find links to the corresponding Firefox release notes at the bottom of the respective page. I visited each of those (also through the beta cycle) and removed any entries that were Firefox-specific. Knowledge of which functionality Firefox already had in excess of SM prior to the relevant release helps to sort this out more quickly. Some examples:
* Developer Tools (including Inspector != DOM Inspector)
* Scratchpad
* New tab page
URLs of Firefox release notes are easy to guess once you know one and the version number of the relevant release. Alternatively, use your favorite search engine to find it.

2. For SM releases since 2.30 I included a link to the relevant Firefox for Developers page. Any information included in those pages is considered developer-centric, hence I remove any of those from the changes list extracted from the Firefox release notes. Basically this excludes most things HTML5, JS, CSS, etc., but I actually checked every single item listed on the Firefox release notes against the Firefox for Developers list rather than excluding items according to general topic.

3. Any SM-specific changes come on top. Here, you may either follow the hg pushlog yourself or check the auto-generated "SeaMonkey bugs" and "Thunderbird bugs" (for changes in shared MailNews code - to be identified using bug/patch inspection) links under "Bugs fixed in this release".

As you can see, when done properly, the above is a rather time-consuming task even for a single corresponding Firefox release. Now that we were forced to skip several releases again, the task is even more time-consuming. Unfortunately I don't have the time to do this myself anymore - and I mean even just that, just imagine I'd still try to list all bugs fixed in the meantime on the Changes page, including beautifying all the bug summaries! No way.

HTH

Comment 3

[Rainer Bielefeld]

Due to Bug 616821 comment #7

Comment 4

[rsx11m]

SM 2.35 has been released long ago