Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Ran Ziv]

With 4 binding +1, the vote passes.
I'll send this to the incubator for the official incubator general list for
the official incubator vote now.

Thanks,
Ran

On Tue, Jul 4, 2017 at 7:51 PM, Avia Efrat  wrote:

> 1) Validated signature & checksums
> 2) Validated LICENSE, NOTICE, DISCLAIMER, "incubating" in archive name
> 3) Made a clean install using "pip install ."
> 4) Ran tests using "make test"
>
> +1
>
> On Mon, Jul 3, 2017 at 3:39 PM, Suneel Marthi  wrote:
>
> > +1 binding
> >
> > 1. Verified {sdist, bdist, source} * {sha, md5} hashes and sigs
> > 2. Built project from {source} with "pip install"
> > 3. Ran tests
> > 4. Verified -incubating in artifacts names.
> >
> >
> > On Mon, Jul 3, 2017 at 7:13 AM, John D. Ament 
> > wrote:
> >
> > > On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:
> > >
> > > > Okay. I didn't have anything to go by since as far as I can tell,
> other
> > > > projects don't put their PyPI package candidates on /dist/dev, but to
> > my
> > > > understanding, in the previous voting thread you've requested to have
> > it
> > > on
> > > > there as well.
> > > >
> > >
> > > Nope, the only package I care about is source.  Having the others is an
> > ace
> > > in the hole though, since it's covering the source, binary and sdist
> > > releases needed by pypi (FWIW, there was an effort to spin up an
> internal
> > > pypi service but it's stalled).  When we verify, we can verify the full
> > > package.  Now I know more about pypi dist's to be able to push back
> when
> > > other projects publish bad releases.
> > >
> > > Here's my +1 to release as is.
> > >
> > > I would recommend adding the instructions to the readme at some point,
> > this
> > > block:
> > >
> > > Instructions for installation etc. may be found in the README file
> inside
> > > the tarball.
> > > (Please note that the relevant installation instructions are for
> "source
> > > installation", not "install from PyPI")
> > >
> > >
> > > To use RAT to validate package conformance with ASF standards, please
> use
> > > the ".rat-excludes" file, for example:
> > > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> > >
> > >
> > > In any case, I modified the layout as you'd requested.
> > > >
> > > > Regarding md5 and sha files, note that on PyPI only pgp signatures
> may
> > be
> > > > used. I added them regardless.
> > > >
> > > >
> > > > Thanks,
> > > > Ran
> > > >
> > > >
> > > > On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament  >
> > > > wrote:
> > > >
> > > > > Ran,
> > > > >
> > > > > I would recommend a different directory layout, to make it clear
> that
> > > > these
> > > > > are three different artifacts for the same release.  Most projects
> > > > create a
> > > > > version number below their project name, or just dump all of the
> > files
> > > in
> > > > > the root (makes it easier to remember to clean up afterwards).
> > > > >
> > > > > Starting from
> > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > > 0.1.0-incubating/
> > > > > create
> > > > > "source", "sdist" and "bdist" directories.
> > > > >
> > > > > Put the current contents of this URL in "source" and move the other
> > two
> > > > to
> > > > > the respective locations.  When sending out the vote, you only need
> > to
> > > > > include the root URL.  Or you can just dump everything directly
> into
> > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> > > > >
> > > > > For the contents in sdist and bdist, please include the md5 and sha
> > > > files.
> > > > >
> > > > > John
> > > > >
> > > > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> > > > >
> > > > > > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it
> > in
> > > > > ARIA's
> > > > > > /dist/dev folder:
> > > > > > *
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > > 0.1.0-incubating/
> > > > > > <
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > > 0.1.0-incubating/
> > > > > > >*
> > > > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be
> > found
> > > > in
> > > > > > that folder as well.
> > > > > >
> > > > > >
> > > > > > In addition, I've created packages for (Pythonic-)source & binary
> > > > > > distributions, which would be uploaded to PyPI if the release is
> > > > > approved.
> > > > > > These artifacts may be found here:
> > > > > > Source distribution:
> > > > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 0.1.0-sdist/
> > > > > > Binary distribution:
> > > > > >
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Avia Efrat]

1) Validated signature & checksums
2) Validated LICENSE, NOTICE, DISCLAIMER, "incubating" in archive name
3) Made a clean install using "pip install ."
4) Ran tests using "make test"

+1

On Mon, Jul 3, 2017 at 3:39 PM, Suneel Marthi  wrote:

> +1 binding
>
> 1. Verified {sdist, bdist, source} * {sha, md5} hashes and sigs
> 2. Built project from {source} with "pip install"
> 3. Ran tests
> 4. Verified -incubating in artifacts names.
>
>
> On Mon, Jul 3, 2017 at 7:13 AM, John D. Ament 
> wrote:
>
> > On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:
> >
> > > Okay. I didn't have anything to go by since as far as I can tell, other
> > > projects don't put their PyPI package candidates on /dist/dev, but to
> my
> > > understanding, in the previous voting thread you've requested to have
> it
> > on
> > > there as well.
> > >
> >
> > Nope, the only package I care about is source.  Having the others is an
> ace
> > in the hole though, since it's covering the source, binary and sdist
> > releases needed by pypi (FWIW, there was an effort to spin up an internal
> > pypi service but it's stalled).  When we verify, we can verify the full
> > package.  Now I know more about pypi dist's to be able to push back when
> > other projects publish bad releases.
> >
> > Here's my +1 to release as is.
> >
> > I would recommend adding the instructions to the readme at some point,
> this
> > block:
> >
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.
> > (Please note that the relevant installation instructions are for "source
> > installation", not "install from PyPI")
> >
> >
> > To use RAT to validate package conformance with ASF standards, please use
> > the ".rat-excludes" file, for example:
> > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> >
> >
> > In any case, I modified the layout as you'd requested.
> > >
> > > Regarding md5 and sha files, note that on PyPI only pgp signatures may
> be
> > > used. I added them regardless.
> > >
> > >
> > > Thanks,
> > > Ran
> > >
> > >
> > > On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament 
> > > wrote:
> > >
> > > > Ran,
> > > >
> > > > I would recommend a different directory layout, to make it clear that
> > > these
> > > > are three different artifacts for the same release.  Most projects
> > > create a
> > > > version number below their project name, or just dump all of the
> files
> > in
> > > > the root (makes it easier to remember to clean up afterwards).
> > > >
> > > > Starting from
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > 0.1.0-incubating/
> > > > create
> > > > "source", "sdist" and "bdist" directories.
> > > >
> > > > Put the current contents of this URL in "source" and move the other
> two
> > > to
> > > > the respective locations.  When sending out the vote, you only need
> to
> > > > include the root URL.  Or you can just dump everything directly into
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> > > >
> > > > For the contents in sdist and bdist, please include the md5 and sha
> > > files.
> > > >
> > > > John
> > > >
> > > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> > > >
> > > > > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it
> in
> > > > ARIA's
> > > > > /dist/dev folder:
> > > > > *
> > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > 0.1.0-incubating/
> > > > > <
> > > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > 0.1.0-incubating/
> > > > > >*
> > > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be
> found
> > > in
> > > > > that folder as well.
> > > > >
> > > > >
> > > > > In addition, I've created packages for (Pythonic-)source & binary
> > > > > distributions, which would be uploaded to PyPI if the release is
> > > > approved.
> > > > > These artifacts may be found here:
> > > > > Source distribution:
> > > > >
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-sdist/
> > > > > Binary distribution:
> > > > >
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-bdist/
> > > > >
> > > > >
> > > > >
> > > > > The list of issues Resolved for this release are simply all the
> > issues
> > > > that
> > > > > have been resolved thus far, seeing as this would be the first
> > release
> > > :)
> > > > > Those can be found here:
> > > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > > > > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%
> 20closed)
> > > > >
> > > > >
> > > > > Instructions for installation etc. may be found in the README file
> > > 

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Suneel Marthi]

+1 binding

1. Verified {sdist, bdist, source} * {sha, md5} hashes and sigs
2. Built project from {source} with "pip install"
3. Ran tests
4. Verified -incubating in artifacts names.


On Mon, Jul 3, 2017 at 7:13 AM, John D. Ament  wrote:

