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 HossMan: http://wiki.apache.org/solr/TaskList The comment on the change is: removing DONE things, adding some more things i think we should do ------------------------------------------------------------------------------ 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. + * bugs we probably want to wait on... + * https://issues.apache.org/jira/browse/SOLR-78 + * https://issues.apache.org/jira/browse/SOLR-59 + * https://issues.apache.org/jira/browse/SOLR-58 - * [in progress: HowToRelease] 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 - * ant has a built in [http://ant.apache.org/manual/CoreTasks/checksum.html checksum task] that can be used to make our checksome files as part of the "package" target so people dont' have to do it manually as an extra step. - * [DONE] ensure all files have liscence info (Yonik started this, is it finished?) - * [DONE] verify that NOTICE file is up to snuff - * [DONE] the META-INF of all jars/wars we produce need to include our LICENSE and NOTICE files - * get someone smarter then hoss to review our jar/war MANIFEST file + * Get someone smarter then hoss to review our jar/war MANIFEST file... - * figure out way to set the Manifest-Version cleanly regardless of full version number + * is it as valid as it needs to be? * should we inlcude Class-Path info specifying the lib jars, or is it better to leave it out? - * [DONE, removed src build] change src builds to include LICENSE, CHANGES, README, build.xml - * [DONE] verify that all release artifacts unzip/untar into a single directory with the same name as the release (not into the 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. + * all source code in "zip" based 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 + * is there any deprecated code that should be removed? * check in website changes, but don't commit until release approval * do we need release notes, or is changes.txt enough? + * "Build Instructions" should probably be moved out of README.txt and into BUILD.txt + * README.txt needs better verbage targeted at people who unpack a release bundle: ie: mention tutorial/javadocs, mention war, mention wiki for more info 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?)
