Overview

This page explains the development and review process for the GlassFish Server 3.1 Release Notes.

Document Links

The following are links to several versions of the GlassFish Server Release Notes:

  • GlassFish 3.0.1 Release Notes
  • GlassFish 2.1.1 Release Notes

Links to the 3.1 Release Notes will be made available after comments on the 3.0.1 and 2.1.1 Release Notes have been incorporated and any new 3.1-specific topics have been added.

Release Notes Development and Review Process

The GlassFish Server 3.1 Release Notes development process is a bit unusual because the 3.1 release combines features from both the 2.1.1 release and the 3.0.1 release. Specifically, GF3.1 inherits clustering features from 2.1.1 and Java 6 EE features from 3.0.1. Because of this, there are topics from both the 2.1.1 and 3.0.1 Release Notes that are relevant to the 3.1 Release Notes.

With the foregoing in mind, the Release Notes development and review process is divided into four phases:

  1. Assess 2.1.1 and 3.0.1 Topics: Determine which topics from the 2.1.1 and 3.0.1 Release Notes are still relevant to 3.1. Please review the 2.1.1 and 3.0.1 documents, linked above, with an eye towards what to keep and what to throw with regard to the 3.1 Release Notes.
  2. Determine New Topics for 3.1: After establishing a baseline in Phase 1, the next phase is to determine the new topics that need to be included in the 3.1 Release Notes. Most of these topics should already be added as bugs, per the instructions in How to identify doc issues to technical writers.
  3. First Draft Review: Review the first complete draft of the 3.1 Release Notes, which will combine the relevant 2.1.1 and 3.0.1 topics and any new 3.1-specific topics. The goal of this phase is to identify any major issues or topics that have been omitted or not integrated correctly.
  4. Final Hand-off Review: The final review phase will be to verify that all relevant topics and comments have been incorporated in the 3.1 Release Notes. Note that this will not be the time to add major new topics or sections. Such comments should be made during Phase 3, above.

Providing Feedback

Please provide your feedback by adding comments to this wiki. Please review existing comments before posting to avoid duplicates.

Milestone Dates

Phase Summary Purpose Deadline Date
1 Assess 2.1.1 and 3.0.1 Topics Determine which topics from the 2.1.1 and 3.0.1 RNs are still relevant to 3.0.1 February 14th
2 Determine new 3.1 topics Use the defined procedure for notifying the RN writer of any new topics to add February 18th
3 First complete draft review Identify any major issues or topics that still need to be integrated February 21st
4 Final hand-off review Verify that all comments and topic requests have been integrated correctly February 24th

Any Release Notes comments that do not make it into the initial GlassFish 3.1 release will be added during the documentation refresh in March.

Questions

If you have any specific questions about the Release Notes or the Release Notes development process, please contact the Release Notes owner.

Comment ID
Comment
JC-001
We should remove the following sections, and replace them with a section that links (link TBD) to the published certification matrix:
JC-002
Add a section "Deprecated Functionality" that covers deprecated/EOL'd functionality (such as HADB), and to host announced deprecated features moving forward (TBD).  Unclear if we can link to an external "Deprecated Functionality" table. FYI, WLS "deprecated functionality" section: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/notes/new.html#wp1093291
JC-003
Add a section "Standards Support".  Unclear if we can point to an external document. I'll post an update. FYI, WLS "standards support" section: http://download.oracle.com/docs/cd/E12840_01/wls/docs103/notes/new.html#wp1078833We have the data for this.  Will post an update.
Posted by johnclingan at Feb 11, 2011 13:22