> On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:
>
> > Okay. I didn't have anything to go by since as far as I can tell, other
> > projects don't put their PyPI package candidates on /dist/dev, but to my
> > understanding, in the previous voting thread you've requested to have it
> on
> > there as well.
> >
>
> Nope, the only package I care about is source.  Having the others is an ace
> in the hole though, since it's covering the source, binary and sdist
> releases needed by pypi (FWIW, there was an effort to spin up an internal
> pypi service but it's stalled).  When we verify, we can verify the full
> package.  Now I know more about pypi dist's to be able to push back when
> other projects publish bad releases.
>
> Here's my +1 to release as is.
>
> I would recommend adding the instructions to the readme at some point, this
> block:
>
> Instructions for installation etc. may be found in the README file inside
> the tarball.
> (Please note that the relevant installation instructions are for "source
> installation", not "install from PyPI")
>
>
> To use RAT to validate package conformance with ASF standards, please use
> the ".rat-excludes" file, for example:
> java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
>
>
> In any case, I modified the layout as you'd requested.
> >
> > Regarding md5 and sha files, note that on PyPI only pgp signatures may be
> > used. I added them regardless.
> >
> >
> > Thanks,
> > Ran
> >
> >
> > On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament 
> > wrote:
> >
> > > Ran,
> > >
> > > I would recommend a different directory layout, to make it clear that
> > these
> > > are three different artifacts for the same release.  Most projects
> > create a
> > > version number below their project name, or just dump all of the files
> in
> > > the root (makes it easier to remember to clean up afterwards).
> > >
> > > Starting from
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > create
> > > "source", "sdist" and "bdist" directories.
> > >
> > > Put the current contents of this URL in "source" and move the other two
> > to
> > > the respective locations.  When sending out the vote, you only need to
> > > include the root URL.  Or you can just dump everything directly into
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> > >
> > > For the contents in sdist and bdist, please include the md5 and sha
> > files.
> > >
> > > John
> > >
> > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> > >
> > > > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > *
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > <
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > >*
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > In addition, I've created packages for (Pythonic-)source & binary
> > > > distributions, which would be uploaded to PyPI if the release is
> > > approved.
> > > > These artifacts may be found here:
> > > > Source distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> > > > Binary distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
> > > >
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > > > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > > >
> > > >
> > > > Instructions for installation etc. may be found in the README file
> > inside
> > > > the tarball.
> > > > (Please note that the relevant installation instructions are for
> > "source
> > > > installation", not "install from PyPI")
> > > >
> > > >
> > > > To use RAT to validate package conformance with ASF standards, please
> > use
> > > > the ".rat-excludes" file, for example:
> > > > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> > > >
> > > >
> > > >
> > > > The vote will last 72 hours.
> > > >
> > > > Please vote:
> > > >
> > > > [ ] +1: Good to go!
> > > > [ ] 0: I don't care
> > > > [ ] -1: 

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Ran Ziv]

Thanks John.
I took a note of adding the relevant instructions to the readme. I'll make
sure it's added soon.


On Mon, Jul 3, 2017 at 2:13 PM, John D. Ament  wrote:

> On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:
>
> > Okay. I didn't have anything to go by since as far as I can tell, other
> > projects don't put their PyPI package candidates on /dist/dev, but to my
> > understanding, in the previous voting thread you've requested to have it
> on
> > there as well.
> >
>
> Nope, the only package I care about is source.  Having the others is an ace
> in the hole though, since it's covering the source, binary and sdist
> releases needed by pypi (FWIW, there was an effort to spin up an internal
> pypi service but it's stalled).  When we verify, we can verify the full
> package.  Now I know more about pypi dist's to be able to push back when
> other projects publish bad releases.
>
> Here's my +1 to release as is.
>
> I would recommend adding the instructions to the readme at some point, this
> block:
>
> Instructions for installation etc. may be found in the README file inside
> the tarball.
> (Please note that the relevant installation instructions are for "source
> installation", not "install from PyPI")
>
>
> To use RAT to validate package conformance with ASF standards, please use
> the ".rat-excludes" file, for example:
> java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
>
>
> In any case, I modified the layout as you'd requested.
> >
> > Regarding md5 and sha files, note that on PyPI only pgp signatures may be
> > used. I added them regardless.
> >
> >
> > Thanks,
> > Ran
> >
> >
> > On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament 
> > wrote:
> >
> > > Ran,
> > >
> > > I would recommend a different directory layout, to make it clear that
> > these
> > > are three different artifacts for the same release.  Most projects
> > create a
> > > version number below their project name, or just dump all of the files
> in
> > > the root (makes it easier to remember to clean up afterwards).
> > >
> > > Starting from
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > create
> > > "source", "sdist" and "bdist" directories.
> > >
> > > Put the current contents of this URL in "source" and move the other two
> > to
> > > the respective locations.  When sending out the vote, you only need to
> > > include the root URL.  Or you can just dump everything directly into
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> > >
> > > For the contents in sdist and bdist, please include the md5 and sha
> > files.
> > >
> > > John
> > >
> > > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> > >
> > > > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > *
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > <
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > 0.1.0-incubating/
> > > > >*
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > In addition, I've created packages for (Pythonic-)source & binary
> > > > distributions, which would be uploaded to PyPI if the release is
> > > approved.
> > > > These artifacts may be found here:
> > > > Source distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> > > > Binary distribution:
> > > >
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
> > > >
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > > > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > > >
> > > >
> > > > Instructions for installation etc. may be found in the README file
> > inside
> > > > the tarball.
> > > > (Please note that the relevant installation instructions are for
> > "source
> > > > installation", not "install from PyPI")
> > > >
> > > >
> > > > To use RAT to validate package conformance with ASF standards, please
> > use
> > > > the ".rat-excludes" file, for example:
> > > > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> > > >
> > > >
> > > >
> > > > The vote will last 72 hours.
> > > >
> > > > Please vote:
> > > >
> > > > [ ] +1: Good to go!
> > > > [ ] 0: I don't care
> > > > [ ] -1: Don't release this because...
> > > >
> > > >
> > > > Thanks,
> > > > Ran

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[John D. Ament]

On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv  wrote:

> Okay. I didn't have anything to go by since as far as I can tell, other
> projects don't put their PyPI package candidates on /dist/dev, but to my
> understanding, in the previous voting thread you've requested to have it on
> there as well.
>

Nope, the only package I care about is source.  Having the others is an ace
in the hole though, since it's covering the source, binary and sdist
releases needed by pypi (FWIW, there was an effort to spin up an internal
pypi service but it's stalled).  When we verify, we can verify the full
package.  Now I know more about pypi dist's to be able to push back when
other projects publish bad releases.

Here's my +1 to release as is.

I would recommend adding the instructions to the readme at some point, this
block:

Instructions for installation etc. may be found in the README file inside
the tarball.
(Please note that the relevant installation instructions are for "source
installation", not "install from PyPI")


To use RAT to validate package conformance with ASF standards, please use
the ".rat-excludes" file, for example:
java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes


In any case, I modified the layout as you'd requested.
>
> Regarding md5 and sha files, note that on PyPI only pgp signatures may be
> used. I added them regardless.
>
>
> Thanks,
> Ran
>
>
> On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament 
> wrote:
>
> > Ran,
> >
> > I would recommend a different directory layout, to make it clear that
> these
> > are three different artifacts for the same release.  Most projects
> create a
> > version number below their project name, or just dump all of the files in
> > the root (makes it easier to remember to clean up afterwards).
> >
> > Starting from
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 0.1.0-incubating/
> > create
> > "source", "sdist" and "bdist" directories.
> >
> > Put the current contents of this URL in "source" and move the other two
> to
> > the respective locations.  When sending out the vote, you only need to
> > include the root URL.  Or you can just dump everything directly into
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
> >
> > For the contents in sdist and bdist, please include the md5 and sha
> files.
> >
> > John
> >
> > On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
> >
> > > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it in
> > ARIA's
> > > /dist/dev folder:
> > > *
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 0.1.0-incubating/
> > > <
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > 0.1.0-incubating/
> > > >*
> > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> in
> > > that folder as well.
> > >
> > >
> > > In addition, I've created packages for (Pythonic-)source & binary
> > > distributions, which would be uploaded to PyPI if the release is
> > approved.
> > > These artifacts may be found here:
> > > Source distribution:
> > >
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> > > Binary distribution:
> > >
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
> > >
> > >
> > >
> > > The list of issues Resolved for this release are simply all the issues
> > that
> > > have been resolved thus far, seeing as this would be the first release
> :)
> > > Those can be found here:
> > > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > >
> > >
> > > Instructions for installation etc. may be found in the README file
> inside
> > > the tarball.
> > > (Please note that the relevant installation instructions are for
> "source
> > > installation", not "install from PyPI")
> > >
> > >
> > > To use RAT to validate package conformance with ASF standards, please
> use
> > > the ".rat-excludes" file, for example:
> > > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> > >
> > >
> > >
> > > The vote will last 72 hours.
> > >
> > > Please vote:
> > >
> > > [ ] +1: Good to go!
> > > [ ] 0: I don't care
> > > [ ] -1: Don't release this because...
> > >
> > >
> > > Thanks,
> > > Ran
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[Ran Ziv]

Okay. I didn't have anything to go by since as far as I can tell, other
projects don't put their PyPI package candidates on /dist/dev, but to my
understanding, in the previous voting thread you've requested to have it on
there as well.
In any case, I modified the layout as you'd requested.

Regarding md5 and sha files, note that on PyPI only pgp signatures may be
used. I added them regardless.


Thanks,
Ran


On Sun, Jul 2, 2017 at 4:01 PM, John D. Ament  wrote:

> Ran,
>
> I would recommend a different directory layout, to make it clear that these
> are three different artifacts for the same release.  Most projects create a
> version number below their project name, or just dump all of the files in
> the root (makes it easier to remember to clean up afterwards).
>
> Starting from
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-incubating/
> create
> "source", "sdist" and "bdist" directories.
>
> Put the current contents of this URL in "source" and move the other two to
> the respective locations.  When sending out the vote, you only need to
> include the root URL.  Or you can just dump everything directly into
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .
>
> For the contents in sdist and bdist, please include the md5 and sha files.
>
> John
>
> On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:
>
> > This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > *
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-incubating/
> > <
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> 0.1.0-incubating/
> > >*
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > In addition, I've created packages for (Pythonic-)source & binary
> > distributions, which would be uploaded to PyPI if the release is
> approved.
> > These artifacts may be found here:
> > Source distribution:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> > Binary distribution:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
> >
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> > jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > Instructions for installation etc. may be found in the README file inside
> > the tarball.
> > (Please note that the relevant installation instructions are for "source
> > installation", not "install from PyPI")
> >
> >
> > To use RAT to validate package conformance with ASF standards, please use
> > the ".rat-excludes" file, for example:
> > java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
> >
> >
> >
> > The vote will last 72 hours.
> >
> > Please vote:
> >
> > [ ] +1: Good to go!
> > [ ] 0: I don't care
> > [ ] -1: Don't release this because...
> >
> >
> > Thanks,
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0 (#2)

[John D. Ament]

Ran,

I would recommend a different directory layout, to make it clear that these
are three different artifacts for the same release.  Most projects create a
version number below their project name, or just dump all of the files in
the root (makes it easier to remember to clean up afterwards).

Starting from
https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
create
"source", "sdist" and "bdist" directories.

Put the current contents of this URL in "source" and move the other two to
the respective locations.  When sending out the vote, you only need to
include the root URL.  Or you can just dump everything directly into
https://dist.apache.org/repos/dist/dev/incubator/ariatosca/ .

For the contents in sdist and bdist, please include the md5 and sha files.

John

On Sun, Jul 2, 2017 at 8:40 AM Ran Ziv  wrote:

> This is a vote to release Apache AriaTosca (Incubating) 0.1.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.1.0 release and placed it in ARIA's
> /dist/dev folder:
> *
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
> <
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-incubating/
> >*
> The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> that folder as well.
>
>
> In addition, I've created packages for (Pythonic-)source & binary
> distributions, which would be uploaded to PyPI if the release is approved.
> These artifacts may be found here:
> Source distribution:
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-sdist/
> Binary distribution:
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/0.1.0-bdist/
>
>
>
> The list of issues Resolved for this release are simply all the issues that
> have been resolved thus far, seeing as this would be the first release :)
> Those can be found here:
> https://issues.apache.org/jira/browse/ARIA-295?filter=-1;
> jql=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
>
>
> Instructions for installation etc. may be found in the README file inside
> the tarball.
> (Please note that the relevant installation instructions are for "source
> installation", not "install from PyPI")
>
>
> To use RAT to validate package conformance with ASF standards, please use
> the ".rat-excludes" file, for example:
> java -jar ../apache-rat-0.12/apache-rat-0.12.jar . -E .rat-excludes
>
>
>
> The vote will last 72 hours.
>
> Please vote:
>
> [ ] +1: Good to go!
> [ ] 0: I don't care
> [ ] -1: Don't release this because...
>
>
> Thanks,
> Ran
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

Ran,

I previously sent this email [1] on a recommended approach for creating a
source release.  Let me know if that helps.  Since I didn't see any
questions, I had assumed that it made sense.

I would label what you have proposed here as the pypi package, which would
be good for review as well.

I'm traveling the next few days (US holiday) so my responses may be delayed.

John


[1]:
https://lists.apache.org/thread.html/59e8102457c1a1b49c435e714c39780dc728d7f74da2021ddd5c8281@%3Cdev.ariatosca.apache.org%3E

On Thu, Jun 29, 2017 at 12:28 PM Ran Ziv  wrote:

> The vote is cancelled in light of a "-1" vote.
> I'll fix the mentioned issues next week and raise another vote.
>
> I could still use some clarification with regards to what constitutes a
> "source distribution" for this matter.
>
> Thanks,
> Ran
>
> On Thu, Jun 29, 2017 at 7:08 PM, Ran Ziv  wrote:
>
> > Right, I'll need to look more into RAT before creating another RC package
> > then.
> >
> >
> > Re source release - so should it contain exactly everything that's in the
> > repository? This is somewhat different from the Python concept of a
> source
> > distribution.
> > Does it mean the generated doc files can't be there (since they're not in
> > the repo)?
> > Should files like "MANIFEST.IN" which gets compiled when creating a
> > source distribution appear in the source release?
> > Do all the tests and CI-related configurations need to appear in the
> > source release as well?
> >
> >
> > If that's what's needed I can just tar the repository itself I guess.
> > Setting aside the canonical distribution for a moment, would it be ok for
> > the source distribution on PyPI to be of the format that I'm using
> > currently rather than the one you're describing now?
> >
> >
> >
> > On Thu, Jun 29, 2017 at 7:00 PM, John D. Ament 
> > wrote:
> >
> >> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
> >>
> >> > Suneel, re mentioning 72 hours - note that I simply used the
> recommended
> >> > template for these messages from here:
> >> >
> >> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-de
> >> v/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
> >> >
> >> >
> >> I'll note this is an email from 10 years ago, and things have been
> refined
> >> since then.  I plan to rewrite that guide to give better examples.
> Here's
> >> a more up to date example
> >>
> >> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06
> >> fc2e1c03d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
> >>
> >>
> >>
> >> >
> >> >
> >> > John:
> >> > Are you reading this off the README? If so, you'll notice that the
> >> > installation section mentions that when installing ARIA from source,
> the
> >> > command that should be executed is actually "pip install ." when
> you're
> >> > inside the extracted dir.
> >> >
> >> > Regarding your other comments:
> >> >  - DISCLAIMER file - apparently it was dropped from the manifest file
> >> > somehow, i'll add it back.
> >> >  - Is RAT to be used for Python projects as well? I thought it was
> >> > Java-specific and I'm not familiar with similar tools for Python.
> We've
> >> > done what we can to verify every code file has the license header.
> >> >
> >>
> >> RAT is a tool written in java that checks headers in all languages.  We
> >> should have instructions on how to run it here.
> >>
> >>
> >> >  - This is indeed the source release - There are indeed deltas between
> >> this
> >> > and the repo files but that's because some files are unnecessary for
> >> users
> >> > (e.g. docs generating files) while some aren't needed in the repo
> (e.g.
> >> > docs generated files).
> >> >
> >> >
> >> The source release is what's in your repo.  Source releases are for
> >> everyone to consume.
> >>
> >>
> >> >
> >> >
> >> > Ran
> >> >
> >> >
> >> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament  >
> >> > wrote:
> >> >
> >> > > -1.  Found the following issues:
> >> > >
> >> > > - BUILD instructions are INSTALL instructions, and the installation
> >> > doesn't
> >> > > work
> >> > >
> >> > > pip install apache-ariatosca
> >> > >
> >> > >
> >> > > Collecting apache-ariatosca
> >> > >   Could not find a version that satisfies the requirement
> >> > apache-ariatosca
> >> > > (from versions: )
> >> > > No matching distribution found for apache-ariatosca
> >> > >
> >> > > - There is no DISCLAIMER file
> >> > > - No instructions on how to run RAT
> >> > > - I'm not sure this is a source release, many files don't match
> whats
> >> in
> >> > > the repo (files added/missing?)
> >> > >
> >> > > Other things look fine:
> >> > > - contains incubating
> >> > > - files contain headers
> >> > >
> >> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv 
> wrote:
> >> > >
> >> > > > I created a tarball candidate for the 0.1.0 release and placed it
> in
> >> > > ARIA's
> >> > > > /dist/dev folder:
> >> > > > 

Re: [VOTE] publish ariatosca 0.1.0

[Ran Ziv]

The vote is cancelled in light of a "-1" vote.
I'll fix the mentioned issues next week and raise another vote.

I could still use some clarification with regards to what constitutes a
"source distribution" for this matter.

Thanks,
Ran

On Thu, Jun 29, 2017 at 7:08 PM, Ran Ziv  wrote:

> Right, I'll need to look more into RAT before creating another RC package
> then.
>
>
> Re source release - so should it contain exactly everything that's in the
> repository? This is somewhat different from the Python concept of a source
> distribution.
> Does it mean the generated doc files can't be there (since they're not in
> the repo)?
> Should files like "MANIFEST.IN" which gets compiled when creating a
> source distribution appear in the source release?
> Do all the tests and CI-related configurations need to appear in the
> source release as well?
>
>
> If that's what's needed I can just tar the repository itself I guess.
> Setting aside the canonical distribution for a moment, would it be ok for
> the source distribution on PyPI to be of the format that I'm using
> currently rather than the one you're describing now?
>
>
>
> On Thu, Jun 29, 2017 at 7:00 PM, John D. Ament 
> wrote:
>
>> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>>
>> > Suneel, re mentioning 72 hours - note that I simply used the recommended
>> > template for these messages from here:
>> >
>> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-de
>> v/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
>> >
>> >
>> I'll note this is an email from 10 years ago, and things have been refined
>> since then.  I plan to rewrite that guide to give better examples.  Here's
>> a more up to date example
>>
>> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06
>> fc2e1c03d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>>
>>
>>
>> >
>> >
>> > John:
>> > Are you reading this off the README? If so, you'll notice that the
>> > installation section mentions that when installing ARIA from source, the
>> > command that should be executed is actually "pip install ." when you're
>> > inside the extracted dir.
>> >
>> > Regarding your other comments:
>> >  - DISCLAIMER file - apparently it was dropped from the manifest file
>> > somehow, i'll add it back.
>> >  - Is RAT to be used for Python projects as well? I thought it was
>> > Java-specific and I'm not familiar with similar tools for Python. We've
>> > done what we can to verify every code file has the license header.
>> >
>>
>> RAT is a tool written in java that checks headers in all languages.  We
>> should have instructions on how to run it here.
>>
>>
>> >  - This is indeed the source release - There are indeed deltas between
>> this
>> > and the repo files but that's because some files are unnecessary for
>> users
>> > (e.g. docs generating files) while some aren't needed in the repo (e.g.
>> > docs generated files).
>> >
>> >
>> The source release is what's in your repo.  Source releases are for
>> everyone to consume.
>>
>>
>> >
>> >
>> > Ran
>> >
>> >
>> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
>> > wrote:
>> >
>> > > -1.  Found the following issues:
>> > >
>> > > - BUILD instructions are INSTALL instructions, and the installation
>> > doesn't
>> > > work
>> > >
>> > > pip install apache-ariatosca
>> > >
>> > >
>> > > Collecting apache-ariatosca
>> > >   Could not find a version that satisfies the requirement
>> > apache-ariatosca
>> > > (from versions: )
>> > > No matching distribution found for apache-ariatosca
>> > >
>> > > - There is no DISCLAIMER file
>> > > - No instructions on how to run RAT
>> > > - I'm not sure this is a source release, many files don't match whats
>> in
>> > > the repo (files added/missing?)
>> > >
>> > > Other things look fine:
>> > > - contains incubating
>> > > - files contain headers
>> > >
>> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>> > >
>> > > > I created a tarball candidate for the 0.1.0 release and placed it in
>> > > ARIA's
>> > > > /dist/dev folder:
>> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
>> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be
>> found
>> > in
>> > > > that folder as well.
>> > > >
>> > > >
>> > > > The list of issues Resolved for this release are simply all the
>> issues
>> > > that
>> > > > have been resolved thus far, seeing as this would be the first
>> release
>> > :)
>> > > > Those can be found here:
>> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
>> > > > 1=project%3Dariatosca%20and%20status%20in%20(resolved%
>> 2C%20closed)
>> > > >
>> > > >
>> > > > 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.
>> > > >
>> > > >
>> > > > Ran
>> > > >
>> > >
>> >
>>
>
>

Re: [VOTE] publish ariatosca 0.1.0

[Ran Ziv]

Right, I'll need to look more into RAT before creating another RC package
then.


Re source release - so should it contain exactly everything that's in the
repository? This is somewhat different from the Python concept of a source
distribution.
Does it mean the generated doc files can't be there (since they're not in
the repo)?
Should files like "MANIFEST.IN" which gets compiled when creating a source
distribution appear in the source release?
Do all the tests and CI-related configurations need to appear in the source
release as well?


If that's what's needed I can just tar the repository itself I guess.
Setting aside the canonical distribution for a moment, would it be ok for
the source distribution on PyPI to be of the format that I'm using
currently rather than the one you're describing now?



On Thu, Jun 29, 2017 at 7:00 PM, John D. Ament 
wrote:

> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>
> > Suneel, re mentioning 72 hours - note that I simply used the recommended
> > template for these messages from here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-
> dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
> >
> >
> I'll note this is an email from 10 years ago, and things have been refined
> since then.  I plan to rewrite that guide to give better examples.  Here's
> a more up to date example
>
> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c0
> 3d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>
>
>
> >
> >
> > John:
> > Are you reading this off the README? If so, you'll notice that the
> > installation section mentions that when installing ARIA from source, the
> > command that should be executed is actually "pip install ." when you're
> > inside the extracted dir.
> >
> > Regarding your other comments:
> >  - DISCLAIMER file - apparently it was dropped from the manifest file
> > somehow, i'll add it back.
> >  - Is RAT to be used for Python projects as well? I thought it was
> > Java-specific and I'm not familiar with similar tools for Python. We've
> > done what we can to verify every code file has the license header.
> >
>
> RAT is a tool written in java that checks headers in all languages.  We
> should have instructions on how to run it here.
>
>
> >  - This is indeed the source release - There are indeed deltas between
> this
> > and the repo files but that's because some files are unnecessary for
> users
> > (e.g. docs generating files) while some aren't needed in the repo (e.g.
> > docs generated files).
> >
> >
> The source release is what's in your repo.  Source releases are for
> everyone to consume.
>
>
> >
> >
> > Ran
> >
> >
> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
> > wrote:
> >
> > > -1.  Found the following issues:
> > >
> > > - BUILD instructions are INSTALL instructions, and the installation
> > doesn't
> > > work
> > >
> > > pip install apache-ariatosca
> > >
> > >
> > > Collecting apache-ariatosca
> > >   Could not find a version that satisfies the requirement
> > apache-ariatosca
> > > (from versions: )
> > > No matching distribution found for apache-ariatosca
> > >
> > > - There is no DISCLAIMER file
> > > - No instructions on how to run RAT
> > > - I'm not sure this is a source release, many files don't match whats
> in
> > > the repo (files added/missing?)
> > >
> > > Other things look fine:
> > > - contains incubating
> > > - files contain headers
> > >
> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> > >
> > > > I created a tarball candidate for the 0.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > > 1=project%3Dariatosca%20and%20status%20in%20(
> resolved%2C%20closed)
> > > >
> > > >
> > > > 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.
> > > >
> > > >
> > > > Ran
> > > >
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Tal Liron]

This is confusing to me. Python is an interpreted language, so there is no
real difference between source and binary.

In the Python world, you would probably differentiate between "dev"
(everything on the git repo, including tests and development tools) and
"release" (just what's needed to run). I think we treated this as a
"release".

Is there a way to map Python's "dev" and "release" onto ASF's "source" and
"binary"? What do other Python ASF projects do?

On Thu, Jun 29, 2017 at 11:00 AM, John D. Ament 
wrote:

> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>
> > Suneel, re mentioning 72 hours - note that I simply used the recommended
> > template for these messages from here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-
> dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
> >
> >
> I'll note this is an email from 10 years ago, and things have been refined
> since then.  I plan to rewrite that guide to give better examples.  Here's
> a more up to date example
>
> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c0
> 3d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>
>
>
> >
> >
> > John:
> > Are you reading this off the README? If so, you'll notice that the
> > installation section mentions that when installing ARIA from source, the
> > command that should be executed is actually "pip install ." when you're
> > inside the extracted dir.
> >
> > Regarding your other comments:
> >  - DISCLAIMER file - apparently it was dropped from the manifest file
> > somehow, i'll add it back.
> >  - Is RAT to be used for Python projects as well? I thought it was
> > Java-specific and I'm not familiar with similar tools for Python. We've
> > done what we can to verify every code file has the license header.
> >
>
> RAT is a tool written in java that checks headers in all languages.  We
> should have instructions on how to run it here.
>
>
> >  - This is indeed the source release - There are indeed deltas between
> this
> > and the repo files but that's because some files are unnecessary for
> users
> > (e.g. docs generating files) while some aren't needed in the repo (e.g.
> > docs generated files).
> >
> >
> The source release is what's in your repo.  Source releases are for
> everyone to consume.
>
>
> >
> >
> > Ran
> >
> >
> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
> > wrote:
> >
> > > -1.  Found the following issues:
> > >
> > > - BUILD instructions are INSTALL instructions, and the installation
> > doesn't
> > > work
> > >
> > > pip install apache-ariatosca
> > >
> > >
> > > Collecting apache-ariatosca
> > >   Could not find a version that satisfies the requirement
> > apache-ariatosca
> > > (from versions: )
> > > No matching distribution found for apache-ariatosca
> > >
> > > - There is no DISCLAIMER file
> > > - No instructions on how to run RAT
> > > - I'm not sure this is a source release, many files don't match whats
> in
> > > the repo (files added/missing?)
> > >
> > > Other things look fine:
> > > - contains incubating
> > > - files contain headers
> > >
> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> > >
> > > > I created a tarball candidate for the 0.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > > 1=project%3Dariatosca%20and%20status%20in%20(
> resolved%2C%20closed)
> > > >
> > > >
> > > > 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.
> > > >
> > > >
> > > > Ran
> > > >
> > >
> >
>



-- 
Tal Liron, Senior Solutions Architect 
--
M: +1-312-375-8299 http://cloudify.co @cloudifysource

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

You can go with this - this is more recent and i have been enforcing this
on podlings I mentor as well as TLPs I am involved with

https://lists.apache.org/thread.html/f27488e6a5d2355651b0aeb9dd6d82891e20d802ee3c58a0cc4a6533@%3Cdev.streams.apache.org%3E



On Thu, Jun 29, 2017 at 12:00 PM, John D. Ament 
wrote:

> On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:
>
> > Suneel, re mentioning 72 hours - note that I simply used the recommended
> > template for these messages from here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-
> dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
> >
> >
> I'll note this is an email from 10 years ago, and things have been refined
> since then.  I plan to rewrite that guide to give better examples.  Here's
> a more up to date example
>
> https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c0
> 3d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E
>
>
>
> >
> >
> > John:
> > Are you reading this off the README? If so, you'll notice that the
> > installation section mentions that when installing ARIA from source, the
> > command that should be executed is actually "pip install ." when you're
> > inside the extracted dir.
> >
> > Regarding your other comments:
> >  - DISCLAIMER file - apparently it was dropped from the manifest file
> > somehow, i'll add it back.
> >  - Is RAT to be used for Python projects as well? I thought it was
> > Java-specific and I'm not familiar with similar tools for Python. We've
> > done what we can to verify every code file has the license header.
> >
>
> RAT is a tool written in java that checks headers in all languages.  We
> should have instructions on how to run it here.
>
>
> >  - This is indeed the source release - There are indeed deltas between
> this
> > and the repo files but that's because some files are unnecessary for
> users
> > (e.g. docs generating files) while some aren't needed in the repo (e.g.
> > docs generated files).
> >
> >
> The source release is what's in your repo.  Source releases are for
> everyone to consume.
>
>
> >
> >
> > Ran
> >
> >
> > On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
> > wrote:
> >
> > > -1.  Found the following issues:
> > >
> > > - BUILD instructions are INSTALL instructions, and the installation
> > doesn't
> > > work
> > >
> > > pip install apache-ariatosca
> > >
> > >
> > > Collecting apache-ariatosca
> > >   Could not find a version that satisfies the requirement
> > apache-ariatosca
> > > (from versions: )
> > > No matching distribution found for apache-ariatosca
> > >
> > > - There is no DISCLAIMER file
> > > - No instructions on how to run RAT
> > > - I'm not sure this is a source release, many files don't match whats
> in
> > > the repo (files added/missing?)
> > >
> > > Other things look fine:
> > > - contains incubating
> > > - files contain headers
> > >
> > > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> > >
> > > > I created a tarball candidate for the 0.1.0 release and placed it in
> > > ARIA's
> > > > /dist/dev folder:
> > > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> > in
> > > > that folder as well.
> > > >
> > > >
> > > > The list of issues Resolved for this release are simply all the
> issues
> > > that
> > > > have been resolved thus far, seeing as this would be the first
> release
> > :)
> > > > Those can be found here:
> > > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > > 1=project%3Dariatosca%20and%20status%20in%20(
> resolved%2C%20closed)
> > > >
> > > >
> > > > 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.
> > > >
> > > >
> > > > Ran
> > > >
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv  wrote:

