lucene-solr-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "TaskList" by HossMan
Date Thu, 04 Jan 2007 04:07:14 GMT
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

------------------------------------------------------------------------------
  
  Many of the ideas on this page have been discussed on the [http://www.nabble.com/Solr-f14479.html
Solr mailing lists], you should search there for more informaiton.
  
- == 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.
- 
-  * [DONEish] bugs we probably want to wait on...
-    * 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?
-  * is there any deprecated code that should be removed?
-  * "Build Instructions" should probably be moved out of README.txt and into BUILD.txt
- 
- 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
- 
  == 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...
  
+  * "Build Instructions" should probably be moved out of README.txt and into a BUILD.txt
and expanded on.
+  * Get someone smarter then hoss to review our jar/war MANIFEST file...
+    * is it as valid as it can be?
+    * should we include Class-Path info specifying the lib jars, or is it better to leave
it out?
   * 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

Mime
View raw message