Re: Closing out 2.7 beta 4
Jim Baker <[email protected]>
| Newsgroups | gmane.comp.lang.jython.devel |
|---|---|
| Message-ID | <CAOhO=aNOzgCZ1hX+LJ7MQ9zFEi+xRUHb4a684JKc_=AEHpcYog@mail.gmail.com> |
On Mon, Oct 13, 2014 at 1:37 PM, [email protected] < [email protected]> wrote: > Jim: wow, this is a great writeup! Thanks, I really appreciate this! > I agree with almost everything > here, including going to a 6 month schedule for the 2.7.x series once > a 2.7.0 is reached. > I'm good with every 6 months, or annually, depending on what we find works well. The important thing we can agree on is to start doing regular time-based releases. I forgot to mention one other thing: we should leave open the possibility of breaking Java API changes. We intentionally did not do that in 2.5, and I think in the end that policy was too strict: in a number of cases, we could not fix resource leaks and related problems. We should minimize such changes, however. > > The one spot I'm not sure about is the drop in replacement of zxJDBC > with JyJDBC. I'm inclined to leave zxJDBC in (deprecated) and have > users explicitly use JyJDBC in their apps, with a warning that zxJDBC > is basically unmaintained at this point. I'm worried that there are > many unknown corner cases where they are not really drop in > replacements, and that we'll end up with a flood of bug reports for > broken code that worked before. I think it would be easier allow a > slow transition for those that need it (knowing that zxJDBC will be > gone in 3.x). > I'm glad you raised this potential problem. On the one hand, we have a lot of bugs/missing features in zxJDBC that none of us feel comfortable tackling because of the lack of test coverage. On the other, this scenario could really derail the 2.7.0 rollout. This is especially true when we consider that zxJDBC has proven to be stable for what it does, given the underlying JDBC stability. And JyJDBC is easily installable by people who needs its features. So deprecating zxJDBC for now sounds like the best path. If we get more experience with these possible problems, we can replace in a future 2.7.x, where x > 0. And we will certainly remove zxJDBC in favor of JyJDBC for 3.5. Thanks, this is why we triage! :) - Jim ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ Jython-dev mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jython-dev