Thank you very much the feedback Justin:
It's best to put releases at https://dist.apache.org/repos/dist/dev/
I updated the release guidelines [1] with the instruction to use this
SVN space.
The public key used for signing the artifacts can be found at.
The signing key could be added to the KEY file.
We added the public key to the KEY file:
https://dist.apache.org/repos/dist/release/ozone/KEYS
But this fact was not shared in the mail.
I updated the same wiki page with more instructions to add the KEYS file
and asking to share the url of the KEYS file in the vote mail.
While it may not matter in our lifetime, copyright can expire so it would be best to put
the published year in the NOTICE file rather than "Copyright 2006 and onwards".
I think we inherited it from Hadoop.
I created HDDS-5229 to track this, and also created the first PR.
Can you please confirm that it's enough to include the last/current year
(eg. 2021 instead of 2019-2021)
I also "noticed" that NOTICE files are missing from some of the
technical repositories (ozone-docker, ozone-docker-runner,...). We don't
release those repos, but with the same effort I will include default
NOTICE everywhere
I notice a number of dependancies are licensed under " BSD License or the GNU
General Public License (GPL) Version 2.", when something is dual licensed you can
pick the most favourable one. Currently it's a little hard to determine if this code may
contain anything with a Category X license because of the inclusion to the GPL license
text.
Here I created HDDS-5230 to track the issue.
I didn't create the PR yet, but set it to blocker for the next release.
Thanks for all the suggestions,
Marton
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@ozone.apache.org
For additional commands, e-mail: dev-h...@ozone.apache.org
