You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Stefan Bodewig <bo...@apache.org> on 2013/10/23 06:56:20 UTC
[VOTE] Release Compress 1.6 based on RC3
Compress 1.6 RC3 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/compress/
(svn revision 3327)
Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-compress/1.6/
Details of changes since 1.5 are in the release notes:
http://people.apache.org/~bodewig/cc-1.6-rc3/RELEASE-NOTES.txt
http://people.apache.org/~bodewig/cc-1.6-rc3/site/changes-report.html
The tag is here:
https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.6-RC3/
(svn revision 1534904)
Site:
http://people.apache.org/~bodewig/cc-1.6-rc3/site/
Clirr Report (compared to 1.1):
http://people.apache.org/~bodewig/cc-1.6-rc3/site/clirr-report.html
RAT Report:
http://people.apache.org/~bodewig/cc-1.6-rc3/site/rat-report.html
KEYS:
http://www.apache.org/dist/commons/KEYS
Please review the release candidate and vote.
This vote will close no sooner than 72 hours from now, i.e. after 0500
GMT 26-October 2013
[ ] +1 Release these artifacts
[ ] +0 OK, but...
[ ] -0 OK, but really should fix...
[ ] -1 I oppose this release because...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[RESULT] Release Compress 1.6 based on RC3
Posted by Stefan Bodewig <bo...@apache.org>.
With +1s by
Torsten Curdt
Emmanuel Bourg
Benedikt Ritter
Gary Gregory
Stefan Bodewig
and no other votes the vote has passed.
I'll copy around the release artifacts but will give the mirrors a bit
of time to catch up before I announce the release and update the site.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Compress 1.6 based on RC3
Posted by Benedikt Ritter <br...@apache.org>.
Hello Stefan,
my environment is:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
17:22:22+0200)
Maven home: /Applications/dev/maven/apache-maven-3.1.1
Java version: 1.7.0_40, vendor: Oracle Corporation
Java home:
/Library/Java/JavaVirtualMachines/jdk1.7.0_40.jdk/Contents/Home/jre
Default locale: de_DE, platform encoding: UTF-8
OS name: "mac os x", version: "10.9", arch: "x86_64", family: "mac"
- signatures and checksums are fine
- Tag and sources archive have the same content
- builds fine
- site looks good - FindBugs has two errors but I can not judge whether
they are critical.
here is my +1 :-)
Benedikt
2013/10/23 Stefan Bodewig <bo...@apache.org>
> Compress 1.6 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 3327)
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-compress/1.6/
>
> Details of changes since 1.5 are in the release notes:
> http://people.apache.org/~bodewig/cc-1.6-rc3/RELEASE-NOTES.txt
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/changes-report.html
>
> The tag is here:
>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.6-RC3/
> (svn revision 1534904)
>
> Site:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/
>
> Clirr Report (compared to 1.1):
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/clirr-report.html
>
> RAT Report:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/rat-report.html
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 0500
> GMT 26-October 2013
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
http://people.apache.org/~britter/
http://www.systemoutprintln.de/
http://twitter.com/BenediktRitter
http://github.com/britter
Re: [compress] Strong Crypto in Tests
Posted by Benedikt Ritter <be...@gmail.com>.
2013/10/24 Gary Gregory <ga...@gmail.com>
> On Thu, Oct 24, 2013 at 1:45 AM, Benedikt Ritter <beneritter@gmail.com
> >wrote:
>
> >
> >
> > Send from my mobile device
> >
> > > Am 23.10.2013 um 16:12 schrieb Stefan Bodewig <bo...@apache.org>:
> > >
> > >> On 2013-10-23, Gary Gregory wrote:
> > >>
> > >> Consider using JUnit's Assume to skip testing, this will allow IDEs
> and
> > >> tools to know a test has been skipped.
> > >
> > > Unfortunately the test like many of Compress' tests is in JUnit 3.x
> land
> > > - something to change if we ever get 2.x off the ground.
> >
> > I don't see a reason to wait for 2.x before updating to JUnit 4. The old
> > tests will be executable without changes.
> > Am I missing something here?
> >
>
> Updating to JUnit 4 from 3 is not always a drop in replacement. I've run
> into cases that required tweaking.
>
I'll try to have a look when I have some time.
>
> G
>
> >
> > Benedikt
> >
> > >
> > > Stefan
> > >
> > > ---------------------------------------------------------------------
> > > 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
> >
> >
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> Java Persistence with Hibernate, Second Edition<
> http://www.manning.com/bauer3/>
> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
> Spring Batch in Action <http://www.manning.com/templier/>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
Re: [compress] Strong Crypto in Tests
Posted by Gary Gregory <ga...@gmail.com>.
On Thu, Oct 24, 2013 at 1:45 AM, Benedikt Ritter <be...@gmail.com>wrote:
>
>
> Send from my mobile device
>
> > Am 23.10.2013 um 16:12 schrieb Stefan Bodewig <bo...@apache.org>:
> >
> >> On 2013-10-23, Gary Gregory wrote:
> >>
> >> Consider using JUnit's Assume to skip testing, this will allow IDEs and
> >> tools to know a test has been skipped.
> >
> > Unfortunately the test like many of Compress' tests is in JUnit 3.x land
> > - something to change if we ever get 2.x off the ground.
>
> I don't see a reason to wait for 2.x before updating to JUnit 4. The old
> tests will be executable without changes.
> Am I missing something here?
>
Updating to JUnit 4 from 3 is not always a drop in replacement. I've run
into cases that required tweaking.
G
>
> Benedikt
>
> >
> > Stefan
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-24, Benedikt Ritter wrote:
> I don't see a reason to wait for 2.x before updating to JUnit 4. The
> old tests will be executable without changes.
There already are 4.x and 3.x tests mixed up.
> Am I missing something here?
It needs somebody to do it. As I expet us to rewrite all tests when we
do 2.x it would be a good time to migrate the tests then. Otherwise
we'd have to touch them twice.
That being said, I don't see us rushing towards 2.x and if anybody
thinks migrating all tests for the sake of migrating them is worth the
effort, then I certainly won't stop him. :-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Benedikt Ritter <be...@gmail.com>.
Send from my mobile device
> Am 23.10.2013 um 16:12 schrieb Stefan Bodewig <bo...@apache.org>:
>
>> On 2013-10-23, Gary Gregory wrote:
>>
>> Consider using JUnit's Assume to skip testing, this will allow IDEs and
>> tools to know a test has been skipped.
>
> Unfortunately the test like many of Compress' tests is in JUnit 3.x land
> - something to change if we ever get 2.x off the ground.
I don't see a reason to wait for 2.x before updating to JUnit 4. The old tests will be executable without changes.
Am I missing something here?
Benedikt
>
> Stefan
>
> ---------------------------------------------------------------------
> 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
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Gary Gregory wrote:
> Consider using JUnit's Assume to skip testing, this will allow IDEs and
> tools to know a test has been skipped.
Unfortunately the test like many of Compress' tests is in JUnit 3.x land
- something to change if we ever get 2.x off the ground.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Gary Gregory <ga...@gmail.com>.
Consider using JUnit's Assume to skip testing, this will allow IDEs and
tools to know a test has been skipped.
If you use a conditional in the test code, there is no possible feedback.
Gary
On Wed, Oct 23, 2013 at 5:15 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2013-10-23, Emmanuel Bourg wrote:
>
> > The test coverage is much better, thank you Stefan.
>
> Thank you for making me find a serious bug by pointing out the low
> coverage :-)
>
> > test7zDecryptUnarchive failed on Linux using the Java 6 JDK (not
> > OpenJDK6) due to the lack of the strong crypto policy. That's easily
> > fixed by installing the missing files [1], but as a convenience I would
> > suggest skipping this test when the strong crypto is not installed.
>
> Right. I'm so used to having strong crypto installed on all my machines
> I just forget about it. I'll look into skipping the test (in trunk, for
> 1.7 :-) if I cannot get AES256.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Paul Benedict wrote:
> In my own research on strong crypto, I found out that US law allows
> strong crypto to be exported for open source software. That was some
> provision recently carved out in the last 10 years. I think there are
> some limitations and procedures wrapped around it -- like submitting
> the URL to the source code to the US Commerce Department -- but
> generally it's allowed. However, this isn't legal advice :-) and just
> my own understanding. I hope this helps.
This is exactly what the page I pointed to[1] is about. All required
dancing has been performed. :-)
Stefan
[1] http://www.apache.org/licenses/exports/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Paul Benedict <pb...@apache.org>.
In my own research on strong crypto, I found out that US law allows strong
crypto to be exported for open source software. That was some provision
recently carved out in the last 10 years. I think there are some
limitations and procedures wrapped around it -- like submitting the URL to
the source code to the US Commerce Department -- but generally it's
allowed. However, this isn't legal advice :-) and just my own
understanding. I hope this helps.
With that said, I wouldn't commit any strong crypto code into Apache's SCM
without first getting assurance from the IP folks.
Paul
On Wed, Oct 23, 2013 at 8:54 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2013-10-23, Mark Fortner wrote:
>
> > As you're probably aware, aes is export restricted.
>
> Commons Compress already has a crypto notice, see also
> <http://www.apache.org/licenses/exports/>
>
> 7z uses 256bit AES when encrypting so if we want to provide code that
> can read encrypted archives there is little choice which algorithms we
> support :-)
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
Cheers,
Paul
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Mark Fortner wrote:
> As you're probably aware, aes is export restricted.
Commons Compress already has a crypto notice, see also
<http://www.apache.org/licenses/exports/>
7z uses 256bit AES when encrypting so if we want to provide code that
can read encrypted archives there is little choice which algorithms we
support :-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Mark Fortner <ph...@gmail.com>.
As you're probably aware, aes is export restricted. So it might be better
to simply check for the availability of a particular encryption algorithm
before running a test and avoid making restricted libraries generally
available.
Mark
On Oct 23, 2013 6:10 AM, "Stefan Bodewig" <bo...@apache.org> wrote:
> On 2013-10-23, Bear Giles wrote:
>
> > Should that be PKCS7Padding? Or would that be worse - I don't recall
> > if it's one of the "must have" paddings in the spec.
>
> 7z uses "AES/CBC/NoPadding" and that's what I use during the check
> inside the unit tests as well now.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Bear Giles wrote:
> Should that be PKCS7Padding? Or would that be worse - I don't recall
> if it's one of the "must have" paddings in the spec.
7z uses "AES/CBC/NoPadding" and that's what I use during the check
inside the unit tests as well now.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Bear Giles <bg...@coyotesong.com>.
Should that be PKCS7Padding? Or would that be worse - I don't recall if
it's one of the "must have" paddings in the spec.
http://crypto.stackexchange.com/questions/9043/what-is-the-difference-between-pkcs5-padding-and-pkcs7-padding
In practice it's unlikely that a software-based crypto provider will be so
pedantic that it throws an exception if you try to use PKCS5 with a 256-bit
cipher but I'm not sure if that's true if it's a hardware-based crypto
provider. Anyone who springs for hardware will probably want something that
strictly complies with the spec and PKCS5 is only defined for 64-bit
ciphers.
Bear
On Wed, Oct 23, 2013 at 5:03 AM, Stefan Bodewig <bo...@apache.org> wrote:
> On 2013-10-23, Jörg Schaible wrote:
>
> > boolean supportedKeyLength(int keyLen) throws NoSuchAlgorithmException
> > {
> > if (Cipher.getMaxAllowedKeyLength("AES/ECB/PKCS5Padding") < keyLen) {
> > System.err.println("WARNING: " + getName()
> > + " not executed, environment does not support " + keyLen
> > + "-bit keys for AES");
> > return false;
> > }
> > return true;
>
> Looks a lot nicer than my "catch Exception" approach, thanks.
>
> Stefan
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
Re: [compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Jörg Schaible wrote:
> boolean supportedKeyLength(int keyLen) throws NoSuchAlgorithmException
> {
> if (Cipher.getMaxAllowedKeyLength("AES/ECB/PKCS5Padding") < keyLen) {
> System.err.println("WARNING: " + getName()
> + " not executed, environment does not support " + keyLen
> + "-bit keys for AES");
> return false;
> }
> return true;
Looks a lot nicer than my "catch Exception" approach, thanks.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [compress] Strong Crypto in Tests
Posted by Jörg Schaible <Jo...@scalaris.com>.
Stefan Bodewig wrote:
> On 2013-10-23, Emmanuel Bourg wrote:
>
>> The test coverage is much better, thank you Stefan.
>
> Thank you for making me find a serious bug by pointing out the low
> coverage :-)
>
>> test7zDecryptUnarchive failed on Linux using the Java 6 JDK (not
>> OpenJDK6) due to the lack of the strong crypto policy. That's easily
>> fixed by installing the missing files [1], but as a convenience I would
>> suggest skipping this test when the strong crypto is not installed.
>
> Right. I'm so used to having strong crypto installed on all my machines
> I just forget about it. I'll look into skipping the test (in trunk, for
> 1.7 :-) if I cannot get AES256.
=============== %< ===============
void testMe() {
if(supportedKeyLength(256)) {
// ...
}
}
boolean supportedKeyLength(int keyLen) throws NoSuchAlgorithmException
{
if (Cipher.getMaxAllowedKeyLength("AES/ECB/PKCS5Padding") < keyLen) {
System.err.println("WARNING: " + getName()
+ " not executed, environment does not support " + keyLen
+ "-bit keys for AES");
return false;
}
return true;
}
=============== %< ===============
We use this helper method in our unit tests.
Cheers,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
[compress] Strong Crypto in Tests
Posted by Stefan Bodewig <bo...@apache.org>.
On 2013-10-23, Emmanuel Bourg wrote:
> The test coverage is much better, thank you Stefan.
Thank you for making me find a serious bug by pointing out the low
coverage :-)
> test7zDecryptUnarchive failed on Linux using the Java 6 JDK (not
> OpenJDK6) due to the lack of the strong crypto policy. That's easily
> fixed by installing the missing files [1], but as a convenience I would
> suggest skipping this test when the strong crypto is not installed.
Right. I'm so used to having strong crypto installed on all my machines
I just forget about it. I'll look into skipping the test (in trunk, for
1.7 :-) if I cannot get AES256.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [VOTE] Release Compress 1.6 based on RC3
Posted by Emmanuel Bourg <eb...@apache.org>.
+1
The test coverage is much better, thank you Stefan.
test7zDecryptUnarchive failed on Linux using the Java 6 JDK (not
OpenJDK6) due to the lack of the strong crypto policy. That's easily
fixed by installing the missing files [1], but as a convenience I would
suggest skipping this test when the strong crypto is not installed.
Emmanuel Bourg
[1]
http://www.oracle.com/technetwork/java/javase/downloads/jce-6-download-429243.html
Le 23/10/2013 06:56, Stefan Bodewig a écrit :
> Compress 1.6 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 3327)
>
> Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-compress/1.6/
>
> Details of changes since 1.5 are in the release notes:
> http://people.apache.org/~bodewig/cc-1.6-rc3/RELEASE-NOTES.txt
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/changes-report.html
>
> The tag is here:
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.6-RC3/
> (svn revision 1534904)
>
> Site:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/
>
> Clirr Report (compared to 1.1):
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/clirr-report.html
>
> RAT Report:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/rat-report.html
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 0500
> GMT 26-October 2013
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
Re: [VOTE] Release Compress 1.6 based on RC3
Posted by Gary Gregory <ga...@gmail.com>.
+1
Checked out the tag and built "mvn site" with:
Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17
11:22:22-0400)
Maven home: C:\Java\apache-maven-3.1.1\bin\..
Java version: 1.7.0_45, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.7.0_45\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
Clirr errors are acceptable per our discussion on the ML and the release
notes include a warning/explanation.
Other reports are OK.
FindBugs is no worse than previous release.
Cobertura shows some classes at 0% coverage which is not great but not a
blocker.
Gary
On Wed, Oct 23, 2013 at 12:56 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Compress 1.6 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 3327)
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-compress/1.6/
>
> Details of changes since 1.5 are in the release notes:
> http://people.apache.org/~bodewig/cc-1.6-rc3/RELEASE-NOTES.txt
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/changes-report.html
>
> The tag is here:
>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.6-RC3/
> (svn revision 1534904)
>
> Site:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/
>
> Clirr Report (compared to 1.1):
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/clirr-report.html
>
> RAT Report:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/rat-report.html
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 0500
> GMT 26-October 2013
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
Java Persistence with Hibernate, Second Edition<http://www.manning.com/bauer3/>
JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
Spring Batch in Action <http://www.manning.com/templier/>
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release Compress 1.6 based on RC3
Posted by Torsten Curdt <tc...@vafer.org>.
+1 let's release it!
On Wed, Oct 23, 2013 at 6:56 AM, Stefan Bodewig <bo...@apache.org> wrote:
> Compress 1.6 RC3 is available for review here:
> https://dist.apache.org/repos/dist/dev/commons/compress/
> (svn revision 3327)
>
> Maven artifacts are here:
>
> https://repository.apache.org/content/repositories/orgapachecommons-ABC/org/apache/commons/commons-compress/1.6/
>
> Details of changes since 1.5 are in the release notes:
> http://people.apache.org/~bodewig/cc-1.6-rc3/RELEASE-NOTES.txt
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/changes-report.html
>
> The tag is here:
>
> https://svn.apache.org/repos/asf/commons/proper/compress/tags/COMPRESS-1.6-RC3/
> (svn revision 1534904)
>
> Site:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/
>
> Clirr Report (compared to 1.1):
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/clirr-report.html
>
> RAT Report:
> http://people.apache.org/~bodewig/cc-1.6-rc3/site/rat-report.html
>
> KEYS:
> http://www.apache.org/dist/commons/KEYS
>
> Please review the release candidate and vote.
> This vote will close no sooner than 72 hours from now, i.e. after 0500
> GMT 26-October 2013
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
>