Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (herse.apache.org: domain of m.v.lunteren@gmail.com
 designates 66.249.92.168 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=IUIPjnZBIvU5tXN2d93EcDXAfCLiiJ6DDQrBq53k73h/VGWYwdxhCdZ0+9MdFxXnwr0Bu85aqtk74+4N9b1ExFLbWOLQ+VkBKPzJdVXOHe3QZOw2O9lyyrmJFgCtt3/dDHlJK6HeooQgyCMb4gA84EBenbX1tP8uXU0A3nmS8dI=
Message-ID: <c25576af0701220955x131a2c79ia2e2c5a3dc428d4d@mail.gmail.com>
Date: Mon, 22 Jan 2007 09:55:54 -0800
From: "Myrna van Lunteren" <m.v.lunteren@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: trunk docs header page says 10.2
In-Reply-To: <9f40b500701220932w6793284eo536b7431df20032b@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c25576af0701201709r59f1dc5end19e0ff41ab43674@mail.gmail.com>
	 <54ac72d70701210111r33da76a1he3bdb9f19bd0862@mail.gmail.com>
	 <9f40b500701220932w6793284eo536b7431df20032b@mail.gmail.com>

On 1/22/07, Laura Stewart <scotsmatrix@gmail.com> wrote:
> On 1/21/07, Andrew McIntyre <mcintyre.a@gmail.com> 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