On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau <tnad...@apache.org> wrote:
> I updated the script and pushed the artifacts again. The issue is that > test.pypi.org does not let you change artifacts once they've been pushed, > so I cannot delete the one I pushed to replace it with the updated one. > This should not be an issue, as you can test/verify everything else and > when I push to the real pypi after everyone checks this out, we should be > ok. > > BTW there is a bug in the asf-release script that has issues if you re-push > onto an existing release. The script should delete the target (or attempt > to) before it svn adds the new artifacts. I can fix that once the smoke has > cleared with this release. > > Cool, that'll be useful. I reviewed the release. I thought there was a downloads page on http://ariatosca.apache.org/ we need to add one after this release goes out. You can use http://deltaspike.apache.org/download.html as an example of one that works and is comprehensive. It would be good to have instructions on how to run the verification steps (I can't find the KEYS file). but I'm +1 from a licensing point of view. > --Tom > > > > On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament <johndam...@apache.org> > wrote: > > > Can you use the one that is checked in ? > > https://github.com/apache/incubator-ariatosca/blob/ > > master/release/asf-release.sh#L138 > > > > > > On Thu, Jan 4, 2018 at 11:37 AM Thomas Nadeau <tnadeaua...@gmail.com> > > wrote: > > > > > The asf-release.sh script we are currently using names them as they > are: > > > > > > function _sign_package { > > > local ARCHIVE_NAME=$1 > > > > > > echo "Signing archive ${ARCHIVE_NAME}..." > > > gpg --armor --output ${ARCHIVE_NAME}.asc --detach-sig > ${ARCHIVE_NAME} > > > gpg --print-md MD5 ${ARCHIVE_NAME} > ${ARCHIVE_NAME}.md5 > > > gpg --print-md SHA512 ${ARCHIVE_NAME} > ${ARCHIVE_NAME}.sha > > > } > > > > > > > > > I can change that to sha512 now. > > > > > > --Tom > > > > > > > > > > > > On Thu, Jan 4, 2018 at 11:14 AM, John D. Ament <johndam...@apache.org> > > > wrote: > > > > > > > Thomas, > > > > > > > > The files are still named "sha" instead of "sha512" > > > > > > > > John > > > > > > > > On Thu, Jan 4, 2018 at 10:59 AM Thomas Nadeau <tnad...@apache.org> > > > wrote: > > > > > > > > > Aria Community: > > > > > > > > > > This is a vote to release Apache AriaTosca (Incubating) 0.2.0. If > the > > > > vote > > > > > passes, another vote for approving the release will take place on > the > > > > > Apache Incubator's PMC. Please verify the various release artifacts > > and > > > > > respond to the list with your results. Instructions for locating > the > > > > > artifacts can be found below. > > > > > > > > > > The tarball candidate for the 0.2.0 release is in ARIA's /dist/dev > > > > folder: > > > > > * > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ > > > > 0.2.0-incubating/ > > > > > < > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ > > > > 0.2.0-incubating/ > > > > > >* > > > > > > > > > > The testing/staging pypi version can be found here: > > > > > https://test.pypi.org/project/apache-ariatosca/ > > > > > Instructions for installation etc. may be found in the README file > > > inside > > > > > the tarball. Note there are different instructions for downloading > > and > > > > > installing from test.pypi, so please refer to test.pypi.org for > > > > > instructions. The list of resolved issues for this release are > > simply > > > > all > > > > > the issues that have been resolved thus far since the last release. > > > Those > > > > > can be found here: > https://issues.apache.org/jira/secure/RapidBoard. > > > > > jspa?rapidView=150&projectKey=ARIA&view=planning& > > selectedIssue=ARIA-394 > > > > > <https://issues.apache.org/jira/secure/RapidBoard.jspa? > > > > rapidView=150&projectKey=ARIA&view=planning&selectedIssue=ARIA-394> > > > > > Please vote to publish this tarball on ARIA's /dist/release folder > > and > > > > > release on pypi. The voting for this must be open for 3 full days > to > > > all > > > > > Committers within the project, and then for 3 full days on the > Apache > > > > PMC. > > > > > Voting for the release will begin now at 12PM EST, Thursday, > January > > > 4, > > > > > 2018 and be completed on 12PM EST on Sunday, January 7, 2018. > > > > > > > > > > Thanks, > > > > > > > > > > --Tom > > > > > > > > > > > > > > >
