On Mon, Oct 23, 2006 at 10:40:21AM -0300, Jorge Godoy wrote:
> If I were you, I'd adopt the first approach and release 0.8 and then start
> with 0.9.
>
> > I am going to start obsoleting support for Python 2.2. The first step
> > will be to issue a warning. I am not sure if SQLObject 0.8 should issues
> > the warning, or should I wait for SQLObject 0.9?
>
> I'd do that as earlier as possible so that people have time to study. If you
Considering your first advice I read this "release 0.8 now, add the
warning in 0.9, remove support after 0.9."
> can postpone that obsolescense to 1.0 (it looks like it since you're asking if
> it should start with 0.9) then start now, keep it on 0.9 and deprecate Python
> 2.2 in 1.0...
The release after 0.9 not necessary will be numerated as 1.0. It could
be 0.10 ;) It will depend on its quality.
Oleg.
--
Oleg Broytmann http://phd.pp.ru/ [EMAIL PROTECTED]
Programmers don't die, they just GOSUB without RETURN.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
sqlobject-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sqlobject-discuss
