On 11/28/06, Apache Wiki <[EMAIL PROTECTED]> wrote:
+ == Things That Need Done To Have An Initial Release == + + This is a "short term" list of things people think of that need to be done before we can have our first official release. [http://incubator.apache.org/guides/releasemanagement.html This guide] should also be consulted for more info. + + * write a Release HOWTO wiki documenting all of hte steps to making a release ...
ideally this should mainly be stuff about validating the release, signing it, and pushing it out to the mirrors ... any mindless command execution that winds up being listed in the HOWTO should be added to the build.xml
+ * ensure all files have liscence info (Yonik started this, is it finished?)
Getting there... I still need to investigate to see what Jetty requires us to add to our NOTICE.
+ * verify that NOTICE file is up to snuff + * add a STATUS file (what goes in it?)
Where's the link that you saw this STATUS file?
+ * the META-INF of all jars/wars we produce need to include our LICENSE and NOTICE files + * make jar MANIFEST files "standards compliant" (what exactly does that mean? + * change src builds to include LICENSE, CHANGES, README, build.xml
src.zip isn't packaged as a release. Here is what I'm currently "testing": $ cat disttest DIR=disttestdir rm -rf $DIR svn checkout http://svn.apache.org/repos/asf/incubator/solr/trunk $DIR cd $DIR ant package -Dversion=1.0-incubating rm -rf apache-solr-1.0-incubating tar xvzf $DIR/dist/apache-solr-1.0-incubating.tgz
+ * verify that all release artifacts unzip/untar into a single directory with the same name as the release + (not inot hte current working directory) + * all source code in "zip" based src releases should be processed by ant's `<fixcrlf>` for windows users ... scripts probably shouldn't get this treatment since they are only usefull to windows users running cygwin and cygwin doesn't like windows line endings. + * remove deprecated code
-Yonik
