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 <smar...@apache.org> 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 <johndam...@apache.org>
> wrote:
>
> > On Sun, Jul 2, 2017 at 9:18 AM Ran Ziv <r...@gigaspaces.com> 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 <johndam...@apache.org>
> > > 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 <r...@gigaspaces.com> 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
> > > > >
> > > >
> > >
> >
>
--
Avia Efrat
SW Engineer
a...@gigaspaces.com | +972546204553
Cloudify | http://getcloudify.org
<http://getcloudify.org?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature>
<https://twitter.com/CloudifySource>
<https://www.linkedin.com/groups/8467478>
<https://github.com/cloudify-cosmo> <https://github.com/cloudify-cosmo>
[image: Azure Webinar]
<http://getcloudify.org/webinars/Azure-plugin-for-cloudify-webinar.html?utm_source=signaturesatori&utm_medium=email&utm_campaign=general_signature>
