ibatis-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Clinton Begin" <clinton.be...@gmail.com>
Subject Re: Multiple Result Set Support complete, 2.2.0 will fly within a week
Date Tue, 15 Aug 2006 03:17:01 GMT
That's a great idea.  Let's do an infomercial with Chuck Norris too.

Cheers,  :-)
Clinton

On 8/14/06, Larry Meadors <lmeadors@apache.org> wrote:
>
> ..or take a cue from commercial software vendors, and release them all
> today (available for pre-order, that is).
>
> Larry
>
>
>
> On 8/14/06, Jeff Butler <jeffgbutler@gmail.com> wrote:
> >
> > LOL - we should do MDD - then we could just draw a pretty picture and
> > there would be NO development time. :)
> >
> > Jeff
> >
> >
> > On 8/14/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > >
> > > >> don't make any grand pronouncements about 2.2.0
> > >
> > > Good call Jeff.  Sorry for sounding extreme.  We'll definitely be
> > > supporting 2.2.0 for a long time, including new features that make too
> > > much sense to ignore.
> > >
> > > At the end of the day, we'll always do what makes sense.  Our
> > > investors don't mind.  ;-)
> > >
> > > >> we don't have any idea how long it will take to develop [iBATIS 3.0
> > > ]
> > >
> > > I do!  According to the latest hype:
> > >
> > >   * iBATIS 3.0 will take 4 weeks to write.
> > >   * iBATIS.NET <http://ibatis.net/> 3.0 will take 2 weeks to write.
> > >   * RBatis 3.0 will take 3.5 hours.
> > >
> > > Cheers,  ;-)
> > >
> > > Clinton
> > >
> > >
> > > On 8/14/06, Jeff Butler <jeffgbutler@gmail.com > wrote:
> > > >
> > > >  I agree that no new JDK/JDBC features should be put into iBATIS 2.x.
> > > > But I'd suggest that we don't make any grand pronouncements about
> > > > 2.2.0 being the last release except for maintenance.  It's hard to
> > > > predict what the future holds and we have no idea when iBATIS 3.0might
be released.  There have been no substantive discussions about iBATIS
> > > > 3.0 anywhere and we don't have any idea how long it will take to
> > > > develop such a thing.
> > > >
> > > > So I'd just say that we plan to keep iBATIS 2.x using JDK 1.4.  I
> > > > can't see any value to declaring some kind of extended maintenance mode
for
> > > > iBATIS 2.x - let's wait to do that until iBATIS 3.0 is somewhat
> > > > close to a real product.
> > > >
> > > > Jeff Butler
> > > >
> > > >
> > > > On 8/13/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > > > >
> > > > > Hi all,
> > > > >
> > > > > The good news is that I'm on vacation.  The bad news is that I
> > > > > spent the last 6 hours watching the first two extended edition Lord
of the
> > > > > Rings movies while implementing the Multiple ResultSet support.
> > > > >
> > > > > That was the last "required" feature for 2.2.0 to go out, so I'm
> > > > > thinking it should be no more than a week before we see it deployed.
 There
> > > > > may be a few more things to go, but certainly not of that size.
> > > > >
> > > > > Speaking of major features, I think that must be darn near the
> > > > > entire JDBC API we've wrapped with iBATIS, and iBATIS 2.0 is
> > > > > showing its age.  It's been in production for almost 2.5 years,
> > > > > which is great life to get out of any software.
> > > > >
> > > > > That said, with 2.2.0 out, I fully expect the next major version
> > > > > to be 3.0.  I recommend 2.0 enter an extended maintenance mode,
> > > > > whereby we only fix bugs and make minor improvements to existing
features.
> > > > >
> > > > > I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4
> > > > > features in iBATIS 2.x.
> > > > >
> > > > > Instead, I'm thinking iBATIS 3.0 should cover all of those, with
> > > > > 2.x still supported until JDK 1.4 drops to well below 15% usage
> > > > > (it's currently at around 80%).
> > > > >
> > > > > Thoughts welcome.
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Clinton
> > > > >
> > > >
> > > >
> > >
> >
>

Mime
View raw message