On 1/22/07, Laura Stewart <[EMAIL PROTECTED]> wrote:
On 1/21/07, Andrew McIntyre <[EMAIL PROTECTED]> wrote:
> You didn't do anything wrong. No one has updated the doc tree to
> reflect the new version yet. :-)
>
> Like the code trunk, someone has to make the change to reflect that
> the Derby version represented on the docs trunk is now 10.3. Because
> the doc and code trees are separate, they need to be updated
> separately. There's no doc or wiki for this, although maybe there
> should be. Maybe we should start a MinorVersionBumpTasks topic on the
> wiki that describes the changes needed for code, docs, and website for
> a minor release.
I have started developing a new page on the Derby docs Web pages
called " Release Checklist for Docs". I am still working on the
content and have not submitted the patch yet for this new page. I
think that this would be a good place to mention the steps that need
to take place for the doc specific updates and WHEN in the release
cycle this change needs to take place.
What I propose is this:
After each new release is made public, the conref files for the Derby
manuals need to be updated so that the Alpha versions of the manuals
reflect the next release number. This task needs to be completed for
each new minor and point release.
To complete this task:
1. Ask on the derby-dev list what the correct release number is (minor
or point).
2. Create a JIRA issue for this task.
3. Open the conrefs files for each Derby manual with the new release
version. For example: devconrefs.dita
4. In the "Version and release numbers" section, change the ph tag for
shortversionnumber.
5. If this is a change to a major release, for example from 10 to 11,
in the "Product specific entities" section change the ph tag for
productinstallname.
How does this sound?
--
Laura Stewart
Sounds good to me. I felt that creating a new page was going to be too
fragmented, so I added a comment to the
http://wiki.apache.org/db-derby/DerbySnapshotOrRelease page, but I can
easily be convinced of the use of a dedicated page (as long as it's
linked of that main page).
Myrna