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 <johndam...@apache.org> wrote: > On Thu, Jun 29, 2017 at 11:53 AM Ran Ziv <r...@gigaspaces.com> 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 <johndam...@apache.org> > > 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 <r...@gigaspaces.com> 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&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 vote to publish this tarball on ARIA's /dist/release folder. > > > > > > > > > > > > Ran > > > > > > > > > > -- Tal Liron, Senior Solutions Architect <http://cloudify.co> ------------------------------ M: +1-312-375-8299 http://cloudify.co @cloudifysource <https://twitter.com/CloudifySource> <https://www.linkedin.com/company-beta/17918192/> <https://github.com/cloudify-cosmo> <https://www.youtube.com/cloudifysource>
