Changeset 1956

Show
Ignore:
Timestamp:
11/13/07 23:36:50 (6 months ago)
Author:
karpet
Message:

state of swish

Files:

Legend:

Unmodified
Added
Removed
Modified
Copied
Moved
  • swish_website/src/news.html

    r1875 r1956  
    88 
    99<h1 id="news">News</h1> 
     10 
     11<h3>November 13, 2007 - The State of Swish-e</h3> 
     12 
     13<p> 
     14It's been nearly a year since the last official release. 
     15Lest folks think Swish-e is just gathering dust we thought we would 
     16do a little "state of the project" summary to get folks up to speed on 
     17where we are. 
     18</p> 
     19 
     20<p> 
     21There are currently 4 people regularly contributing to Swish-e. Bill Moseley 
     22is the project leader; David Norris handles all the Windows builds; Jose Ruiz 
     23has been working on the 2.6 branch; and Peter Karman has been working on the 
     243.0 version. 
     25</p> 
     26 
     27<h4>The 2.6 branch</h4> 
     28<p> 
     29As documented on the <a href="/devel/">development page</a>, the 2.6 version 
     30of Swish-e will offer a stable incremental index format and deprecate several features 
     31of the 2.4 branch. You can <a href="http://svn.swish-e.org/swish-e/branches/2.6/"> 
     32check out the 2.6 branch from the Subversion repository</a> to see our progress. 
     33The 2.6 branch uses the Berkeley database for storage. There is currently no timeline 
     34for when an official 2.6 release will happen. 
     35</p> 
     36 
     37<h4>Version 3.0</h4> 
     38<p>Peter has been working on the next major version of Swish-e in fits and starts 
     39for a couple of years. Version 3.0 marks a significant change in the architecture 
     40and will support Unicode and offer a variety of backend storage formats. See the 
     41<a href="/devel/">development page</a> and <a href="http://dev.swish-e.org/wiki/swish3">the 
     42development wiki</a> for more details. 
     43</p> 
     44 
     45<h4>How you can help</h4> 
     46<p> 
     47Version 3.0 is at the point where several API decisions need to be made. Even if you 
     48don't code in C, you can contribute by: 
     49 
     50 <ul> 
     51  <li>reviewing the existing documentation</li> 
     52  <li>testing the existing code to see if it builds correctly (passes tests) 
     53  in your local environment</li> 
     54  <li>contributing tests</li> 
     55 </ul> 
     56  
     57</p> 
     58 
    1059 
    1160<h3>January 22, 2007 - Swish-e Release 2.4.5</h3>