commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rahul Akolkar" <rahul.akol...@gmail.com>
Subject Re: [VOTE] Release Commons Digester 2.0
Date Sat, 27 Dec 2008 21:20:07 GMT
On Sat, Dec 27, 2008 at 11:17 AM, Jörg Schaible <joerg.schaible@gmx.de> wrote:
> Rahul Akolkar wrote:
>
>> This is a vote to release the following artifacts as Commons Digester 2.0:
>>
>>   http://people.apache.org/builds/commons/digester/2.0/RC1/
>>
>> This is a major release, with breaking changes. See release notes for
>> corresponding details.
>>
>> SVN tag is here:
>>
>>
> http://svn.apache.org/repos/asf/commons/proper/digester/tags/DIGESTER_2_0/
>>
>> ------------
>> [ ] +1 for release
>> [ ] +0
>> [ ] -0
>> [ ] -1 for release because...
>> ------------
>>
>> Notes:
>>  * There are a number of (mostly unavoidable) traces when running the
>>  tests
>>  * The staged site contains few broken links (won't be broken when
>>  we go live)
>
> Are you sure here? The Javadoc link in the "Release 2.0 (Current )" section
> points to broken link "docs/api". However, the link for the Javadocs in the
> Maven Reports section points to "apidocs" (Maven 2 default) and works. So
> either one or the other will be broken ...
>
<snip/>

Thanks for taking a look. It doesn't matter where the link in the
"Release 2.0 (Current)" section points to, the Javadoc gets copied
over to match. Note the commons-digester-2.0 segment in the relative
path -- this will be done as part of the site updates after the
release.


>>  * I've looked at most static analysis reports, anything
>>  pending is
>> not important IMO
>>  * I'm traveling rest of the week so my replies won't be immediate
>>  * Vote will run for atleast 72 hours, maybe more given the timing
>
> +1 if the link above is not broken in the final release.
<snap/>

I think its OK. Its a bit tricky to count votes predicated like that,
it would be better if you can confirm either way based on my response
here. I intend to close this vote on Monday.


> Apart from that my
> compiler zoo worked fine with the source distribution (although IMHO it is
> always somewhat irritating to have such a lot stack traces printed if the
> result counts zero errors).
>
<snip/>

Yes, its not good. However, there are patterns in use that make it
more difficult to avoid the traces.

-Rahul


> - Jörg
>

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


Mime
View raw message