>From me also +1, tested some of the HSSF/XSSF stuff in two projects
and compared the src and bin packages between 3.9 and 3.10 to verify
that the content matches.

One difference that I saw is that in 3.9 we just used "poi-3.9", now
we use "poi-3.10-FINAL" in both jar-names and top-level directory, but
this is probably on purpose, right?

Not sure how to update the release-notes, there is a small typo "and a
PGP signatures", the "a" is not needed here.

Dominik.

On Sun, Feb 2, 2014 at 5:26 PM, Andreas Beeker <[email protected]> wrote:
> Maybe use an autogenerated range for the dist files?
>
> SVN has some kind of svn variable replacement:
> http://blog.krisrange.com/2010/07/inserting-keywordsvariables-in-subversion-with-auto_props/
>
> Andi
>
>
> On 02.02.2014 17:15, Nick Burch wrote:
>>
>> On Sun, 2 Feb 2014, Nick Burch wrote:
>>>
>>> Secondly, the NOTICE has "Copyright 2009 The Apache Software Foundation"
>>> in it. Not sure if that should be 2003-2013 (first release in Jakarta was
>>> 2003), or just 2014 (for the current year)? Not a blocker either, but one we
>>> need to work out then fix soonish!
>>
>>
>> HTTPD just has the latest year:
>>   http://svn.apache.org/repos/asf/httpd/httpd/trunk/NOTICE
>> APR has the range:
>>   http://svn.apache.org/repos/asf/apr/apr/trunk/NOTICE
>> Tika has an old year:
>>   http://svn.apache.org/repos/asf/tika/trunk/NOTICE.txt
>> Tomcat has the range:
>>   http://svn.apache.org/repos/asf/tomcat/trunk/NOTICE
>>
>> Anyone have any thoughts on which we should go for?
>>
>> Nick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to