RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-03 Thread Allison, Timothy B. 
Thank you, Javen!

Thank you, Dominik!

-Original Message-
From: Javen O'Neal [mailto:one...@apache.org] 
Sent: Thursday, February 2, 2017 3:02 PM
To: POI Developers List 
Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

Dominik,

The trunk is open for commits. I have built and deployed 3.16-beta2. The only 
thing left is to send out an announcement email.

On Feb 2, 2017 11:45, "Dominik Stadler"  wrote:

> Hi,
>
> this seems to have been caused by r1747942, I have a local change 
> pending the beta2-release which reverts some parts of this change so 
> that this works as before again.
>
> Dominik.
>
> On Wed, Feb 1, 2017 at 10:24 PM, Allison, Timothy B. 
> 
> wrote:
>
> > Thank you, Dominik!
> >
> > Looks like there is one other new one -- very rare -- that isn't 
> > caused
> by
> > the embedded extractor or the WMF component.
> >
> > java.lang.NegativeArraySizeException
> > at o.a.p.ddf.EscherComplexProperty.resizeComplexData(
> > EscherComplexProperty.java:102)
> > at o.a.p.ddf.EscherArrayProperty.setArrayData(
> > EscherArrayProperty.java:169)
> > at o.a.p.ddf.EscherPropertyFactory.createProperties(
> > EscherPropertyFactory.java:81)
> > at o.a.p.ddf.AbstractEscherOptRecord.fillFields(
> > AbstractEscherOptRecord.java:55)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.hwpf.model.EscherRecordHolder.fillEscherRecords(
> > EscherRecordHolder.java:56)
> > at o.a.p.hwpf.model.EscherRecordHolder.(
> > EscherRecordHolder.java:45)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:275)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:157)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:145)
> > at o.a.p.stress.HWPFFileHandler.handleFile(HWPFFileHandler.
> > java:32)
> > at org.dstadler.commoncrawl.FileHandlingRunnable.run(
> > FileHandlingRunnable.java:64)
> > at java.base/java.util.concurrent.Executors$
> RunnableAdapter.call(
> > Executors.java:514)
> > at java.base/java.util.concurrent.FutureTask.run(
> > FutureTask.java:264)
> > at java.base/java.util.concurrent.ThreadPoolExecutor.
> > runWorker(ThreadPoolExecutor.java:1161)
> > at java.base/java.util.concurrent.ThreadPoolExecutor$
> > Worker.run(ThreadPoolExecutor.java:635)
> > at java.base/java.lang.Thread.run(Thread.java:844)
> >
>

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-02 Thread Javen O'Neal 
Dominik,

The trunk is open for commits. I have built and deployed 3.16-beta2. The
only thing left is to send out an announcement email.

On Feb 2, 2017 11:45, "Dominik Stadler"  wrote:

> Hi,
>
> this seems to have been caused by r1747942, I have a local change pending
> the beta2-release which reverts some parts of this change so that this
> works as before again.
>
> Dominik.
>
> On Wed, Feb 1, 2017 at 10:24 PM, Allison, Timothy B. 
> wrote:
>
> > Thank you, Dominik!
> >
> > Looks like there is one other new one -- very rare -- that isn't caused
> by
> > the embedded extractor or the WMF component.
> >
> > java.lang.NegativeArraySizeException
> > at o.a.p.ddf.EscherComplexProperty.resizeComplexData(
> > EscherComplexProperty.java:102)
> > at o.a.p.ddf.EscherArrayProperty.setArrayData(
> > EscherArrayProperty.java:169)
> > at o.a.p.ddf.EscherPropertyFactory.createProperties(
> > EscherPropertyFactory.java:81)
> > at o.a.p.ddf.AbstractEscherOptRecord.fillFields(
> > AbstractEscherOptRecord.java:55)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.ddf.EscherContainerRecord.fillFields(
> > EscherContainerRecord.java:81)
> > at o.a.p.hwpf.model.EscherRecordHolder.fillEscherRecords(
> > EscherRecordHolder.java:56)
> > at o.a.p.hwpf.model.EscherRecordHolder.(
> > EscherRecordHolder.java:45)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:275)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:157)
> > at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:145)
> > at o.a.p.stress.HWPFFileHandler.handleFile(HWPFFileHandler.
> > java:32)
> > at org.dstadler.commoncrawl.FileHandlingRunnable.run(
> > FileHandlingRunnable.java:64)
> > at java.base/java.util.concurrent.Executors$
> RunnableAdapter.call(
> > Executors.java:514)
> > at java.base/java.util.concurrent.FutureTask.run(
> > FutureTask.java:264)
> > at java.base/java.util.concurrent.ThreadPoolExecutor.
> > runWorker(ThreadPoolExecutor.java:1161)
> > at java.base/java.util.concurrent.ThreadPoolExecutor$
> > Worker.run(ThreadPoolExecutor.java:635)
> > at java.base/java.lang.Thread.run(Thread.java:844)
> >
>

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-02 Thread Dominik Stadler 
Hi,