> Suneel, re mentioning 72 hours - note that I simply used the recommended
> template for these messages from here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E
>
>
I'll note this is an email from 10 years ago, and things have been refined
since then.  I plan to rewrite that guide to give better examples.  Here's
a more up to date example

https://lists.apache.org/thread.html/9fd77b14753bbde462bea06fc2e1c03d5cf5a89cea2fabd6751d805a@%3Cdev.ponymail.apache.org%3E



>
>
> John:
> Are you reading this off the README? If so, you'll notice that the
> installation section mentions that when installing ARIA from source, the
> command that should be executed is actually "pip install ." when you're
> inside the extracted dir.
>
> Regarding your other comments:
>  - DISCLAIMER file - apparently it was dropped from the manifest file
> somehow, i'll add it back.
>  - Is RAT to be used for Python projects as well? I thought it was
> Java-specific and I'm not familiar with similar tools for Python. We've
> done what we can to verify every code file has the license header.
>

RAT is a tool written in java that checks headers in all languages.  We
should have instructions on how to run it here.


>  - This is indeed the source release - There are indeed deltas between this
> and the repo files but that's because some files are unnecessary for users
> (e.g. docs generating files) while some aren't needed in the repo (e.g.
> docs generated files).
>
>
The source release is what's in your repo.  Source releases are for
everyone to consume.


