commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sebb <seb...@gmail.com>
Subject Re: [VOTE] Release Commons Lang 2.6 based on RC1
Date Wed, 12 Jan 2011 22:50:44 GMT
On 12 January 2011 21:10, Niall Pemberton <niall.pemberton@gmail.com> wrote:
> On Wed, Jan 12, 2011 at 12:18 PM, Niall Pemberton
> <niall.pemberton@gmail.com> wrote:
>> On Wed, Jan 12, 2011 at 3:02 AM, Phil Steitz <phil.steitz@gmail.com> wrote:
>>> I will test the release in the next couple of days, but I have one
>>> comment on the release notes.  Not enough for a -1 by itself, worth
>>> talking about if you roll another RC.
>>>
>>> I like the format and content of the release notes.  I don't much like
>>> the heading "TASKS IN 2.6" over the list of resolved issues classified
>>> as "update" in changes.xml, though.
>>
>> I was trying to separate out changes that didn't actually affect the
>> code from the actual software bug fixes/enhancments. I take your point
>> though and I will fix it in the branch so that if a new RC is
>> required, then it will be fixed.
>
> OK I updated the following which will be ported to the trunk:
>
> http://people.apache.org/~niallp/lang/upgradeto2_6.html

The first section heading is
"Upgrade to 2.5"

and the page title is
"Lang - Upgrade from 2.4 to 2.5"

Both seem wrong, although the section heading is ambiguous - it could
mean "This is an upgrade to 2.5" or "You must upgrade to 2.5".

It would be clearer to put "Upgrading to 2.6" or "How to upgrade to 2.6"

[The old TASKS section header now looks fine]

> http://people.apache.org/~niallp/lang/changes-report.html
>
> Niall
>
>>>   The text descriptions are taken
>>> from the issue descriptions and refer to the enhancement request,
>>> e.g., "Javadoc is incorrect for lastIndexOf() method"  Labeling these
>>> as "tasks" leaves open the interpretation that these are known,
>>> unresolved issues.  I think it is better to either just lump them with
>>> the "adds" or use labels like "New Features" (for the adds) and
>>> "Enhancements" or "Updates" for the "updates."
>>
>> I look at re-doing the changes.xml - since the site isn't part of the
>> release and I will be copying the new 2.6 elements over to the trunk's
>> changes.xml if/when the 2.6 release goes out.
>>
>> Niall
>>
>>> Phil
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>

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


Mime
View raw message