Hi PJ,
On 8/27/18 12:00 PM, pj.fanning wrote:
> Hi Andi,
>
> I'm not sure how to sign an announce email. It also doesn't seem to be
> common on https://lists.apache.org/list.html?annou...@apache.org to have
> signed emails.
You are right ... I couldn't find a reference noting that a release
anno
Hi Andi,
I'm not sure how to sign an announce email. It also doesn't seem to be
common on https://lists.apache.org/list.html?annou...@apache.org to have
signed emails.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
--
Hi PJ,
I've regenerated the website - basically you need to set the FORREST_HOME
environment variable
and call $FORREST_HOME/bin/forrest. I've adapted the ant script to the POI
version.
Find an example for the announcement mail under ...
http://apache-poi.1045710.n5.nabble.com/ANNOUNCE-Apache-X
Hi Andi,
I've done most of the pieces for the release.
The items that are incomplete are:
* Regenerating the xmlbeans site html using Forrest
* Announcing the release
I'm not sure of the exact command to use Forrest in the xmlbeans setup.
I'm also not sure what `Announcing the release` entails.
I have a look at doing all the items on the release list at the weekend.
--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-Dev-f2312866.html
-
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional comman
Hi PJ,
> I'd prefer not to wait for INFRA-14923. Even Sonatype's Nexus only adds md5
> and sha1 digests.
ACK to not wait for INFRA, but for nexus, I thought you have to provide the
hashes in the upload?! -
at least that's what the POI release script is doing.
So you haven't generated the *.asc.m
I'd prefer not to wait for INFRA-14923. Even Sonatype's Nexus only adds md5
and sha1 digests.
These are generated by Nexus, as opposed to publisher's adding their own
digest files.
I have done some checking on maven central and in the cross section I
checked, no jars had sha256 or sha512 digests.
The vote has passed with 3x +1 from POI / XmlBeans PMCs.
Before we release the nexus staging repo, we might check if SHA-256/SHA-512 now
works -
probably not because of INFRA-14923.
And maybe we should remove the *.md5, *.asc.md5, *.asc.sha1 files to keep the
maven repo tidy.
... and for the si
