As others have mentioned, the only thing that I'd really like to see is a "bug-fixes-only" release of the 1.x branch that finally brings it up to date with what's in source control. I don't mind if 3.x breaks compatibility and has new features (which it seems it already has) since it is clearly marked as a major release.
If 1.X maintains compatibility with .NET 1.x, then I think that it should maintain compatibility through its entire lifetime, and save dropping the legacy support for the 3.x line, where other things are breaking anyway. Thanks for your dedication to the project! V/R, Nicholas Piasecki From: Michael McCurrey [mailto:mmccur...@gmail.com] Sent: Monday, June 22, 2009 9:29 AM To: user-cs@ibatis.apache.org Subject: Next Release Ok folks, I'd like to plan the next release of iBatis and would like to know "What do you want?" I would like to make a few small releases to bridge the 1.X line & the existing 3.X line due to the number of breaking changes in the 3.X line. Some things I want to do for 'just me' are: 1. Feature match the Java version 2. Fix an annoying list non lazy load bug 3. Rev to my Castle.DynamicProxy2 patch 4. Expose a QueryForDataTable 5. Drop .net 1.X compatibility. 6. Lastly, I would like something ambitious like Orin's Binsor for Castle on the configuration front. -- Michael
