Guys, Let's try this again...
Apache is about Open Source. There is a huge emphasis on the "Source" part, to the degree that there are times when some projects don't even release binaries at all, only the sources. So the "Released Artifact" are the sources and the build system (incl instructions) required to produce a useful binary. The binary output is NOT included in the primary release artifact, but is "generated" by it. So; SVN --(packaging)--> Source Release --(build+package)--> Binary Release So, on these grounds, I am not going to recommend the PMC to approve the release. Here is what is needed; 1. Create a target in the Ant build, that zips/tars up the SVN sources, not including the .svn directories. Sources in this instance means everything that is needed to build Pivot, except for "System Requirements" (listed in the README/BUILD). Ant and JDK is typical System Requirements, as are any external jar files that are only required for the build, BUT some people (like myself) prefer to have them part of the source dist. 2. That zip/tar IS your primary release artifact; apache-pivot-1.1-incubating.tar.gz 3. Using that zip/tar, execute another Ant target (for instance 'install') which compiles, jars and sticks everything into a 'generated/apache-pivot-1.1-incubating' directory. 4. The same target could also create a zip/tar of the 'generated/apache-pivot-1.1-incubating', and that IS your supplementary binary release. 5. Ask a couple of community members to sanity check the binary release, and make sure it is useful. 6. Let people worry about Maven distro separately. And perhaps later migrate to Maven build system, if you find Maven support important and want to simplify such process. 7. Finally, the release artifacts needs checksums and signatures. The PGP signature should be uploaded to at least one or two public PGP servers, such as pgp.mit.edu, and eventually be cross-signed in person with other people in Apache (for instance at an ApacheCon event). That creates the Apache Web of Trust. This may seem like a lot of work for nothing, but there are some people who takes this aspect of Apache very, very seriously. See http://www.apache.org/dev/release-signing.html for more details. Apache level FAQ on releases are here; http://www.apache.org/dev/release.html Note that additional requirements are imposed by the Incubator, and is found embedded in http://incubator.apache.org/guides/releasemanagement.html. Hope this helps. Cheers -- Niclas Hedhman, Software Developer http://www.qi4j.org - New Energy for Java I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
