Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.
The following page has been changed by YonikSeeley: http://wiki.apache.org/solr/TaskList ------------------------------------------------------------------------------ * 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?) * verify that NOTICE file is up to snuff - * add a STATUS file (what goes in it?) * 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 @@ -23, +22 @@ (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 - + + Post Approval (Some of these should go in the Release HOWTO) + * website update to point to releases, put a news item on Solr news, (and lucene top-level?) + * update incubation status file + * start new section in CHANGES.txt + * bump default version number in build.xml == Simple Non-Invasive Tasks ==
