Mailing-List: contact dev-help@ibatis.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ibatis.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jeffgbutler@gmail.com designates
 66.249.92.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=VRGN+vD8vhvbnW+tSuaRuTjU8QiU2ENxAS9nNwhKxeYnVFT79oFkrN3HZTyG0OOzTxBRWLO8QDAbQUgvPLxmCXyZafnsYOA6w2430Q0g3uQeUlyJKkOavrrfK9VknMMListzHr2X4L/hjRVit1PTba0fLqar73KRJRLz3VDe/c8=
Message-ID: <c593b8750608140922r5035113bxc6d026765c1daa05@mail.gmail.com>
Date: Mon, 14 Aug 2006 11:22:35 -0500
From: "Jeff Butler" <jeffgbutler@gmail.com>
To: dev@ibatis.apache.org
Subject: Re: Multiple Result Set Support complete,
 2.2.0 will fly within a week
In-Reply-To: <16178eb10608140909k41f4e794y3b058ad02de0847a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_149096_5972178.1155572555792"
References: <16178eb10608130227o42dc89bahe4288e7d9af8e103@mail.gmail.com>
	 <c593b8750608140856w64373669xd84521115c78ce8c@mail.gmail.com>
	 <16178eb10608140909k41f4e794y3b058ad02de0847a@mail.gmail.com>

------=_Part_149096_5972178.1155572555792
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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.0being the last release except for maintenance.  It's hard to predict what
> > the future holds and we have no idea when iBATIS 3.0 might 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.xstill supported until JDK
> > > 1.4 drops to well below 15% usage (it's currently at around 80%).
> > >
> > > Thoughts welcome.
> > >
> > > Cheers,
> > >
> > > Clinton
> > >
> >
> >
>

------=_Part_149096_5972178.1155572555792
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>LOL - we should do MDD - then we could just draw a pretty picture and there would be NO development time. :)</div>
<div>&nbsp;</div>
<div>Jeff<br><br>&nbsp;</div>
<div><span class="gmail_quote">On 8/14/06, <b class="gmail_sendername">Clinton Begin</b> &lt;<a href="mailto:clinton.begin@gmail.com">clinton.begin@gmail.com</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div><span class="q">&gt;&gt; don't make any grand pronouncements about 2.2.0 <br><br></span></div>
<div>Good call Jeff.&nbsp; Sorry for sounding extreme.&nbsp; We'll definitely be supporting 2.2.0 for a long time, including new features that make too much sense to ignore.&nbsp; <br><br>At the end of the day, we'll always do what makes sense.&nbsp; Our investors don't mind.&nbsp; ;-)
<br><br>&gt;&gt; we don't have any idea how long it will take to develop [iBATIS 3.0]<br><br>I do!&nbsp; According to the latest hype: <br><br>&nbsp; * iBATIS 3.0 will take 4 weeks to write.&nbsp; <br>&nbsp; * <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://ibatis.net/" target="_blank">
iBATIS.NET</a> 3.0 will take 2 weeks to write.<br>&nbsp; * RBatis 3.0 will take 3.5 <span style="FONT-WEIGHT: bold">hours.</span><br><br>Cheers,&nbsp; ;-)<br>&nbsp;</div>
<div><span class="sg">Clinton</span></div>
<div><span class="e" id="q_10d0d71e777d0b54_3"><br><br>
<div><span class="gmail_quote">On 8/14/06, <b class="gmail_sendername">Jeff Butler</b> &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:jeffgbutler@gmail.com" target="_blank">jeffgbutler@gmail.com
</a>&gt; wrote:</span> 
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>
<div>I agree that no new JDK/JDBC&nbsp;features should be put into iBATIS 2.x.&nbsp; But I'd suggest that we don't make any grand pronouncements about 2.2.0 being the last release except for maintenance.&nbsp; It's hard to predict what the future holds and we have no idea when iBATIS 
3.0 might be released.&nbsp; 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.</div>
<div>&nbsp;</div>
<div>So I'd just say that we plan to keep iBATIS 2.x using&nbsp;JDK 1.4.&nbsp; 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. 
</div></div>
<div><span>
<div>&nbsp;</div>
<div>Jeff Butler</div></span></div>
<div><span><br><br>
<div><span class="gmail_quote">On 8/13/06, <b class="gmail_sendername">Clinton Begin</b> &lt;<a onclick="return top.js.OpenExtLink(window,event,this)" href="mailto:clinton.begin@gmail.com" target="_blank">clinton.begin@gmail.com 
</a>&gt; wrote:</span> 
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<div>Hi all,<br><br>The good news is that I'm on vacation.&nbsp; 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. 
<br><br>That was the last &quot;required&quot; 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.&nbsp; There may be a few more things to go, but certainly not of that size. 
<br><br>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.&nbsp; It's been in production for almost 2.5 years, which is great life to get out of any software.&nbsp;&nbsp; 
<br><br>That said, with 2.2.0 out, I fully expect the next major version to be 3.0.&nbsp; I recommend 2.0 enter an extended maintenance mode, whereby we only fix bugs and make minor improvements to existing features.&nbsp; <br><br>
I don't suggest we attempt to leverage Java 5/6 or JDBC 3/4 features in iBATIS 2.x.<br><br>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%).&nbsp; 
<br><br>Thoughts welcome.<br><br>Cheers,<br>&nbsp;</div>
<div><span>Clinton<br></span></div></blockquote></div><br></span></div></blockquote></div><br></span></div></blockquote></div><br>

------=_Part_149096_5972178.1155572555792--