Oleg Broytmann <[EMAIL PROTECTED]> writes: > Hello! I am going to start working on a number of rather large issues, and > few of them are really big changes. I will describe them in greater details > below, but now I want to ask a question: how should I handle the changes? > I can release SQLObject 0.8 from the trunk and start to work on these > large issues; then they will be in the SQLObject 0.9. Or I can continue to > work in the trunk now, so the changes will be in SQLObject 0.8, but the > release will be much later. What is better for the SQLObject users?
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 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... -- Jorge Godoy <[EMAIL PROTECTED]> ------------------------------------------------------------------------- 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
