RFC: Timeline/Roadmap

All,
  There's been a great deal of discussion of various database backends
on the list lately, with patches, ideas, and designs flying around all
willy-nilly.

  Thats great - a database backend is what current really needs down the
road. However, we still need to get a 1.0 out the door, so there's some
work yet to be done.

0.9.4 - current stable release
        I have a newer delete patch 
        I have a timestamp the logs patch
        
0.9.5  will hopefully ship today (might be late) with those two.

For 1.0, we also need:
    a) reorg the logging a little.
       I want level 0 to be startup, shutdown, and all error messages.
       I want the new level 1 to add a one line/query (same as apache)
    b) We need to add "obsoletes" to the database. A user/admin has 
       presented a clear case for why we need them (even for 1.0). Even
       if we don't use them correctly in 1.0, if they are in the     
       database, theoretically all 1.0.x versions could use the same 
       database. (Still the old shelve system)
    c) bug report of solveDep() not doing the right thing on multiple 
       unsolved - I think I know what to do, I still need to tweak 
       and test.
    d) The "framework" that comes in python, that Current is based on, 
       includes threading/multi-process "mixins" that _should_ be fairly
       simple to turn on and then test. This feature is NOT required 
       for 1.0, but I want to play with it here so if we can get a 
       threaded/multi-process 1.0, we can.
    e) John? Anybody? Bueller?

All that should be 1.0.rc1 - ship that (end of this week? man that would
be nice) get all you nice people to test it, and then if no problems
crop up, ship 1.0. (Still shelves, still anon only)

Then the fun starts - 

1.0.x stable, production releases, new featurlets that don't _change_ 
      things, and bug fixes.

1.1.x The great database integration, part 1.   
      Right now, this will be based on toby's patch
      The goals here would be to get the big 13 (13 rules, soon on the 
      website).

1.2.x stable production releases, based on the 1.1.x 

1.3.x The great I/O integration.
      People don't seem to realise it, but Current in the 0.9 releases 
      is very much single threaded. 1.3 should be where we move to 
      apache/mod_python for speed/scalability. (I think, and others 
      confirm, that apache/mod_python will scale much better than 
      even a multi-threaded/multi-process all python daemon.)

2.x   To Infinity - And Beyond!
      (I have no idea)

Toby, 
   I will do my best to not let 0.9.5 -> 1.0 change your patch, but for
a week or two you're either going to have to update your patch all the
time, or what for 1.0, and then update it.  1.1 will be 1.0 + your
patch.


-- 
Hunter Matthews                          Unix / Network Administrator
Office: BioScience 145/244               Duke Univ. Biology Department
Key: F0F88438 / FFB5 34C0 B350 99A4 BB02  9779 A5DB 8B09 F0F8 8438
Never take candy from strangers. Especially on the internet.