My hope is that by encouraging contributors to participate in release note writing, we can get a larger number of release notes (each with hopefully higher relevance to the average user).
Internally, Netscape QA is asked to submit a list of bugs to a tracking bug for the documentation writer.
I propose the following process:
Nominate:
For Networking Standards QA owned components (Networking, Cache, File, FTP, HTTP), you can tag a bug with the "relnote" keyword. This keyword is not actively used by other groups, but for our purposes, it means:
"Needs to be considered for release noting"
Bugs that do not need to be in the release notes should have existing "relnote" keywords removed. Please make a brief comment if you remove the keyword.
Drafting:
Draft release note text should have a header so it makes sense in the larger context of the bug. For example:
"RELEASE NOTE DRAFT FOR NS 6.1" or something similar.
I expect that for this release, I will need to write most of the release notes, but if anyone wants to give it a try, your help is appreciated.
Submission::
I will take the total result and submit them to the Netscape CPD documentation writer. There will be some editing and size limitations, but I believe we can make substantial improvements over the 6.0.x notes. Currently the deadline is End of Business, 5pm PST, Friday, Aug 3, 2001.
Administravia:
Other release note releated keywords should NOT be used (e.g. "relnote2", "relnote3", "relnoteRTM"). By the end of today, there should be no networking bugs that have these keywords.
Mozilla milestone.next:
For the next milestone, I will probably clear the relnote keyword on fixed bugs, keep taking nominations, and then build a new release note from there.
If anyone has any concerns or suggestions, please let me know.
benc