this seems to have been caused by r1747942, I have a local change pending
the beta2-release which reverts some parts of this change so that this
works as before again.

Dominik.

On Wed, Feb 1, 2017 at 10:24 PM, Allison, Timothy B. 
wrote:

> Thank you, Dominik!
>
> Looks like there is one other new one -- very rare -- that isn't caused by
> the embedded extractor or the WMF component.
>
> java.lang.NegativeArraySizeException
> at o.a.p.ddf.EscherComplexProperty.resizeComplexData(
> EscherComplexProperty.java:102)
> at o.a.p.ddf.EscherArrayProperty.setArrayData(
> EscherArrayProperty.java:169)
> at o.a.p.ddf.EscherPropertyFactory.createProperties(
> EscherPropertyFactory.java:81)
> at o.a.p.ddf.AbstractEscherOptRecord.fillFields(
> AbstractEscherOptRecord.java:55)
> at o.a.p.ddf.EscherContainerRecord.fillFields(
> EscherContainerRecord.java:81)
> at o.a.p.ddf.EscherContainerRecord.fillFields(
> EscherContainerRecord.java:81)
> at o.a.p.ddf.EscherContainerRecord.fillFields(
> EscherContainerRecord.java:81)
> at o.a.p.ddf.EscherContainerRecord.fillFields(
> EscherContainerRecord.java:81)
> at o.a.p.hwpf.model.EscherRecordHolder.fillEscherRecords(
> EscherRecordHolder.java:56)
> at o.a.p.hwpf.model.EscherRecordHolder.(
> EscherRecordHolder.java:45)
> at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:275)
> at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:157)
> at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:145)
> at o.a.p.stress.HWPFFileHandler.handleFile(HWPFFileHandler.
> java:32)
> at org.dstadler.commoncrawl.FileHandlingRunnable.run(
> FileHandlingRunnable.java:64)
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(
> Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(
> FutureTask.java:264)
> at java.base/java.util.concurrent.ThreadPoolExecutor.
> runWorker(ThreadPoolExecutor.java:1161)
> at java.base/java.util.concurrent.ThreadPoolExecutor$
> Worker.run(ThreadPoolExecutor.java:635)
> at java.base/java.lang.Thread.run(Thread.java:844)
>

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-01 Thread Allison, Timothy B. 
Thank you, Dominik!

Looks like there is one other new one -- very rare -- that isn't caused by the 
embedded extractor or the WMF component.

java.lang.NegativeArraySizeException
at 
o.a.p.ddf.EscherComplexProperty.resizeComplexData(EscherComplexProperty.java:102)
at 
o.a.p.ddf.EscherArrayProperty.setArrayData(EscherArrayProperty.java:169)
at 
o.a.p.ddf.EscherPropertyFactory.createProperties(EscherPropertyFactory.java:81)
at 
o.a.p.ddf.AbstractEscherOptRecord.fillFields(AbstractEscherOptRecord.java:55)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.ddf.EscherContainerRecord.fillFields(EscherContainerRecord.java:81)
at 
o.a.p.hwpf.model.EscherRecordHolder.fillEscherRecords(EscherRecordHolder.java:56)
at o.a.p.hwpf.model.EscherRecordHolder.(EscherRecordHolder.java:45)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:275)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:157)
at o.a.p.hwpf.HWPFDocument.(HWPFDocument.java:145)
at o.a.p.stress.HWPFFileHandler.handleFile(HWPFFileHandler.java:32)
at 
org.dstadler.commoncrawl.FileHandlingRunnable.run(FileHandlingRunnable.java:64)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1161)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:844)

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-01 Thread Dominik Stadler 
Hi,

results from the mass-testing are in, see
http://people.apache.org/~centic/poi_regression/reports/ for the comparison
between 3.15 and 3.16-beta2, a few newly introduced exceptions, almost all
related to the new EmbeddedExtractor and one exception in HwmfGraphics,
both areas where we added new functionality as far as I remember.

Full results are available at
http://people.apache.org/~centic/poi_regression/reportsAll/

Dominik.


On Wed, Feb 1, 2017 at 1:10 PM, Allison, Timothy B. 
wrote:

> > had some trouble with JDK crashes in Jpeg handling code
>
> Whoa...
>
> Thank you, Dominik!  And, thank you, Javen!
>
> -Original Message-
> From: Dominik Stadler [mailto:dominik.stad...@gmx.at]
> Sent: Wednesday, February 1, 2017 12:27 AM
> To: POI Developers List 
> Subject: RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)
>
> My testing is still running, had some trouble with JDK crashes in Jpeg
> handling code, but as you said it's just a beta.
>
> Dominik.
>
> On Feb 1, 2017 03:11, "Javen O'Neal"  wrote:
>
> > Alright. Just a beta. I'll release it in a few hours.
> >
> > On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:
> >
> > Argh...sorry, no time this go around...
> >
> > -Original Message-
> > From: Javen O'Neal [mailto:one...@apache.org]
> > Sent: Tuesday, January 31, 2017 8:19 PM
> > To: POI Developers List 
> > Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)
> >
> > Should I wait for the results of common crawl or other regression
> > testing before proceeding with the release?
> >
> > On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:
> >
> > > +1 from me
> > >
> > > I have only done a shallow check of the - not any more - usual
> > > suspects, as I'm quite busy with other stuff ... sorry
> > >
> > > Thank you Javen for taking care of this.
> > >
> > > Andi
> > >
> > >
> > > 
> > > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For
> > > additional commands, e-mail: dev-h...@poi.apache.org
> > >
> > >
> >
>

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-02-01 Thread Allison, Timothy B. 
> had some trouble with JDK crashes in Jpeg handling code

Whoa...

Thank you, Dominik!  And, thank you, Javen!

-Original Message-
From: Dominik Stadler [mailto:dominik.stad...@gmx.at] 
Sent: Wednesday, February 1, 2017 12:27 AM
To: POI Developers List 
Subject: RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

My testing is still running, had some trouble with JDK crashes in Jpeg handling 
code, but as you said it's just a beta.

Dominik.

On Feb 1, 2017 03:11, "Javen O'Neal"  wrote:

> Alright. Just a beta. I'll release it in a few hours.
>
> On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:
>
> Argh...sorry, no time this go around...
>
> -Original Message-
> From: Javen O'Neal [mailto:one...@apache.org]
> Sent: Tuesday, January 31, 2017 8:19 PM
> To: POI Developers List 
> Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)
>
> Should I wait for the results of common crawl or other regression 
> testing before proceeding with the release?
>
> On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:
>
> > +1 from me
> >
> > I have only done a shallow check of the - not any more - usual 
> > suspects, as I'm quite busy with other stuff ... sorry
> >
> > Thank you Javen for taking care of this.
> >
> > Andi
> >
> >
> > 
> > - To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For 
> > additional commands, e-mail: dev-h...@poi.apache.org
> >
> >
>

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-31 Thread Dominik Stadler 
My testing is still running, had some trouble with JDK crashes in Jpeg
handling code, but as you said it's just a beta.

