Hi Rich,
Jeff is right. The release packages must include at least a LICENSE and
a NOTICE file. A README file would be nice.
Grab a recent OpenCMIS release package, copy the LICENSE file and
modify the NOTICE file.
We also need hashes for release packages and they must be signed.
Florian
Rich,
Should the zip include:
KEYS
LICENSE.txt
NOTICE.txt
README.txt with at least a bare minimum of how-to or a pointer back
to the chemistry web site
I don't know if these are 100% required, but someone in the group
will.
I also think, but am not certain, that you should provide md5 and
sha1 signatures for each of the artifacts in addition to the asc sigs
you've already provided.
Jeff
On Nov 18, 2013, at 6:18 AM, Richard McKnight
<[email protected]> wrote:
Hi,
I am preparing for the first official release of the CMIS PHP
client. Please find the following items below.
https://svn.apache.org/repos/asf/chemistry/phpclient/tags/0.2.0-RC1/
-- the source for the release candidate
https://people.apache.org/~richardm/chemistry/phpclient/0.2.0-RC1/
-- the artifacts….
I decided to just go with a .tgz and a .zip -- Doing a PHAR file
seemed a bit complex..
The vote is open for 72 hours and passes if a majority of at least
three +1 Chemistry PMC votes are cast.
Please cast your votes!
[ ] +1 Release this package as Apache Chemistry PHP CMIS client
0.2.0
[ ] -1 Do not release this package because...
My vote is +1. (I can vote right?)….
This is my first release so I would welcome any feedback on anything
that I may be missing in the process.
Thanks,
Rich
Richard McKnight | Principal Technical Consultant - Americas,
o +1 512 692 6179 | m +1 908 247 0756 | skype rmknightstar
Alfresco Professional Services | LinkedIn Profile
Thinking about Alfresco or new to enterprise content management? Get
up to speed with the basics.