>
>
> Ran
>
>
> On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
> wrote:
>
> > -1.  Found the following issues:
> >
> > - BUILD instructions are INSTALL instructions, and the installation
> doesn't
> > work
> >
> > pip install apache-ariatosca
> >
> >
> > Collecting apache-ariatosca
> >   Could not find a version that satisfies the requirement
> apache-ariatosca
> > (from versions: )
> > No matching distribution found for apache-ariatosca
> >
> > - There is no DISCLAIMER file
> > - No instructions on how to run RAT
> > - I'm not sure this is a source release, many files don't match whats in
> > the repo (files added/missing?)
> >
> > Other things look fine:
> > - contains incubating
> > - files contain headers
> >
> > On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
> >
> > > I created a tarball candidate for the 0.1.0 release and placed it in
> > ARIA's
> > > /dist/dev folder:
> > > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > > The file is signed (.asc) and its MD5 / SHA512 checksums may be found
> in
> > > that folder as well.
> > >
> > >
> > > The list of issues Resolved for this release are simply all the issues
> > that
> > > have been resolved thus far, seeing as this would be the first release
> :)
> > > Those can be found here:
> > > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> > >
> > >
> > > 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.
> > >
> > >
> > > Ran
> > >
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Ran Ziv]

Suneel, re mentioning 72 hours - note that I simply used the recommended
template for these messages from here:
http://mail-archives.apache.org/mod_mbox/incubator-stdcxx-dev/200601.mbox/%3c43c1c0a0.7040...@roguewave.com%3E



