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 ------------------------------------------------------------------------------ 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... + * [DONEish] bugs we probably want to wait on... - * https://issues.apache.org/jira/browse/SOLR-58 + * https://issues.apache.org/jira/browse/SOLR-58 ... (analysis.jsp changes rolled back) * Get someone smarter then hoss to review our jar/war MANIFEST file... * 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? - * 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. * is there any deprecated code that should be removed? - * check in website changes, but don't commit until release approval - * [DONE?] do we need release notes, or is changes.txt enough? * "Build Instructions" should probably be moved out of README.txt and into BUILD.txt - * [DONE?] 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?) * update incubation status file * start new section in CHANGES.txt - * bump default version number in build.xml == Simple Non-Invasive Tasks == This section is for ideas that are relatively straight forward or don't involve major changes to the Solr codebase. People who are eager to "give back" to the Solr community but don't have a lot of familiarity with the Solr code base may be interested in taking on these Tasks... * Create a "Powered By Solr" icon that people can include in their applications if they so choose. + * all source code in "tgz" based releases should be processed by ant's `<fixcrlf>` in case someone prepares a release on a windows box * alternate ways of indexing (it currently requires an HTTP POST of an XML document * be able to load a text file, with variable delimiters (see also [http://issues.apache.org/jira/browse/SOLR-66 SOLR-66]) * point it at a database and give it SQL
