I want to wrap this up in a way that follow precedent. While Groovy was incubating, we voted on their source releases. Their source releases followed incubator policies - including the -incubating in the source release file name. The output from the Groovy releases though (the convenience binaries) all omitted the -incubating suffix. I believe we can follow that same pattern here - the pypi packages (convenience binaries) don't include -incubating, but the source release does.
So I'm staying with my +1, based on this and the explanation Tal gave for the Clearwater samples. John On Thu, Jan 11, 2018 at 7:32 AM Thomas Nadeau <tnad...@apache.org> wrote: > I agree on explicit clarity, especially in the cases of incubation projects > where people might be new to this whole process. > I personally scoured the available documentation yesterday after this came > up and just didn't have the time to chime in, > but I didn't find any specific guidance. > > I agree with Tal here %100. Apache needs to have clear instructions on how > to handle this situation. After this > discussion is clarified, can we ensure someone takes the action to update > the apache docs? I am happy to help > with this if I can. > > --Tom > > > > On Wed, Jan 10, 2018 at 7:52 PM, Tal Liron <t...@cloudify.co> wrote: > > > The line mentioned is not in NOTICE. The line is specifically a comment > in > > a file used to download/install a 3rd party product on the cloud. I truly > > think we are in the clear here. > > > > Re: Python packaging. Apache Airflow is also in incubation and also, like > > AriaTosca, does not have the "-incubating" in its Python package name. > > > > I think it's time we had some clarity here regarding policy and apply it > to > > all projects. AriaTosca would of course comply with whatever is decided. > > > > On Wed, Jan 10, 2018 at 6:44 PM, sebb <seb...@gmail.com> wrote: > > > > > On 10 January 2018 at 17:10, Tal Liron <t...@cloudify.co> wrote: > > > > John, the line is relevant. The service template in question is used > to > > > > install and deploy Clearwater IMS. > > > > > > The NOTICE and LICENSE files are ONLY for files that are actually > > > included in the release archive. > > > > > > > I believe users should know what they are installing. > > > > > > Yes, but not in NOTICE. > > > There should be a prompt to ask the user whether it's OK to install the > > > code. > > > The license can be mentioned at that point. > > > > > > A separate issue is whether the dependency on the GPL code is OK. > > > Will the product run without the download? > > > The general rule is that Cat X dependencies (includes GPL) must be > > > optional. > > > > > > http://www.apache.org/legal/resolved.html#optional > > > > > > > I don't know if we can include a suffix easily, and wonder why need > to > > > > change it now -- it will make it harder for users to upgrade if there > > are > > > > two different package names. > > > > > > > > On Wed, Jan 10, 2018 at 10:57 AM, John D. Ament < > johndam...@apache.org > > > > > > > wrote: > > > > > > > >> On Wed, Jan 10, 2018 at 2:35 AM Tal Liron <t...@cloudify.co> wrote: > > > >> > > > >> > Hi Justin, > > > >> > > > > >> > Project Clearwater is GNU GPLv3, however it is not included in > this > > > >> > distribution. These two files are Apache licensed. The line you > > quote > > > is > > > >> > merely informational. > > > >> > > > > >> > > > >> That line should be removed, as it is not relevant to the release > > > contents > > > >> then. > > > >> > > > >> > > > >> > > > > >> > That tarball and wheel file you are looking at are not Apache > > > >> > distributions, but rather Python packages. Are you sure they need > to > > > have > > > >> > "-incubating" in the name? > > > >> > > > > >> > > > >> As far as I can tell, this is a limitation of the pypi packages, and > > the > > > >> source release includes the proper naming. I see that in the 0.1.1 > > > >> release, this issue didn't come up. Do you know if we can include a > > > suffix > > > >> this like, or would pypi treat this as a part of the version #? > > > >> > > > >> > > > >> > > > > >> > On Wed, Jan 10, 2018 at 1:15 AM, Justin Mclean < > justinmcl...@me.com > > > > > > >> > wrote: > > > >> > > > > >> > > Hi, > > > >> > > > > > >> > > -1 binding as releases don't have incubating in the name. > > > >> > > apache-ariatosca-0.2.0.tar.gz > > > >> > > apache_ariatosca-0.2.0-py2-none-any.whl > > > >> > > > > > >> > > Also can you confirm the license of these two files [1][2] as > > they > > > >> > > contain: > > > >> > > "Project Clearwater is an open-source IMS core, developed by > > > Metaswitch > > > >> > > Networks and released under the GNU GPLv3." > > > >> > > > > > >> > > I checked: > > > >> > > - incubating missing in release name > > > >> > > - signatures and hashes correct > > > >> > > - DISCLAIMER exists > > > >> > > - LICENSE and NOTICE correct > > > >> > > - no unexpected binaries in source release > > > >> > > - all source files have ASF headers > > > >> > > - couldn’t compile from source but probably my environment > > > >> > > > > > >> > > Thanks, > > > >> > > Justin > > > >> > > > > > >> > > 1. apache-ariatosca-0.2.0-incubating.tar/apache- > > > >> > > ariatosca-0.2.0-incubating/examples/clearwater/ > > > >> > > clearwater-live-test-existing.yaml > > > >> > > 2. apache-ariatosca-0.2.0-incubating.tar/apache- > > > >> > > > > > >> > ariatosca-0.2.0-incubating/examples/clearwater/ > > > >> clearwater-single-existing. > > > >> > > yaml > > > >> > > ------------------------------------------------------------ > > > --------- > > > >> > > To unsubscribe, e-mail: > general-unsubscr...@incubator.apache.org > > > >> > > For additional commands, e-mail: general-help@incubator.apache. > > org > > > >> > > > > > >> > > > > > >> > > > > >> > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > >
