On 16/12/2019 13:26, Shawn McKinney wrote:
On Dec 15, 2019, at 10:54 AM, Emmanuel Lécharny <[email protected]> wrote:
Congrats, Shawn !
Two remarks :
- the 2.0.4 was visible on teh web site before the vote was closed, AFAICT. Did
you pushed the web site before ?
Hi Emmanuel. Thanks for your attention.
Yes, I did publish the website changes (before the vote closed), but did not
publish the artifacts to maven or apache. Next time, I’ll wait until after the
vote to publish the website changes.
Usually, what I do is that I push the updates on staging, and the
javadoc on prod, and wait before the announcement to be made to push the
site. Sadly, if someone else publish the site, you are screwed. There is
also something to check regarding the extpaths and .htaccess in this
very case, otherwise it's very possible that the javadoc gets removed
during a publish. Tricky...
- there is a news missing on http://directory.apache.org/fortress/ for 2.0.4
otherwise, all is ok !
Yes, this has been an ongoing issue with me and our website. If you click on
the news, the latest. However, it doesn’t show on the landing page. I’ve yet
to determine why this happens.
Yes, very strange...
Another issue, sent via email, after the announcement:
*** Begin excerpt:
Sorry, but there is an issue with the binary download page.
Each archive has both a download icon with a link and separate a text
download link.
This is not ideal, as the links may be different.
In fact one of the icons has a broken link (fortress-realm-2.0.4.jar).
Please fix, and resubmit the announce email once this has been done and
checked.
I'll fix that.
Thanks !
—
Shawn
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