John:
Are you reading this off the README? If so, you'll notice that the
installation section mentions that when installing ARIA from source, the
command that should be executed is actually "pip install ." when you're
inside the extracted dir.

Regarding your other comments:
 - DISCLAIMER file - apparently it was dropped from the manifest file
somehow, i'll add it back.
 - Is RAT to be used for Python projects as well? I thought it was
Java-specific and I'm not familiar with similar tools for Python. We've
done what we can to verify every code file has the license header.
 - This is indeed the source release - There are indeed deltas between this
and the repo files but that's because some files are unnecessary for users
(e.g. docs generating files) while some aren't needed in the repo (e.g.
docs generated files).



Ran


On Thu, Jun 29, 2017 at 6:43 PM, John D. Ament 
wrote:

> -1.  Found the following issues:
>
> - BUILD instructions are INSTALL instructions, and the installation doesn't
> work
>
> pip install apache-ariatosca
>
>
> Collecting apache-ariatosca
>   Could not find a version that satisfies the requirement apache-ariatosca
> (from versions: )
> No matching distribution found for apache-ariatosca
>
> - There is no DISCLAIMER file
> - No instructions on how to run RAT
> - I'm not sure this is a source release, many files don't match whats in
> the repo (files added/missing?)
>
> Other things look fine:
> - contains incubating
> - files contain headers
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > 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.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

-1.  Found the following issues:

- BUILD instructions are INSTALL instructions, and the installation doesn't
work

pip install apache-ariatosca


Collecting apache-ariatosca
  Could not find a version that satisfies the requirement apache-ariatosca
(from versions: )
No matching distribution found for apache-ariatosca

- There is no DISCLAIMER file
- No instructions on how to run RAT
- I'm not sure this is a source release, many files don't match whats in
the repo (files added/missing?)

Other things look fine:
- contains incubating
- files contain headers

On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:

> I created a tarball candidate for the 0.1.0 release and placed it in ARIA's
> /dist/dev folder:
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> that folder as well.
>
>
> The list of issues Resolved for this release are simply all the issues that
> have been resolved thus far, seeing as this would be the first release :)
> Those can be found here:
> https://issues.apache.org/jira/browse/ARIA-295?filter=-
> 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
>
>
> 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.
>
>
> Ran
>

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

... and also please mention that the vote will be 'Open' for 72 hrs - which
means July 2, Sunday for this release candidate - following which we move
to IPMC votes (another 72 hrs) --- and then the release happens if all goes
well.

On Thu, Jun 29, 2017 at 11:37 AM, John D. Ament 
wrote:

> Ran,
>
> Just to be clear, per incubator voting policies this is the dev vote.
> There's a second vote that happens on general@incubator before actually
> moving it to /dist/release
>
> John
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > 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.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Suneel Marthi]

