Roadmap to 2.0 (up to the last microsecond)

Hello!

   A big part of my frustration was that I created a backward
incompatible version and didn't know where and how to move further from
there.
   Now I see it was stupid. Such a major incompatibility should only be
introduced in version 2.0. Gradually if possible.

   So my plan currently is:

-- Completely remove support for microseconds from branch 1.6; deprecate
   support for Python 2.5 (format ".%f" for microseconds is only
   supported in 2.6+).
-- Create branch 1.7; drop support for Python 2.5, minimally supported
   version will be 2.6; restore the code to read microseconds (from
   databases created with SO 2.0) but not write them.
-- Create branch 2.0 with full support for microseconds.

PS. I beg your pardon. I said something about microseconds in the
subject but that was only a pun. I cannot promise months, even less
concrete dates. I'm sorry.

Oleg.
-- 
     Oleg Broytman            http://phdru.name/            [email protected]
           Programmers don't die, they just GOSUB without RETURN.

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs