commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Henri Yandell <flame...@gmail.com>
Subject Re: [all] Release preparation documentation
Date Tue, 06 Apr 2010 04:37:22 GMT
On Mon, Apr 5, 2010 at 1:54 PM, sebb <sebbaz@gmail.com> wrote:

> I think it might be useful to add a note regarding consistency between
> changes.xml, RELEASE-NOTES and JIRA.
>
> For example, if JIRA FOO-1234 is fixed in release 1.2, then IMO it
> should have a JIRA "fix" release of 1.2, and appear in the
> changes/RelNotes for 1.2. Conversely, if FOO-1234 is not fixed in
> release 1.2, then it should not have a JIRA fix of 1.2.

Is there a component for which this isn't true?

> This is to make it easy for users/developers to find which release
> contains the fix for a particular JIRA bug. It is not always so easy
> to find this out from checking release notes.
>
> It may be quite tedious to do the consistency check - and it may not
> always be 100% accurate - but I would hope to get agreement that it's
> worth documenting as a desirable goal.

I've been deleting desirable goals from the docs :)

I think it's more desirable that they be short, sweet and focused;
than that they cover all possibilities.

Hen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message