That's correct - u get to move the artifacts to /release only after the
iPMC okays the release artifacts.

On Thu, Jun 29, 2017 at 11:37 AM, John D. Ament 
wrote:

> Ran,
>
> Just to be clear, per incubator voting policies this is the dev vote.
> There's a second vote that happens on general@incubator before actually
> moving it to /dist/release
>
> John
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > 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.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[Ran Ziv]

Yes, I'm aware of this, sorry if I've mis-phrased the purpose of the vote.
Thanks for clearing this up.

On Thu, Jun 29, 2017 at 6:37 PM, John D. Ament 
wrote:

> Ran,
>
> Just to be clear, per incubator voting policies this is the dev vote.
> There's a second vote that happens on general@incubator before actually
> moving it to /dist/release
>
> John
>
> On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:
>
> > I created a tarball candidate for the 0.1.0 release and placed it in
> ARIA's
> > /dist/dev folder:
> > https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> > The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> > that folder as well.
> >
> >
> > The list of issues Resolved for this release are simply all the issues
> that
> > have been resolved thus far, seeing as this would be the first release :)
> > Those can be found here:
> > https://issues.apache.org/jira/browse/ARIA-295?filter=-
> > 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
> >
> >
> > 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.
> >
> >
> > Ran
> >
>

Re: [VOTE] publish ariatosca 0.1.0

[John D. Ament]

Ran,

Just to be clear, per incubator voting policies this is the dev vote.
There's a second vote that happens on general@incubator before actually
moving it to /dist/release

John

On Thu, Jun 29, 2017 at 11:26 AM Ran Ziv  wrote:

> I created a tarball candidate for the 0.1.0 release and placed it in ARIA's
> /dist/dev folder:
> https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
> The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
> that folder as well.
>
>
> The list of issues Resolved for this release are simply all the issues that
> have been resolved thus far, seeing as this would be the first release :)
> Those can be found here:
> https://issues.apache.org/jira/browse/ARIA-295?filter=-
> 1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)
>
>
> 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.
>
>
> Ran
>

[VOTE] publish ariatosca 0.1.0

[Ran Ziv]

I created a tarball candidate for the 0.1.0 release and placed it in ARIA's
/dist/dev folder:
https://dist.apache.org/repos/dist/dev/incubator/ariatosca/
The file is signed (.asc) and its MD5 / SHA512 checksums may be found in
that folder as well.


The list of issues Resolved for this release are simply all the issues that
have been resolved thus far, seeing as this would be the first release :)
Those can be found here:
https://issues.apache.org/jira/browse/ARIA-295?filter=-
1=project%3Dariatosca%20and%20status%20in%20(resolved%2C%20closed)


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.


Ran