Re: [VOTE] publish ariatosca 0.2.0

The vote status on the 0.2.0 release candidate is: There were 4 positive binding votes from Tom, Tal, Suneel, Maxim There were no negative votes, so the release vote now will be pushed to the Apache PMC. Thank you, --Tom On Thu, Jan 4, 2018 at 11:54 AM, Thomas Nadeau

Re: [VOTE] publish ariatosca 0.2.0

+1 binding On Fri, Jan 5, 2018 at 12:04 PM, John D. Ament wrote: > On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau wrote: > > > I updated the script and pushed the artifacts again. The issue is that > > test.pypi.org does not let you change artifacts

Re: [VOTE] publish ariatosca 0.2.0

> On Jan 5, 2018, at 12:04 PM, John D. Ament wrote: > > On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau wrote: > >> I updated the script and pushed the artifacts again. The issue is that >> test.pypi.org does not let you change artifacts once

Re: [VOTE] publish ariatosca 0.2.0

On Thu, Jan 4, 2018 at 11:54 AM Thomas Nadeau 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.

Re: [VOTE] publish ariatosca 0.2.0

My vote is +1. --Tom On Thu, Jan 4, 2018 at 11:35 AM, Maxim Orlov wrote: >1. Validated signature & checksums >2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name >3. Ran RAT check >4. Made a clean install using "pip install ." >5. Ran

Re: [VOTE] publish ariatosca 0.2.0

+1 On Thu, Jan 4, 2018 at 10:54 AM, Thomas Nadeau 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

Re: [VOTE] publish ariatosca 0.2.0

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

Re: [VOTE] publish ariatosca 0.2.0

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 wrote: > The asf-release.sh script we are currently using names them as they are: > > function

Re: [VOTE] publish ariatosca 0.2.0

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} >

Re: [VOTE] publish ariatosca 0.2.0

1. Validated signature & checksums 2. Validated LICENSE, NOTICE, DISCLAIMER, "-incubating" in file name 3. Ran RAT check 4. Made a clean install using "pip install ." 5. Ran tests using "make test" +1 On Thu, Jan 4, 2018 at 5:59 PM Thomas Nadeau wrote: > Aria

Re: [VOTE] publish ariatosca 0.2.0

Thomas, The files are still named "sha" instead of "sha512" John On Thu, Jan 4, 2018 at 10:59 AM Thomas Nadeau 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

[VOTE] publish ariatosca 0.2.0

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

Re: [VOTE] publish ariatosca 0.2.0

I just wanted to update the community on my progress pushing out the new release candidate. I was able to successfully regenerate ALL of the sdist/bdist/doc artifacts and they are currently sitting at apache's svn public area for aria as before. They images are signed, and the key info is there

Re: [VOTE] publish ariatosca 0.2.0

Thanks for catching that. I thought I'd done the signing properly as I generated a new key for myself and used it as part of the process. Ill take a look at this when I am back in the office on Tuesday. In the meantime, my vote is officially changed to -1. Happy New Years! --Tom On Fri, Dec

Re: [VOTE] publish ariatosca 0.2.0

mas Nadeau <tnadeaua...@gmail.com> Sent: Thursday, December 28, 2017 9:15 AM To: dev@ariatosca.incubator.apache.org Subject: Re: [VOTE] publish ariatosca 0.2.0 I forgot to vote myself. I downloaded and unpacked the release, the version number there appeared correct, the API docs are in the p

Re: [VOTE] publish ariatosca 0.2.0

You can also compare to the previously staged release candidates that are still on /dev https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.1-incubating/ We created separate source/sdist/bdist directories to house each. Note that compared to the existing releases, the use of "sha"

Re: [VOTE] publish ariatosca 0.2.0

-1 (binding) * The release needs to be signed, include the signature and sha512 and md5 hashes (see https://dist.apache.org/repos/dist/dev/incubator/airflow/1.9.0rc8/ for an example) * Copyright in NOTICE should just be 2017 rather than range * NOTICE/DISCLAIMER/LICENSE look good * Headers look

Re: [VOTE] publish ariatosca 0.2.0

I forgot to vote myself. I downloaded and unpacked the release, the version number there appeared correct, the API docs are in the package, installs correctly using 'make install-virtual', all tests run with "make test" as well. --Tom On Wed, Dec 27, 2017 at 10:49 AM, Tal Liron

Re: [VOTE] publish ariatosca 0.2.0

+1 - I downloaded and unpacked the release. - Version is correct. - API docs are in "docs/html". - All tests run with "make test". - Installs correctly with "make install-virtual". - Played around with Clearwater example. On Tue, Dec 26, 2017 at 10:11 AM, Thomas Nadeau

[VOTE] publish ariatosca 0.2.0

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. I created a tarball candidate for the 0.2.0 release and placed it in ARIA's /dist/dev folder: