Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [paho-dev] Release Review on April 30th 
Hi Roger,
thanks. As long as we try to stick to the spirit of the rules for non-Java code, I don't expect we will be asked for more. At this point, I'm happy to find out during the review process.
Given that the Python client is available through standard Python installation means (PyPi), I'm not sure that any other installation method or packaging is even needed. Does the PyPi installation have the "incubation" label anywhere? 

Ian

On 04/21/2014 11:42 PM, Roger Light wrote:

Hi Ian,

Thanks for pushing this. I've been getting the Python client up to
scratch recently, there is only one thing outstanding - updated README
as per a bug report.

After some hiccups I have the Python code tests running on our HIPP
successfully. I've also updated the job to generate zip/tar.gz files
suitable for distributing - although I'm not sure whether I can get
the automated tools to generate a name with "incubating" in the file
name. I guess that is a manual task as part of the upload process.
FWIW, the files end up at

https://hudson.eclipse.org/paho/job/paho-python-master/lastSuccessfulBuild/artifact/

The only thing that I'm unsure about is 'Bundle manifests contains a
"Bundle-Vendor" entry set to "Eclipse <project> name>""'. Does this
apply to Python code? I guess not.

Cheers,

Roger


On Thu, Apr 17, 2014 at 1:46 PM, Ian Craggs
<icraggs@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

Hello all,

after some discussion with Wayne, I'm hoping that we can have a Paho 0.9
release review on April 30th.  This means having the review documentation
approved by the PMC by EOB on 24th April.  I'm going to try for that.

The checklist for Release Reviews is here:
https://wiki.eclipse.org/Development_Resources/HOWTO/Release_Reviews#Checklist

This includes:

     - website up to date (Nick, myself and anyone else who cares to help)
     - project plan and metadata up to date (I'm handling that)
     - code and builds in order (expanded below)
     - Every download includes the necessary legal documentation (including a
copy of the project licenses) as required by A Guide to the Legal
Documentation for Eclipse-Based Content.
     - Intellectual Property (IP) Logs in order (me)
     - Distribution channels cleaned up (downloads available
https://wiki.eclipse.org/IT_Infrastructure_Doc#Downloads)

Code and builds are in order (debatable how much applies to non-Java code):

All project code available in eclipse.org VCS
All project source code repositories include a CONTRIBUTING file (done)
At least one milestone build available
Builds hosted on download.eclipse.org
archived builds hosted on archive.eclipse.org
Naming Conventions followed:

Bundle and package names e.g. org.eclipse.<subproject>.<component>[.*]

Version Numbering rules followed
Bundle manifests contains a "Bundle-Vendor" entry set to "Eclipse <project
name>"
Every bundles contains an about.html file as required by A Guide to the
Legal Documentation for Eclipse-Based Content.
Features names and descriptions are captured, are spelled correctly, use
proper grammar, and contain content that is actually useful for the intended
audience
(If in incubation phase) Incubation branding on distributed artefacts
Well-defined retention policy for distributed artefacts (e.g. p2
repositories)

Any help welcome :-)

--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Committer on Paho, Mosquitto


_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev


_______________________________________________
paho-dev mailing list
paho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/paho-dev


--
Ian Craggs
icraggs@xxxxxxxxxx                 IBM United Kingdom
Committer on Paho, Mosquitto

Back to the top