Le 4/12/12 9:34 AM, Francesco Chicchiriccò a écrit :
On 11/04/2012 16:59, Emmanuel Lécharny wrote:
Le 4/11/12 4:46 PM, Simone Tripodi a écrit :
On Wed, Apr 11, 2012 at 2:14 PM, Emmanuel
Lécharny<[email protected]> wrote:
I mean, for the best of my knowledge, Syncope were distributed via
Maven artifacts only - it would be appropriate you could include,
in the deploy procedure, the production of sources and compiled
binaries tar/zip archives (assembly plugin is our friend)
Just keep in mind that we, the ASF, distribute sources.
You can provide binaries too, though, but this is not what we check
when we vote a release.
I'd say that this is in charge by every single PMC, i.e. at commons
we do binaries review even with a too restrictive policy - we check
if the artifacts have been produced in the related Tag with exactly
the revision number, a non conformity is enough to justify a -1 :P
No, certainly not ! I just wanted to stres out that the effort should
be focused on the sources for the first release :)
The absence of binaries is also not a reason to reject the first
release.
IMO, in our case a binary release is somehow complicated and maybe not
very useful: in order to provide something that can be effectively
used by someone who downloads it, we should prepare a bundle with at
least a couple of WAR files, full of JARs coming from other Open
Source projects...
If possible, I'd rather provide source files as ZIP / TAR.GZ and keep
Maven artifacts as preferred way to work with Syncope.
You must add your PGP keys into the KEYS file in
/www/www.apache.org/dist/incubator/syncope
ah yes, I forgot it, we should mention somewhere in our release
procedure that has to be copied from
<https://svn.apache.org/repos/asf/incubator/syncope/committers/KEYS>
maybe it - hopefully - increases at every release :)
I don't know if the KEYS file should not be put at the root of the
directory (ie, not under a committers directory) in order to be
easily found.
Ok, let me see if the following procedure is correct:
0. prepare release artifacts (is mvn:release:prepare / mvn
release:perform enough for this?)
1. open a vote process on syncope-dev ML for the release
2. if (1) passes, ask on general@incubator ML for IPMC vote & review
3. if (2) passes
3.1 copy updated KEYS from our SVN to
people.apache.org:/x1/www/www.apache.org/dist/incubator/syncope (who
has enough karma to do this?)
I'll check that.
3.2 prepare some release notes (maybe just adding some introductory
text to the ones automatically generated by JIRA)
The release note should be part of the voted thing. Usually, voters like
to know what's inside the release.
3.3 copy ZIP / TAR.GZ + checksums to the right place (
people.apache.org:/x1/www/www.apache.org/content/dist/incubator/syncope/)
3.4 add / update a download page on our website
3.5 push a notice to [email protected] (how?)
Did I miss something?
Be sure to add the revision number, the links to nexus and any binaries
if you provide some into the vote mail.
Otherwise, I tink it's the proper processus.
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com
