Re: [VOTE] publish ariatosca 0.2.0

2018-01-08 Thread Thomas Nadeau
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  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.
>
> --Tom
>
>
>
> On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament 
> 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 
>> 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 
>> > wrote:
>> >
>> > > 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 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=ARIA=planning
>> ue=ARIA-394
>> > > > > > > rapidView=150=ARIA=planning=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
>> > > >
>> > >
>> >
>>
>
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-05 Thread Suneel Marthi
+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 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 
> > 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 
> > > 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 
> > > > 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=ARIA=planning&
> > > selectedIssue=ARIA-394
> > > > > >  > > > > rapidView=150=ARIA=planning=
> 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
> > > > > >
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-05 Thread Thomas Nadeau


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

Correct. All of that stuff is a second step for me that I’ll get to but 
only
after the release goes out.

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

Agreed. I’ve kept a log of all the stuff I’ve had to do and will be 
updating
the wiki, asft-release.sh, etc… after we get the greenlight that what I’ve
done is all cool.

Have a great weekend!

—Tom


> 
> 
>> --Tom
>> 
>> 
>> 
>> On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament 
>> 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 
>>> 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 
 wrote:
 
> 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 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=ARIA=planning&
>>> selectedIssue=ARIA-394
>>  rapidView=150=ARIA=planning=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
>> 
> 
 
>>> 
>> 



Re: [VOTE] publish ariatosca 0.2.0

2018-01-05 Thread John D. Ament
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.
> 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 
> 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 
> > 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 
> > > wrote:
> > >
> > > > 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 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=ARIA=planning&
> > selectedIssue=ARIA-394
> > > > >  > > > rapidView=150=ARIA=planning=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
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Thomas Nadeau
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 tests using "make test"
>
> +1
>
> On Thu, Jan 4, 2018 at 5:59 PM 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 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=ARIA=planning=ARIA-394
> >  rapidView=150=ARIA=planning=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
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Tal Liron
+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 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.
>
> --Tom
>
>
>
> On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament 
> 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 
> > 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 
> > > wrote:
> > >
> > > > 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 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=ARIA=planning&
> > selectedIssue=ARIA-394
> > > > >  > > > rapidView=150=ARIA=planning=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
> > > > >
> > > >
> > >
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Thomas Nadeau
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.

--Tom



On Thu, Jan 4, 2018 at 11:38 AM, John D. Ament 
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 
> 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 
> > wrote:
> >
> > > 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 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=ARIA=planning&
> selectedIssue=ARIA-394
> > > >  > > rapidView=150=ARIA=planning=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
> > > >
> > >
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread John D. Ament
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 _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 
> wrote:
>
> > 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 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=ARIA=planning=ARIA-394
> > >  > rapidView=150=ARIA=planning=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
> > >
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Thomas Nadeau
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 
wrote:

> 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 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=ARIA=planning=ARIA-394
> >  rapidView=150=ARIA=planning=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
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Maxim Orlov
   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 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=ARIA=planning=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
>


Re: [VOTE] publish ariatosca 0.2.0

2018-01-04 Thread John D. Ament
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 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=ARIA=planning=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
>


[VOTE] publish ariatosca 0.2.0

2018-01-04 Thread Thomas Nadeau
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/
*

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=ARIA=planning=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


Re: [VOTE] publish ariatosca 0.2.0

2018-01-02 Thread Thomas Nadeau
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 as well.

I am missing only 1 thing now: pushing the candidate artifacts to pypi's
"testing" staging area with twine. Im blocked now
because one needs the login credentials for pypi.org. Does anyone know the
credentials for pypi.org?  We need the
ariatosca account's information. I don't believe I can just create a
personal account and push there.  I cannot push the
0.2.0 candidates there until I get the info.  BTW please unicast me on
slack or email with the credentials - please DO NOT
reply-all here.  8)

Cheers,

--Tom




On Fri, Dec 29, 2017 at 8:31 PM, Tal Liron  wrote:

> Thanks, Jakob. I am changing my vote to: -1.
>
> On Fri, Dec 29, 2017 at 4:42 PM, Jakob Homan  wrote:
>
> > -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 good
> > * Didn't see any included libraries that would require inclusion in
> LICENSE
> >
> > Also, just to clarify on the voting procedure.  The entire community
> > is encouraged to vote on releases, although on the Podling Project
> > Management Committee (PPMC) has binding votes.  Testing and voting on
> > releases is an excellent way to contribute to project.
> >
> > -Jakob
> >
> > On 28 December 2017 at 07:15, Thomas Nadeau 
> wrote:
> > > 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  wrote:
> > >
> > >> +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 <
> tnadeaua...@gmail.com>
> > >> 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.
> > >> >
> > >> > I created a tarball candidate for the 0.2.0 release and placed it in
> > >> ARIA's
> > >> >  /dist/dev folder:
> > >> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > >> > 0.2.0-candidate/
> > >> > The list of issues Resolved 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=ARIA=planning=ARIA-394
> > >> > Instructions for installation etc. may be found in the README file
> > inside
> > >> > the tarball.  Please vote to publish this tarball on ARIA's
> > /dist/release
> > >> > folder.  The voting for this as I understand it, 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,
> > Tuesday,
> > >> > December 26, 2017 and be completed on  12PM EST on Friday, December
> > 29,
> > >> > 2017.
> > >> >
> > >> > Thanks,
> > >> >
> > >> > --Tom
> > >> >
> > >>
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-30 Thread Thomas Nadeau
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 29, 2017 at 5:42 PM, Jakob Homan  wrote:

> -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 good
> * Didn't see any included libraries that would require inclusion in LICENSE
>
> Also, just to clarify on the voting procedure.  The entire community
> is encouraged to vote on releases, although on the Podling Project
> Management Committee (PPMC) has binding votes.  Testing and voting on
> releases is an excellent way to contribute to project.
>
> -Jakob
>
> On 28 December 2017 at 07:15, Thomas Nadeau  wrote:
> > 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  wrote:
> >
> >> +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 
> >> 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.
> >> >
> >> > I created a tarball candidate for the 0.2.0 release and placed it in
> >> ARIA's
> >> >  /dist/dev folder:
> >> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> >> > 0.2.0-candidate/
> >> > The list of issues Resolved 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=ARIA=planning=ARIA-394
> >> > Instructions for installation etc. may be found in the README file
> inside
> >> > the tarball.  Please vote to publish this tarball on ARIA's
> /dist/release
> >> > folder.  The voting for this as I understand it, 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,
> Tuesday,
> >> > December 26, 2017 and be completed on  12PM EST on Friday, December
> 29,
> >> > 2017.
> >> >
> >> > Thanks,
> >> >
> >> > --Tom
> >> >
> >>
>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-29 Thread Vishwanath Jayaraman
+1


Used a docker image using Dockerfile 
(https://github.com/vishwanathj/dockerrepo/blob/master/aria020/ubuntu1604/Dockerfile)
 to download and unpack the release on Ubuntu 16.04


I checked the version and ran the the "make test"


Vish



From: Thomas 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 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 <t...@cloudify.co> wrote:

> +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 <tnadeaua...@gmail.com>
> 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.
> >
> > I created a tarball candidate for the 0.2.0 release and placed it in
> ARIA's
> >  /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
dist - Revision 23752: 
/dev/incubator/ariatosca<https://dist.apache.org/repos/dist/dev/incubator/ariatosca/>
dist.apache.org
dist - Revision 23752: /dev/incubator/ariatosca.. 0.1.0-incubating/ 
0.1.1-incubating/ KEYS



> > 0.2.0-candidate/
> > The list of issues Resolved 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=ARIA=planning=ARIA-394
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.  Please vote to publish this tarball on ARIA's /dist/release
> > folder.  The voting for this as I understand it, 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, Tuesday,
> > December 26, 2017 and be completed on  12PM EST on Friday, December 29,
> > 2017.
> >
> > Thanks,
> >
> > --Tom
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-29 Thread John D. Ament
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" extension is now
discouraged to projects, instead the file extension should indicate the
correct sha length (256/512/etc)

The previously documented release process can be seen at
https://cwiki.apache.org/confluence/display/ARIATOSCA/Release+Process

I do see that the release script previously created is still around, and
seems to do the right things (minus the note above about the sha file):
https://github.com/apache/incubator-ariatosca/blob/master/release/asf-release.sh

Perhaps reroll by using this tool?

John

On Fri, Dec 29, 2017 at 5:43 PM Jakob Homan  wrote:

> -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 good
> * Didn't see any included libraries that would require inclusion in LICENSE
>
> Also, just to clarify on the voting procedure.  The entire community
> is encouraged to vote on releases, although on the Podling Project
> Management Committee (PPMC) has binding votes.  Testing and voting on
> releases is an excellent way to contribute to project.
>
> -Jakob
>
> On 28 December 2017 at 07:15, Thomas Nadeau  wrote:
> > 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  wrote:
> >
> >> +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 
> >> 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.
> >> >
> >> > I created a tarball candidate for the 0.2.0 release and placed it in
> >> ARIA's
> >> >  /dist/dev folder:
> >> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> >> > 0.2.0-candidate/
> >> > The list of issues Resolved 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=ARIA=planning=ARIA-394
> >> > Instructions for installation etc. may be found in the README file
> inside
> >> > the tarball.  Please vote to publish this tarball on ARIA's
> /dist/release
> >> > folder.  The voting for this as I understand it, 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,
> Tuesday,
> >> > December 26, 2017 and be completed on  12PM EST on Friday, December
> 29,
> >> > 2017.
> >> >
> >> > Thanks,
> >> >
> >> > --Tom
> >> >
> >>
>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-29 Thread Jakob Homan
-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 good
* Didn't see any included libraries that would require inclusion in LICENSE

Also, just to clarify on the voting procedure.  The entire community
is encouraged to vote on releases, although on the Podling Project
Management Committee (PPMC) has binding votes.  Testing and voting on
releases is an excellent way to contribute to project.

-Jakob

On 28 December 2017 at 07:15, Thomas Nadeau  wrote:
> 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  wrote:
>
>> +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 
>> 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.
>> >
>> > I created a tarball candidate for the 0.2.0 release and placed it in
>> ARIA's
>> >  /dist/dev folder:
>> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
>> > 0.2.0-candidate/
>> > The list of issues Resolved 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=ARIA=planning=ARIA-394
>> > Instructions for installation etc. may be found in the README file inside
>> > the tarball.  Please vote to publish this tarball on ARIA's /dist/release
>> > folder.  The voting for this as I understand it, 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, Tuesday,
>> > December 26, 2017 and be completed on  12PM EST on Friday, December 29,
>> > 2017.
>> >
>> > Thanks,
>> >
>> > --Tom
>> >
>>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-28 Thread Thomas Nadeau
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  wrote:

> +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 
> 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.
> >
> > I created a tarball candidate for the 0.2.0 release and placed it in
> ARIA's
> >  /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 0.2.0-candidate/
> > The list of issues Resolved 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=ARIA=planning=ARIA-394
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.  Please vote to publish this tarball on ARIA's /dist/release
> > folder.  The voting for this as I understand it, 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, Tuesday,
> > December 26, 2017 and be completed on  12PM EST on Friday, December 29,
> > 2017.
> >
> > Thanks,
> >
> > --Tom
> >
>


Re: [VOTE] publish ariatosca 0.2.0

2017-12-27 Thread Tal Liron
+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 
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.
>
> I created a tarball candidate for the 0.2.0 release and placed it in ARIA's
>  /dist/dev folder:
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.2.0-candidate/
> The list of issues Resolved 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=ARIA=planning=ARIA-394
> Instructions for installation etc. may be found in the README file inside
> the tarball.  Please vote to publish this tarball on ARIA's /dist/release
> folder.  The voting for this as I understand it, 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, Tuesday,
> December 26, 2017 and be completed on  12PM EST on Friday, December 29,
> 2017.
>
> Thanks,
>
> --Tom
>


[VOTE] publish ariatosca 0.2.0

2017-12-26 Thread Thomas Nadeau
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:
https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.2.0-candidate/
The list of issues Resolved 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=ARIA=planning=ARIA-394
Instructions for installation etc. may be found in the README file inside
the tarball.  Please vote to publish this tarball on ARIA's /dist/release
folder.  The voting for this as I understand it, 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, Tuesday,
December 26, 2017 and be completed on  12PM EST on Friday, December 29,
2017.

Thanks,

--Tom