You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@poi.apache.org by Javen O'Neal <on...@apache.org> on 2016/11/13 12:06:03 UTC
[VOTE] Apache POI 3.16-beta1 release (RC1)
Hallo,
I have prepared artifacts for the release of Apache POI 3.16-beta1 (RC1).
Copied from the new summary section in the changelog [1], the most
notable changes in this release are:
- Initial work on adding a Gradle build, the Ant based build is
currently still the official buildsystem, but there are plans to replace
this with Gradle in the future.
- Add support for password protected files with "Microsoft Enhanced
Cryptographic Provider v1.0"
- Improve support for reading VBA macros
- Examples to encrypt temp files in SXSSF
https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
What to look for?
- verify the artifacts' md5 and sha1 hashes and asc signature. This is
my first POI release and my first release signed with 8BABDD6C, so you
may need to import it into your keystore.
This key is included in the following KEYS files [2], [3].
It is also be found by searching on [4], [5], or most other PGP key servers.
Steps to verify this are at the end of this email.
- add, remove, or modify notable changes. I believe these notes are
separate from the artifacts, so the changes can be updated without
necessarily rolling a new release (though no big deal if this needs done).
- maybe run another common-crawl test
- check for unintentional API breaks
- verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
are fixed in this 3.16 beta
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, 2016-11-17, 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
Wednesday, 2016-11-23.
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-beta1-RC1
cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
[3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
[4] https://people.apache.org/keys/
[5] https://pgp.mit.edu/
[6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
[7]
https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Dominik Stadler <do...@gmx.at>.
Hi,
It only happens when building the released source package, not the SVN
checkout because some files from SVN are missing in the .zip/tar.gz package.
Dominik.
On Mon, Nov 14, 2016 at 7:58 AM, Javen O'Neal <ja...@gmail.com> wrote:
> > One thing that I found is that Ant-target "assemble" fails now because we
> > call the target "maven-pom", but the directory "maven" and the pom.xml
> > files are not included in the source-package..
> "ant clean assemble" works for me on a full svn checkout. Are you
> referring to assemble failing when compiling from source?
>
> I'm fine with leaving build.xml unfrozen. The release tag defines the
> release, not the state of trunk on release day.
> Feel free to commit your changes so that this is fixed in either the
> next beta 1 RC or beta 2.
>
> On Sun, Nov 13, 2016 at 2:07 PM, Dominik Stadler <do...@gmx.at>
> wrote:
> > +1
> >
> > verified the contents of the various packages and did a full build from
> the
> > sources via target "jenkins".
> >
> > One thing that I found is that Ant-target "assemble" fails now because we
> > call the target "maven-pom", but the directory "maven" and the pom.xml
> > files are not included in the source-package..
> >
> > But I think this was also the case in 3.15, seems to have been introduced
> > via http://svn.apache.org/viewvc?view=revision&revision=1733863 as far
> as I
> > see, so I would not hold a beta1 because of that, but rather fix it
> > afterwards for beta2.
> >
> > I will check why our "source rebuild" target in the CI does not stumble
> > across that because it should!
> >
> > BTW, API-comparisons to 3.15 are at https://builds.apache.org/
> > view/POI/job/POI-API-Check/
> >
> > Dominik.
> >
> > On Sun, Nov 13, 2016 at 2:29 PM, Andreas Beeker <ki...@apache.org>
> > wrote:
> >
> >> +1
> >>
> >> I've copy&paste-checked the signatures, checked the archives for clutter
> >> and ran a very small XSLF test project.
> >>
> >> In the release note the "... password ..." line should be replaced by:
> >> - Add support for mixed-length cipher/hashes in password protected files
> >> typically used by Office for Mac
> >> (... I probably should adapt the changelog to ... but we can do this
> after
> >> the release ...)
> >>
> >> As we discussed yesterday in IRC, I think it's difficult to distinguish
> >> between un-/intentional API breaks -
> >> if it's possible with the api diff tool, I would simply provide a
> >> api-break-report.
> >> It would be cool (, if it's not too large/confusing), to diff against
> >> older versions too, as most users will probably update
> >> from an earlier version.
> >>
> >> Andi.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> >> For additional commands, e-mail: dev-help@poi.apache.org
> >>
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <ja...@gmail.com>.
> One thing that I found is that Ant-target "assemble" fails now because we
> call the target "maven-pom", but the directory "maven" and the pom.xml
> files are not included in the source-package..
"ant clean assemble" works for me on a full svn checkout. Are you
referring to assemble failing when compiling from source?
I'm fine with leaving build.xml unfrozen. The release tag defines the
release, not the state of trunk on release day.
Feel free to commit your changes so that this is fixed in either the
next beta 1 RC or beta 2.
On Sun, Nov 13, 2016 at 2:07 PM, Dominik Stadler <do...@gmx.at> wrote:
> +1
>
> verified the contents of the various packages and did a full build from the
> sources via target "jenkins".
>
> One thing that I found is that Ant-target "assemble" fails now because we
> call the target "maven-pom", but the directory "maven" and the pom.xml
> files are not included in the source-package..
>
> But I think this was also the case in 3.15, seems to have been introduced
> via http://svn.apache.org/viewvc?view=revision&revision=1733863 as far as I
> see, so I would not hold a beta1 because of that, but rather fix it
> afterwards for beta2.
>
> I will check why our "source rebuild" target in the CI does not stumble
> across that because it should!
>
> BTW, API-comparisons to 3.15 are at https://builds.apache.org/
> view/POI/job/POI-API-Check/
>
> Dominik.
>
> On Sun, Nov 13, 2016 at 2:29 PM, Andreas Beeker <ki...@apache.org>
> wrote:
>
>> +1
>>
>> I've copy&paste-checked the signatures, checked the archives for clutter
>> and ran a very small XSLF test project.
>>
>> In the release note the "... password ..." line should be replaced by:
>> - Add support for mixed-length cipher/hashes in password protected files
>> typically used by Office for Mac
>> (... I probably should adapt the changelog to ... but we can do this after
>> the release ...)
>>
>> As we discussed yesterday in IRC, I think it's difficult to distinguish
>> between un-/intentional API breaks -
>> if it's possible with the api diff tool, I would simply provide a
>> api-break-report.
>> It would be cool (, if it's not too large/confusing), to diff against
>> older versions too, as most users will probably update
>> from an earlier version.
>>
>> Andi.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
>> For additional commands, e-mail: dev-help@poi.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Dominik Stadler <do...@gmx.at>.
+1
verified the contents of the various packages and did a full build from the
sources via target "jenkins".
One thing that I found is that Ant-target "assemble" fails now because we
call the target "maven-pom", but the directory "maven" and the pom.xml
files are not included in the source-package..
But I think this was also the case in 3.15, seems to have been introduced
via http://svn.apache.org/viewvc?view=revision&revision=1733863 as far as I
see, so I would not hold a beta1 because of that, but rather fix it
afterwards for beta2.
I will check why our "source rebuild" target in the CI does not stumble
across that because it should!
BTW, API-comparisons to 3.15 are at https://builds.apache.org/
view/POI/job/POI-API-Check/
Dominik.
On Sun, Nov 13, 2016 at 2:29 PM, Andreas Beeker <ki...@apache.org>
wrote:
> +1
>
> I've copy&paste-checked the signatures, checked the archives for clutter
> and ran a very small XSLF test project.
>
> In the release note the "... password ..." line should be replaced by:
> - Add support for mixed-length cipher/hashes in password protected files
> typically used by Office for Mac
> (... I probably should adapt the changelog to ... but we can do this after
> the release ...)
>
> As we discussed yesterday in IRC, I think it's difficult to distinguish
> between un-/intentional API breaks -
> if it's possible with the api diff tool, I would simply provide a
> api-break-report.
> It would be cool (, if it's not too large/confusing), to diff against
> older versions too, as most users will probably update
> from an earlier version.
>
> Andi.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <ja...@gmail.com>.
> In the release note the "... password ..." line should be replaced by: ...
Updated changelog in r1769570 [1]
Updated release notes in r16986 [2]
[1] https://svn.apache.org/viewvc?view=revision&revision=1769570
[2] https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/RELEASE-NOTES.txt?r=16986
On Sun, Nov 13, 2016 at 5:29 AM, Andreas Beeker <ki...@apache.org> wrote:
> +1
>
> I've copy&paste-checked the signatures, checked the archives for clutter and ran a very small XSLF test project.
>
> In the release note the "... password ..." line should be replaced by:
> - Add support for mixed-length cipher/hashes in password protected files typically used by Office for Mac
> (... I probably should adapt the changelog to ... but we can do this after the release ...)
>
> As we discussed yesterday in IRC, I think it's difficult to distinguish between un-/intentional API breaks -
> if it's possible with the api diff tool, I would simply provide a api-break-report.
> It would be cool (, if it's not too large/confusing), to diff against older versions too, as most users will probably update
> from an earlier version.
>
> Andi.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Andreas Beeker <ki...@apache.org>.
+1
I've copy&paste-checked the signatures, checked the archives for clutter and ran a very small XSLF test project.
In the release note the "... password ..." line should be replaced by:
- Add support for mixed-length cipher/hashes in password protected files typically used by Office for Mac
(... I probably should adapt the changelog to ... but we can do this after the release ...)
As we discussed yesterday in IRC, I think it's difficult to distinguish between un-/intentional API breaks -
if it's possible with the api diff tool, I would simply provide a api-break-report.
It would be cool (, if it's not too large/confusing), to diff against older versions too, as most users will probably update
from an earlier version.
Andi.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <ja...@gmail.com>.
I met Clint Adams at PyCon US in July at a mini-keysigning party, but he
hasn't signed my key yet. I should bug him again and exchange keys with
more people on biglumber and Apache committers map.
Nick Burch is 3 signatures away from Clint Adams.
https://pgp.cs.uu.nl/paths/D84E41AE/to/B0AE9A02.html
David Fischer is 4 signatures away
https://pgp.cs.uu.nl/paths/3C7705CF/to/B0AE9A02.html
Tim Allison is 3 signatures away
https://pgp.cs.uu.nl/paths/79A7DD28/to/B0AE9A02.html
Mark Thomas (board) is 3 signatures away
https://pgp.cs.uu.nl/paths/2F6059E7/to/B0AE9A02.html
There might be paths for the rest of the POI PMC, but this site only
links keys in the strong web of trust.
That said, if anyone on this mailing list finds themselves in the San
Francisco Bay Area, Los Angeles, or Portland, Oregon USA, I will gladly
meet up for keysigning.
https://people.apache.org/phonebook.html?pmc=poi
https://community.zones.apache.org/map.html
On Tue, Nov 15, 2016 at 11:27 PM, David North <dn...@apache.org> wrote:
> Hi Javen,
>
> Thanks for taking on this release. Hopefully I'll have time to try it
> against our big POI-using projects at work a bit later today.
>
> Meanwhile, it would be good if we could strengthen your PGP key's ties
> to the web of trust - at the moment, you, Dominik and Andreas have
> signed each others' keys, but that graph doesn't link back to a larger
> web. I'm not going to vote against for a beta release on those grounds,
> but it would be a concern for a full release.
>
> I'll be at the ApacheCon Europe keysigning tomorrow night, so perhaps
> there will be someone there who is geographically local one of you
> three, so my signing their key will allow them to bridge the gap.
>
> Thanks,
> David
>
> On 13/11/16 12:06, Javen O'Neal wrote:
>> Hallo,
>>
>> I have prepared artifacts for the release of Apache POI 3.16-beta1 (RC1).
>>
>> Copied from the new summary section in the changelog [1], the most
>> notable changes in this release are:
>>
>> - Initial work on adding a Gradle build, the Ant based build is
>> currently still the official buildsystem, but there are plans to replace
>> this with Gradle in the future.
>> - Add support for password protected files with "Microsoft Enhanced
>> Cryptographic Provider v1.0"
>> - Improve support for reading VBA macros
>> - Examples to encrypt temp files in SXSSF
>>
>> https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
>>
>> What to look for?
>> - verify the artifacts' md5 and sha1 hashes and asc signature. This is
>> my first POI release and my first release signed with 8BABDD6C, so you
>> may need to import it into your keystore.
>> This key is included in the following KEYS files [2], [3].
>> It is also be found by searching on [4], [5], or most other PGP key servers.
>> Steps to verify this are at the end of this email.
>> - add, remove, or modify notable changes. I believe these notes are
>> separate from the artifacts, so the changes can be updated without
>> necessarily rolling a new release (though no big deal if this needs done).
>> - maybe run another common-crawl test
>> - check for unintentional API breaks
>> - verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
>> are fixed in this 3.16 beta
>>
>> 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, 2016-11-17, 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
>> Wednesday, 2016-11-23.
>>
>> 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-beta1-RC1
>> cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
>> [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
>> [4] https://people.apache.org/keys/
>> [5] https://pgp.mit.edu/
>> [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
>> [7]
>> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
>>
>
> --
> David North | www.dnorth.net
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by David North <dn...@apache.org>.
Hi Javen,
Thanks for taking on this release. Hopefully I'll have time to try it
against our big POI-using projects at work a bit later today.
Meanwhile, it would be good if we could strengthen your PGP key's ties
to the web of trust - at the moment, you, Dominik and Andreas have
signed each others' keys, but that graph doesn't link back to a larger
web. I'm not going to vote against for a beta release on those grounds,
but it would be a concern for a full release.
I'll be at the ApacheCon Europe keysigning tomorrow night, so perhaps
there will be someone there who is geographically local one of you
three, so my signing their key will allow them to bridge the gap.
Thanks,
David
On 13/11/16 12:06, Javen O'Neal wrote:
> Hallo,
>
> I have prepared artifacts for the release of Apache POI 3.16-beta1 (RC1).
>
> Copied from the new summary section in the changelog [1], the most
> notable changes in this release are:
>
> - Initial work on adding a Gradle build, the Ant based build is
> currently still the official buildsystem, but there are plans to replace
> this with Gradle in the future.
> - Add support for password protected files with "Microsoft Enhanced
> Cryptographic Provider v1.0"
> - Improve support for reading VBA macros
> - Examples to encrypt temp files in SXSSF
>
> https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
>
> What to look for?
> - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> my first POI release and my first release signed with 8BABDD6C, so you
> may need to import it into your keystore.
> This key is included in the following KEYS files [2], [3].
> It is also be found by searching on [4], [5], or most other PGP key servers.
> Steps to verify this are at the end of this email.
> - add, remove, or modify notable changes. I believe these notes are
> separate from the artifacts, so the changes can be updated without
> necessarily rolling a new release (though no big deal if this needs done).
> - maybe run another common-crawl test
> - check for unintentional API breaks
> - verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
> are fixed in this 3.16 beta
>
> 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, 2016-11-17, 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
> Wednesday, 2016-11-23.
>
> 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-beta1-RC1
> cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> [4] https://people.apache.org/keys/
> [5] https://pgp.mit.edu/
> [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> [7]
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-fractions
>
--
David North | www.dnorth.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <on...@apache.org>.
Glad to hear you found no binary incompatibility issues.
On Nov 15, 2016 1:45 PM, "Greg Woolsey" <gr...@gmail.com> wrote:
> +1 from me. Tested this build with a complex app compiled against 3.15,
> and don't see any issues.
>
> Greg
>
> TL/DR
> Tested with an app built using Vaadin 7.6.6, with Vaadin Spreadsheet
> 1.3.0-alpha1, loading and manipulating XLSX files with tables, formatting,
> conditional formatting, pivots, charts, and ODBC queries.
>
> On Mon, Nov 14, 2016 at 6:37 PM Javen O'Neal <on...@apache.org> wrote:
>
> > +1 from me.
> >
> > On Nov 14, 2016 1:27 PM, "Dominik Stadler" <do...@gmx.at>
> wrote:
> >
> > > Hi,
> > >
> > > Regression testing looks also good, no new failure at all, details at
> > > http://people.apache.org/~centic/poi_regression/reports/ and
> > > http://people.apache.org/~centic/poi_regression/reportsAll/
> > >
> > > Dominik.
> > >
> > > On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov <ye...@dinom.ru>
> > > wrote:
> > >
> > > > +1
> > > >
> > > > Yegor
> > > >
> > > > On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org>
> > wrote:
> > > >
> > > > > Hallo,
> > > > >
> > > > > I have prepared artifacts for the release of Apache POI 3.16-beta1
> > > (RC1).
> > > > >
> > > > > Copied from the new summary section in the changelog [1], the most
> > > > > notable changes in this release are:
> > > > >
> > > > > - Initial work on adding a Gradle build, the Ant based build is
> > > > > currently still the official buildsystem, but there are plans to
> > > replace
> > > > > this with Gradle in the future.
> > > > > - Add support for password protected files with "Microsoft Enhanced
> > > > > Cryptographic Provider v1.0"
> > > > > - Improve support for reading VBA macros
> > > > > - Examples to encrypt temp files in SXSSF
> > > > >
> > > > > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
> > > > >
> > > > > What to look for?
> > > > > - verify the artifacts' md5 and sha1 hashes and asc signature. This
> > is
> > > > > my first POI release and my first release signed with 8BABDD6C, so
> > you
> > > > > may need to import it into your keystore.
> > > > > This key is included in the following KEYS files [2], [3].
> > > > > It is also be found by searching on [4], [5], or most other PGP key
> > > > > servers.
> > > > > Steps to verify this are at the end of this email.
> > > > > - add, remove, or modify notable changes. I believe these notes are
> > > > > separate from the artifacts, so the changes can be updated without
> > > > > necessarily rolling a new release (though no big deal if this needs
> > > > done).
> > > > > - maybe run another common-crawl test
> > > > > - check for unintentional API breaks
> > > > > - verify enum-related (bug 59836 [6]) unintentional API breaks in
> > 3.15
> > > > > are fixed in this 3.16 beta
> > > > >
> > > > > 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, 2016-11-17, 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
> > > > > Wednesday, 2016-11-23.
> > > > >
> > > > > 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-beta1-RC1
> > > > > cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> > > > > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > > > > [4] https://people.apache.org/keys/
> > > > > [5] https://pgp.mit.edu/
> > > > > [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> > > > > [7]
> > > > > https://www.apache.org/foundation/voting.html#
> > > > expressing-votes-1-0-1-and-
> > > > > fractions
> > > > >
> > > > >
> > > >
> > >
> >
>
RE: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <ja...@gmail.com>.
I still need to figure out how to deploy to dist/release and maven central.
I will update that section of the release guide when I figure out what I
need to do.
On Nov 18, 2016 13:34, "kiwiwings" <ki...@apache.org> wrote:
> Thank you Javen for rolling this release - it seemed to be quite smooth :)
>
> Andi
>
>
>
> --
> View this message in context: http://apache-poi.1045710.n5.
> nabble.com/VOTE-Apache-POI-3-16-beta1-release-RC1-tp5725616p5725696.html
> Sent from the POI - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
> For additional commands, e-mail: dev-help@poi.apache.org
>
>
RE: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by kiwiwings <ki...@apache.org>.
Thank you Javen for rolling this release - it seemed to be quite smooth :)
Andi
--
View this message in context: http://apache-poi.1045710.n5.nabble.com/VOTE-Apache-POI-3-16-beta1-release-RC1-tp5725616p5725696.html
Sent from the POI - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
RE: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <on...@apache.org>.
This vote passes with five +1's and one 0.
On Nov 16, 2016 12:53, "Allison, Timothy B." <tallison@mitre.org
<ma...@mitre.org>> wrote:
+1
Apologies for delay. Finished running comparisons against ~800k files.
Quick look interpretation: more attachments, fewer exceptions (esp
in visio), no new exceptions, better content, esp in macros.
http://162.242.228.174/reports/reports_3_16-rc1.zip
<http://162.242.228.174/reports/reports_3_16-rc1.zip>
-----Original Message-----
From: Greg Woolsey [mailto:greg.woolsey@gmail.com
<ma...@gmail.com>]
Sent: Tuesday, November 15, 2016 4:46 PM
To: POI Developers List <dev@poi.apache.org <ma...@poi.apache.org>>
Subject: Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
+1 from me. Tested this build with a complex app compiled against 3.15,
and don't see any issues.
Greg
TL/DR
Tested with an app built using Vaadin 7.6.6, with Vaadin Spreadsheet
1.3.0-alpha1, loading and manipulating XLSX files with tables,
formatting, conditional formatting, pivots, charts, and ODBC queries.
On Mon, Nov 14, 2016 at 6:37 PM Javen O'Neal <onealj@apache.org
<ma...@apache.org>> wrote:
> +1 from me.
>
> On Nov 14, 2016 1:27 PM, "Dominik Stadler" <dominik.stadler@gmx.at
<ma...@gmx.at>> wrote:
>
> > Hi,
> >
> > Regression testing looks also good, no new failure at all, details
> > at http://people.apache.org/~centic/poi_regression/reports/
<http://people.apache.org/%7Ecentic/poi_regression/reports/> and
> > http://people.apache.org/~centic/poi_regression/reportsAll/
<http://people.apache.org/%7Ecentic/poi_regression/reportsAll/>
> >
> > Dominik.
> >
> > On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov
> > <yegor.kozlov@dinom.ru <ma...@dinom.ru>>
> > wrote:
> >
> > > +1
> > >
> > > Yegor
> > >
> > > On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal
<onealj@apache.org <ma...@apache.org>>
> wrote:
> > >
> > > > Hallo,
> > > >
> > > > I have prepared artifacts for the release of Apache POI
> > > > 3.16-beta1
> > (RC1).
> > > >
> > > > Copied from the new summary section in the changelog [1], the
> > > > most notable changes in this release are:
> > > >
> > > > - Initial work on adding a Gradle build, the Ant based build is
> > > > currently still the official buildsystem, but there are plans to
> > replace
> > > > this with Gradle in the future.
> > > > - Add support for password protected files with "Microsoft
> > > > Enhanced Cryptographic Provider v1.0"
> > > > - Improve support for reading VBA macros
> > > > - Examples to encrypt temp files in SXSSF
> > > >
> > > > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
<https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/>
> > > >
> > > > What to look for?
> > > > - verify the artifacts' md5 and sha1 hashes and asc signature.
> > > > This
> is
> > > > my first POI release and my first release signed with 8BABDD6C,
> > > > so
> you
> > > > may need to import it into your keystore.
> > > > This key is included in the following KEYS files [2], [3].
> > > > It is also be found by searching on [4], [5], or most other PGP
> > > > key servers.
> > > > Steps to verify this are at the end of this email.
> > > > - add, remove, or modify notable changes. I believe these notes
> > > > are separate from the artifacts, so the changes can be updated
> > > > without necessarily rolling a new release (though no big deal if
> > > > this needs
> > > done).
> > > > - maybe run another common-crawl test
> > > > - check for unintentional API breaks
> > > > - verify enum-related (bug 59836 [6]) unintentional API breaks
> > > > in
> 3.15
> > > > are fixed in this 3.16 beta
> > > >
> > > > 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, 2016-11-17, 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 Wednesday, 2016-11-23.
> > > >
> > > > Javen O'Neal
> > > >
> > > > Steps to verify the build artifacts:
> > > > wget https://dist.apache.org/repos/dist/dev/poi/KEYS
<https://dist.apache.org/repos/dist/dev/poi/KEYS>; gpg
> > > > --import
> > KEYS
> > > > gpg --import KEYS
> > > > (alternatively, gpg --keyserver pgp.mit.edu
<http://pgp.mit.edu> --recv-key
> > > > 8BABDD6C) svn checkout
> https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1
<https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1>
> > > > cd 3.16-beta1-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
<https://poi.apache.org/download.html#verify>
> > > >
> > > > [1] https://poi.apache.org/changes.html
<https://poi.apache.org/changes.html>
> > > > [2] https://dist.apache.org/repos/dist/dev/poi/KEYS
<https://dist.apache.org/repos/dist/dev/poi/KEYS>
> > > > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
<https://svn.apache.org/repos/asf/poi/trunk/KEYS>
> > > > [4] https://people.apache.org/keys/
<https://people.apache.org/keys/> [5] https://pgp.mit.edu/ [6]
> > > > https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
<https://bz.apache.org/bugzilla/show_bug.cgi?id=59836>
> > > > [7]
> > > > https://www.apache.org/foundation/voting.html#
<https://www.apache.org/foundation/voting.html#>
> > > expressing-votes-1-0-1-and-
> > > > fractions
> > > >
> > > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
<ma...@poi.apache.org>
For additional commands, e-mail: dev-help@poi.apache.org
<ma...@poi.apache.org>
RE: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by "Allison, Timothy B." <ta...@mitre.org>.
+1
Apologies for delay. Finished running comparisons against ~800k files.
Quick look interpretation: more attachments, fewer exceptions (esp in visio), no new exceptions, better content, esp in macros.
http://162.242.228.174/reports/reports_3_16-rc1.zip
-----Original Message-----
From: Greg Woolsey [mailto:greg.woolsey@gmail.com]
Sent: Tuesday, November 15, 2016 4:46 PM
To: POI Developers List <de...@poi.apache.org>
Subject: Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
+1 from me. Tested this build with a complex app compiled against 3.15,
and don't see any issues.
Greg
TL/DR
Tested with an app built using Vaadin 7.6.6, with Vaadin Spreadsheet 1.3.0-alpha1, loading and manipulating XLSX files with tables, formatting, conditional formatting, pivots, charts, and ODBC queries.
On Mon, Nov 14, 2016 at 6:37 PM Javen O'Neal <on...@apache.org> wrote:
> +1 from me.
>
> On Nov 14, 2016 1:27 PM, "Dominik Stadler" <do...@gmx.at> wrote:
>
> > Hi,
> >
> > Regression testing looks also good, no new failure at all, details
> > at http://people.apache.org/~centic/poi_regression/reports/ and
> > http://people.apache.org/~centic/poi_regression/reportsAll/
> >
> > Dominik.
> >
> > On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov
> > <ye...@dinom.ru>
> > wrote:
> >
> > > +1
> > >
> > > Yegor
> > >
> > > On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org>
> wrote:
> > >
> > > > Hallo,
> > > >
> > > > I have prepared artifacts for the release of Apache POI
> > > > 3.16-beta1
> > (RC1).
> > > >
> > > > Copied from the new summary section in the changelog [1], the
> > > > most notable changes in this release are:
> > > >
> > > > - Initial work on adding a Gradle build, the Ant based build is
> > > > currently still the official buildsystem, but there are plans to
> > replace
> > > > this with Gradle in the future.
> > > > - Add support for password protected files with "Microsoft
> > > > Enhanced Cryptographic Provider v1.0"
> > > > - Improve support for reading VBA macros
> > > > - Examples to encrypt temp files in SXSSF
> > > >
> > > > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
> > > >
> > > > What to look for?
> > > > - verify the artifacts' md5 and sha1 hashes and asc signature.
> > > > This
> is
> > > > my first POI release and my first release signed with 8BABDD6C,
> > > > so
> you
> > > > may need to import it into your keystore.
> > > > This key is included in the following KEYS files [2], [3].
> > > > It is also be found by searching on [4], [5], or most other PGP
> > > > key servers.
> > > > Steps to verify this are at the end of this email.
> > > > - add, remove, or modify notable changes. I believe these notes
> > > > are separate from the artifacts, so the changes can be updated
> > > > without necessarily rolling a new release (though no big deal if
> > > > this needs
> > > done).
> > > > - maybe run another common-crawl test
> > > > - check for unintentional API breaks
> > > > - verify enum-related (bug 59836 [6]) unintentional API breaks
> > > > in
> 3.15
> > > > are fixed in this 3.16 beta
> > > >
> > > > 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, 2016-11-17, 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 Wednesday, 2016-11-23.
> > > >
> > > > 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-beta1-RC1
> > > > cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> > > > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > > > [4] https://people.apache.org/keys/ [5] https://pgp.mit.edu/ [6]
> > > > https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> > > > [7]
> > > > https://www.apache.org/foundation/voting.html#
> > > expressing-votes-1-0-1-and-
> > > > fractions
> > > >
> > > >
> > >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@poi.apache.org
For additional commands, e-mail: dev-help@poi.apache.org
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Greg Woolsey <gr...@gmail.com>.
+1 from me. Tested this build with a complex app compiled against 3.15,
and don't see any issues.
Greg
TL/DR
Tested with an app built using Vaadin 7.6.6, with Vaadin Spreadsheet
1.3.0-alpha1, loading and manipulating XLSX files with tables, formatting,
conditional formatting, pivots, charts, and ODBC queries.
On Mon, Nov 14, 2016 at 6:37 PM Javen O'Neal <on...@apache.org> wrote:
> +1 from me.
>
> On Nov 14, 2016 1:27 PM, "Dominik Stadler" <do...@gmx.at> wrote:
>
> > Hi,
> >
> > Regression testing looks also good, no new failure at all, details at
> > http://people.apache.org/~centic/poi_regression/reports/ and
> > http://people.apache.org/~centic/poi_regression/reportsAll/
> >
> > Dominik.
> >
> > On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov <ye...@dinom.ru>
> > wrote:
> >
> > > +1
> > >
> > > Yegor
> > >
> > > On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org>
> wrote:
> > >
> > > > Hallo,
> > > >
> > > > I have prepared artifacts for the release of Apache POI 3.16-beta1
> > (RC1).
> > > >
> > > > Copied from the new summary section in the changelog [1], the most
> > > > notable changes in this release are:
> > > >
> > > > - Initial work on adding a Gradle build, the Ant based build is
> > > > currently still the official buildsystem, but there are plans to
> > replace
> > > > this with Gradle in the future.
> > > > - Add support for password protected files with "Microsoft Enhanced
> > > > Cryptographic Provider v1.0"
> > > > - Improve support for reading VBA macros
> > > > - Examples to encrypt temp files in SXSSF
> > > >
> > > > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
> > > >
> > > > What to look for?
> > > > - verify the artifacts' md5 and sha1 hashes and asc signature. This
> is
> > > > my first POI release and my first release signed with 8BABDD6C, so
> you
> > > > may need to import it into your keystore.
> > > > This key is included in the following KEYS files [2], [3].
> > > > It is also be found by searching on [4], [5], or most other PGP key
> > > > servers.
> > > > Steps to verify this are at the end of this email.
> > > > - add, remove, or modify notable changes. I believe these notes are
> > > > separate from the artifacts, so the changes can be updated without
> > > > necessarily rolling a new release (though no big deal if this needs
> > > done).
> > > > - maybe run another common-crawl test
> > > > - check for unintentional API breaks
> > > > - verify enum-related (bug 59836 [6]) unintentional API breaks in
> 3.15
> > > > are fixed in this 3.16 beta
> > > >
> > > > 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, 2016-11-17, 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
> > > > Wednesday, 2016-11-23.
> > > >
> > > > 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-beta1-RC1
> > > > cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> > > > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > > > [4] https://people.apache.org/keys/
> > > > [5] https://pgp.mit.edu/
> > > > [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> > > > [7]
> > > > https://www.apache.org/foundation/voting.html#
> > > expressing-votes-1-0-1-and-
> > > > fractions
> > > >
> > > >
> > >
> >
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Javen O'Neal <on...@apache.org>.
+1 from me.
On Nov 14, 2016 1:27 PM, "Dominik Stadler" <do...@gmx.at> wrote:
> Hi,
>
> Regression testing looks also good, no new failure at all, details at
> http://people.apache.org/~centic/poi_regression/reports/ and
> http://people.apache.org/~centic/poi_regression/reportsAll/
>
> Dominik.
>
> On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov <ye...@dinom.ru>
> wrote:
>
> > +1
> >
> > Yegor
> >
> > On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org> wrote:
> >
> > > Hallo,
> > >
> > > I have prepared artifacts for the release of Apache POI 3.16-beta1
> (RC1).
> > >
> > > Copied from the new summary section in the changelog [1], the most
> > > notable changes in this release are:
> > >
> > > - Initial work on adding a Gradle build, the Ant based build is
> > > currently still the official buildsystem, but there are plans to
> replace
> > > this with Gradle in the future.
> > > - Add support for password protected files with "Microsoft Enhanced
> > > Cryptographic Provider v1.0"
> > > - Improve support for reading VBA macros
> > > - Examples to encrypt temp files in SXSSF
> > >
> > > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
> > >
> > > What to look for?
> > > - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> > > my first POI release and my first release signed with 8BABDD6C, so you
> > > may need to import it into your keystore.
> > > This key is included in the following KEYS files [2], [3].
> > > It is also be found by searching on [4], [5], or most other PGP key
> > > servers.
> > > Steps to verify this are at the end of this email.
> > > - add, remove, or modify notable changes. I believe these notes are
> > > separate from the artifacts, so the changes can be updated without
> > > necessarily rolling a new release (though no big deal if this needs
> > done).
> > > - maybe run another common-crawl test
> > > - check for unintentional API breaks
> > > - verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
> > > are fixed in this 3.16 beta
> > >
> > > 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, 2016-11-17, 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
> > > Wednesday, 2016-11-23.
> > >
> > > 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-beta1-RC1
> > > cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> > > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > > [4] https://people.apache.org/keys/
> > > [5] https://pgp.mit.edu/
> > > [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> > > [7]
> > > https://www.apache.org/foundation/voting.html#
> > expressing-votes-1-0-1-and-
> > > fractions
> > >
> > >
> >
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Dominik Stadler <do...@gmx.at>.
Hi,
Regression testing looks also good, no new failure at all, details at
http://people.apache.org/~centic/poi_regression/reports/ and
http://people.apache.org/~centic/poi_regression/reportsAll/
Dominik.
On Mon, Nov 14, 2016 at 4:35 PM, Yegor Kozlov <ye...@dinom.ru> wrote:
> +1
>
> Yegor
>
> On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org> wrote:
>
> > Hallo,
> >
> > I have prepared artifacts for the release of Apache POI 3.16-beta1 (RC1).
> >
> > Copied from the new summary section in the changelog [1], the most
> > notable changes in this release are:
> >
> > - Initial work on adding a Gradle build, the Ant based build is
> > currently still the official buildsystem, but there are plans to replace
> > this with Gradle in the future.
> > - Add support for password protected files with "Microsoft Enhanced
> > Cryptographic Provider v1.0"
> > - Improve support for reading VBA macros
> > - Examples to encrypt temp files in SXSSF
> >
> > https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
> >
> > What to look for?
> > - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> > my first POI release and my first release signed with 8BABDD6C, so you
> > may need to import it into your keystore.
> > This key is included in the following KEYS files [2], [3].
> > It is also be found by searching on [4], [5], or most other PGP key
> > servers.
> > Steps to verify this are at the end of this email.
> > - add, remove, or modify notable changes. I believe these notes are
> > separate from the artifacts, so the changes can be updated without
> > necessarily rolling a new release (though no big deal if this needs
> done).
> > - maybe run another common-crawl test
> > - check for unintentional API breaks
> > - verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
> > are fixed in this 3.16 beta
> >
> > 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, 2016-11-17, 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
> > Wednesday, 2016-11-23.
> >
> > 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-beta1-RC1
> > cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> > [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> > [4] https://people.apache.org/keys/
> > [5] https://pgp.mit.edu/
> > [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> > [7]
> > https://www.apache.org/foundation/voting.html#
> expressing-votes-1-0-1-and-
> > fractions
> >
> >
>
Re: [VOTE] Apache POI 3.16-beta1 release (RC1)
Posted by Yegor Kozlov <ye...@dinom.ru>.
+1
Yegor
On Sun, Nov 13, 2016 at 3:06 PM, Javen O'Neal <on...@apache.org> wrote:
> Hallo,
>
> I have prepared artifacts for the release of Apache POI 3.16-beta1 (RC1).
>
> Copied from the new summary section in the changelog [1], the most
> notable changes in this release are:
>
> - Initial work on adding a Gradle build, the Ant based build is
> currently still the official buildsystem, but there are plans to replace
> this with Gradle in the future.
> - Add support for password protected files with "Microsoft Enhanced
> Cryptographic Provider v1.0"
> - Improve support for reading VBA macros
> - Examples to encrypt temp files in SXSSF
>
> https://dist.apache.org/repos/dist/dev/poi/3.16-beta1-RC1/
>
> What to look for?
> - verify the artifacts' md5 and sha1 hashes and asc signature. This is
> my first POI release and my first release signed with 8BABDD6C, so you
> may need to import it into your keystore.
> This key is included in the following KEYS files [2], [3].
> It is also be found by searching on [4], [5], or most other PGP key
> servers.
> Steps to verify this are at the end of this email.
> - add, remove, or modify notable changes. I believe these notes are
> separate from the artifacts, so the changes can be updated without
> necessarily rolling a new release (though no big deal if this needs done).
> - maybe run another common-crawl test
> - check for unintentional API breaks
> - verify enum-related (bug 59836 [6]) unintentional API breaks in 3.15
> are fixed in this 3.16 beta
>
> 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, 2016-11-17, 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
> Wednesday, 2016-11-23.
>
> 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-beta1-RC1
> cd 3.16-beta1-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://dist.apache.org/repos/dist/dev/poi/KEYS
> [3] https://svn.apache.org/repos/asf/poi/trunk/KEYS
> [4] https://people.apache.org/keys/
> [5] https://pgp.mit.edu/
> [6] https://bz.apache.org/bugzilla/show_bug.cgi?id=59836
> [7]
> https://www.apache.org/foundation/voting.html#expressing-votes-1-0-1-and-
> fractions
>
>
Re: [VOTE] Apache POI 3.16-beta2 release (RC1)
Posted by Javen O'Neal <on...@apache.org>.
Please disregard this email chain and respond to the other [VOTE] 3.16 beta
2 email chain.
On Jan 27, 2017 12:58 AM, "Javen O'Neal" <on...@apache.org> 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 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
>
>
>
[VOTE] Apache POI 3.16-beta2 release (RC1)
Posted by Javen O'Neal <on...@apache.org>.
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