Dominik.

On Feb 1, 2017 03:11, "Javen O'Neal"  wrote:

> Alright. Just a beta. I'll release it in a few hours.
>
> On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:
>
> Argh...sorry, no time this go around...
>
> -Original Message-
> From: Javen O'Neal [mailto:one...@apache.org]
> Sent: Tuesday, January 31, 2017 8:19 PM
> To: POI Developers List 
> Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)
>
> Should I wait for the results of common crawl or other regression testing
> before proceeding with the release?
>
> On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:
>
> > +1 from me
> >
> > I have only done a shallow check of the - not any more - usual
> > suspects, as I'm quite busy with other stuff ... sorry
> >
> > Thank you Javen for taking care of this.
> >
> > Andi
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional
> > commands, e-mail: dev-h...@poi.apache.org
> >
> >
>

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-31 Thread Javen O'Neal 
Alright. Just a beta. I'll release it in a few hours.

On Jan 31, 2017 17:49, "Allison, Timothy B."  wrote:

Argh...sorry, no time this go around...

-Original Message-
From: Javen O'Neal [mailto:one...@apache.org]
Sent: Tuesday, January 31, 2017 8:19 PM
To: POI Developers List 
Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

Should I wait for the results of common crawl or other regression testing
before proceeding with the release?

On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:

> +1 from me
>
> I have only done a shallow check of the - not any more - usual
> suspects, as I'm quite busy with other stuff ... sorry
>
> Thank you Javen for taking care of this.
>
> Andi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional
> commands, e-mail: dev-h...@poi.apache.org
>
>

RE: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-31 Thread Allison, Timothy B. 
Argh...sorry, no time this go around...

-Original Message-
From: Javen O'Neal [mailto:one...@apache.org] 
Sent: Tuesday, January 31, 2017 8:19 PM
To: POI Developers List 
Subject: Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

Should I wait for the results of common crawl or other regression testing 
before proceeding with the release?

On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:

> +1 from me
>
> I have only done a shallow check of the - not any more - usual 
> suspects, as I'm quite busy with other stuff ... sorry
>
> Thank you Javen for taking care of this.
>
> Andi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org For additional 
> commands, e-mail: dev-h...@poi.apache.org
>
>

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-31 Thread Javen O'Neal 
Should I wait for the results of common crawl or other regression testing
before proceeding with the release?

On Jan 30, 2017 16:19, "Andreas Beeker"  wrote:

> +1 from me
>
> I have only done a shallow check of the - not any more - usual suspects,
> as I'm quite busy with other stuff ... sorry
>
> Thank you Javen for taking care of this.
>
> Andi
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
> For additional commands, e-mail: dev-h...@poi.apache.org
>
>

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-30 Thread Andreas Beeker 
+1 from me

I have only done a shallow check of the - not any more - usual suspects, as I'm 
quite busy with other stuff ... sorry

Thank you Javen for taking care of this.

Andi


-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-30 Thread Javen O'Neal 
+1 from me.

Still reviewing API changes
https://builds.apache.org/view/POI/job/POI-DSL-API-Check/

On Jan 28, 2017 15:54, "Dominik Stadler"  wrote:

> Hi,
>
> I compared the the files, content looks good, I did not find anything that
> "slipped in".
>
> Also ran tests in various projects with the newer version, everything looks
> good compared to 3.16-beta1.
>
> +1 from me!
>
> Dominik.
>
> On Fri, Jan 27, 2017 at 7:04 PM, Javen O'Neal  wrote:
>
> > Hallo,
> >
> > I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).
> >
> > Copied from the new summary section in the changelog [1], the most
> > notable changes in this release are:
> >
> > - The third-party jar for commons-collections4 is now required for
> handling of OLE2 properties
> > - Primitive (experimental) EMF/WMF text extraction support
> > - Unicode and internationalization improvements
> >
> > In addition, we have made significant progress in several administrative
> areas, thanks to Dominik and Andreas,
> > - Generating Jenkins continuous integration jobs [2] with a Groovy script
> > - Continued work on Gradle build system to eventually replace our Ant
> build system (Ant is still our official build system)
> > - JCmpApi to detect intentional (removing features that have been
> deprecated for at least 2 final releases) and unintentional API breaks
> (binary and source)
> > - SonarCube fixes
> > - fix open file leaks (mostly in unit tests)
> >
> >  https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/
> >
> > What to look for?
> > - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> > my second POI beta release signed with 8BABDD6C, so you
> > may need to import it into your keystore.
> > This key is included in the following KEYS files [3], [4].
> > It is also be found by searching on [5], [6], or most other PGP key
> servers.
> > Steps to verify this are at the end of this email.
> > - add, remove, or modify notable changes. Updating the release notes
> does not require rolling a new release
> > - run common-crawl test
> > - run file leak detector
> > - check for unintentional API breaks with JCmpApi
> >
> > Please vote [7] to release the artifacts. Please vote 0 if everything
> > looks good but you did not have time to test the artifacts in a POI
> > powered application.
> >
> > The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
> > open until we have analyzed the results of common-crawl.
> > If no issues are discovered, the planned release announcement date is
> > Thursday, 2017-02-02.
> >
> > Javen O'Neal
> >
> > Steps to verify the build artifacts:
> > wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
> > gpg --import KEYS
> > (alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
> > svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
> > cd 3.16-beta2-RC1
> > find . -name "*.md5" -type f -execdir md5sum -c {} \;
> > find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
> > find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;
> >
> > More detailed instructions can be found athttps://poi.apache.org/
> download.html#verify
> >
> > [1] https://poi.apache.org/changes.html
> > [2] https://builds.apache.org/view/POI/
> > [3] https://dist.apache.org/repos/dist/dev/poi/KEYS
> > [4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > [5] https://people.apache.org/keys/
> > [6] https://pgp.mit.edu/
> > [7]https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-fractions
> >
> >
>

Re: [VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-28 Thread Dominik Stadler 
Hi,

I compared the the files, content looks good, I did not find anything that
"slipped in".

Also ran tests in various projects with the newer version, everything looks
good compared to 3.16-beta1.

+1 from me!

Dominik.

On Fri, Jan 27, 2017 at 7:04 PM, Javen O'Neal  wrote:

> Hallo,
>
> I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).
>
> Copied from the new summary section in the changelog [1], the most
> notable changes in this release are:
>
> - The third-party jar for commons-collections4 is now required for handling 
> of OLE2 properties
> - Primitive (experimental) EMF/WMF text extraction support
> - Unicode and internationalization improvements
>
> In addition, we have made significant progress in several administrative 
> areas, thanks to Dominik and Andreas,
> - Generating Jenkins continuous integration jobs [2] with a Groovy script
> - Continued work on Gradle build system to eventually replace our Ant build 
> system (Ant is still our official build system)
> - JCmpApi to detect intentional (removing features that have been deprecated 
> for at least 2 final releases) and unintentional API breaks (binary and 
> source)
> - SonarCube fixes
> - fix open file leaks (mostly in unit tests)
>
>  https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/
>
> What to look for?
> - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> my second POI beta release signed with 8BABDD6C, so you
> may need to import it into your keystore.
> This key is included in the following KEYS files [3], [4].
> It is also be found by searching on [5], [6], or most other PGP key servers.
> Steps to verify this are at the end of this email.
> - add, remove, or modify notable changes. Updating the release notes does not 
> require rolling a new release
> - run common-crawl test
> - run file leak detector
> - check for unintentional API breaks with JCmpApi
>
> Please vote [7] to release the artifacts. Please vote 0 if everything
> looks good but you did not have time to test the artifacts in a POI
> powered application.
>
> The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
> open until we have analyzed the results of common-crawl.
> If no issues are discovered, the planned release announcement date is
> Thursday, 2017-02-02.
>
> Javen O'Neal
>
> Steps to verify the build artifacts:
> wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
> gpg --import KEYS
> (alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
> svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
> cd 3.16-beta2-RC1
> find . -name "*.md5" -type f -execdir md5sum -c {} \;
> find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
> find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;
>
> More detailed instructions can be found 
> athttps://poi.apache.org/download.html#verify
>
> [1] https://poi.apache.org/changes.html
> [2] https://builds.apache.org/view/POI/
> [3] https://dist.apache.org/repos/dist/dev/poi/KEYS
> [4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> [5] https://people.apache.org/keys/
> [6] https://pgp.mit.edu/
> [7]https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
>
>

[VOTE] Apache POI 3.16 beta 2 release (RC1)

2017-01-27 Thread Javen O'Neal 
Hallo,

I have prepared artifacts for the release of Apache POI 3.16-beta2 (RC1).

Copied from the new summary section in the changelog [1], the most
notable changes in this release are:

- The third-party jar for commons-collections4 is now required for handling of 
OLE2 properties
- Primitive (experimental) EMF/WMF text extraction support
- Unicode and internationalization improvements

In addition, we have made significant progress in several administrative areas, 
thanks to Dominik and Andreas,
- Generating Jenkins continuous integration jobs [2] with a Groovy script
- Continued work on Gradle build system to eventually replace our Ant build 
system (Ant is still our official build system)
- JCmpApi to detect intentional (removing features that have been deprecated 
for at least 2 final releases) and unintentional API breaks (binary and source)
- SonarCube fixes
- fix open file leaks (mostly in unit tests)

 https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1/

What to look for?
- verify the artifacts' md5 and sha1 hashes and asc signature. This is
my second POI beta release signed with 8BABDD6C, so you
may need to import it into your keystore.
This key is included in the following KEYS files [3], [4].
It is also be found by searching on [5], [6], or most other PGP key servers.
Steps to verify this are at the end of this email.
- add, remove, or modify notable changes. Updating the release notes does not 
require rolling a new release
- run common-crawl test
- run file leak detector
- check for unintentional API breaks with JCmpApi

Please vote [7] to release the artifacts. Please vote 0 if everything
looks good but you did not have time to test the artifacts in a POI
powered application.

The vote stays open for at least 72hrs, 2017-01-31, 23:59 UTC, staying
open until we have analyzed the results of common-crawl.
If no issues are discovered, the planned release announcement date is
Thursday, 2017-02-02.

Javen O'Neal

Steps to verify the build artifacts:
wget https://dist.apache.org/repos/dist/dev/poi/KEYS; gpg --import KEYS
gpg --import KEYS
(alternatively,  gpg --keyserver pgp.mit.edu --recv-key 8BABDD6C)
svn checkout https://dist.apache.org/repos/dist/dev/poi/3.16-beta2-RC1
cd 3.16-beta2-RC1
find . -name "*.md5" -type f -execdir md5sum -c {} \;
find . -name "*.sha1" -type f -execdir sha1sum -c {} \;
find . -name "*.asc" -exec gpg --no-secmem-warning --verify {} \;

More detailed instructions can be found at
https://poi.apache.org/download.html#verify

[1] https://poi.apache.org/changes.html
[2] https://builds.apache.org/view/POI/
[3] https://dist.apache.org/repos/dist/dev/poi/KEYS
[4] https://svn.apache.org/repos/asf/poi/trunk/KEYS
[5] https://people.apache.org/keys/
[6] https://pgp.mit.edu/
[7]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions




signature.asc
Description: OpenPGP digital signature