You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by Clinton Begin <cl...@gmail.com> on 2006/11/20 18:56:11 UTC
[VOTE] Release iBATIS 2.3
Hi all,
I'd like to release iBATIS 2.3 sometime this week. The changes listed for
the release are as follows:
o DEPRECATED All PaginatedList related features due to misuse, minimal
applicability and inflexibility
o DEPRECATED DAO Framework -- Removed from primary distribution, available
as a separate download
o Removed DAO framework from Subversion source tree (tagged before removal)
o Changed deployment file naming convention, dropped "DBL" and lowercased
all
o Merged common and sqlmap jar files (no more DAO means there's no point in
keeping commons separate)
o Implemented transaction level PreparedStatement caching
o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
Cheers,
Clinton
Re: [VOTE] Release iBATIS 2.3
Posted by Jan Vissers <Ja...@cumquat.nl>.
Agreed!
Brandon Goodin wrote:
> +1 on GA 2.2
> +1 on 2.3 - since we have made changes to the jar organization it
> would be
> good to get it out there. From that point we can begin to work our bug
> fixes. 2.3.x...
>
> On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>>
>> We can vote for GA anytime, even after another release makes it to GA.
>> The beta, alpha, GA status is always flexible.
>>
>> We could vote for GA on 2.2. right now actually.
>>
>> Cheers,
>> Clinton
>>
>> On 11/20/06, j-lists <ja...@gmail.com> wrote:
>> >
>> > Does this mean 2.2 will never be a GA release or that it already is?
>> >
>> > On 11/21/06, Clinton Begin <cl...@gmail.com> wrote:
>> > > Hi all,
>> > >
>> > > I'd like to release iBATIS 2.3 sometime this week. The changes
>> listed
>> > for
>> > > the release are as follows:
>> > >
>> > > o DEPRECATED All PaginatedList related features due to misuse,
>> > minimal
>> > > applicability and inflexibility
>> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
>> > available
>> > > as a separate download
>> > > o Removed DAO framework from Subversion source tree (tagged before
>> > removal)
>> > > o Changed deployment file naming convention, dropped "DBL" and
>> > lowercased
>> > > all
>> > > o Merged common and sqlmap jar files (no more DAO means there's no
>> > point in
>> > > keeping commons separate)
>> > > o Implemented transaction level PreparedStatement caching
>> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value
>> specified
>> >
>> > > o Fixed IBATIS-353 - Probe exception when using inheritance
>> > hierarchies
>> > >
>> > > Cheers,
>> > > Clinton
>> > >
>> >
>>
>>
>
> ------------------------------------------------------------------------
>
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.5.430 / Virus Database: 268.14.11/543 - Release Date: 20-11-2006 21:20
>
--
Cumquat Information Technology
De Dreef 19
3706 BR Zeist
T +31 (0)30 - 6940490
F +31 (0)30 - 6940499
http://www.cumquat.nl
Jan.Vissers@cumquat.nl
M +31 6 51 169 556
Re: [VOTE] Release iBATIS 2.3
Posted by Brandon Goodin <br...@gmail.com>.
+1 on GA 2.2
+1 on 2.3 - since we have made changes to the jar organization it would be
good to get it out there. From that point we can begin to work our bug
fixes. 2.3.x...
On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>
> We can vote for GA anytime, even after another release makes it to GA.
> The beta, alpha, GA status is always flexible.
>
> We could vote for GA on 2.2. right now actually.
>
> Cheers,
> Clinton
>
> On 11/20/06, j-lists <ja...@gmail.com> wrote:
> >
> > Does this mean 2.2 will never be a GA release or that it already is?
> >
> > On 11/21/06, Clinton Begin <cl...@gmail.com> wrote:
> > > Hi all,
> > >
> > > I'd like to release iBATIS 2.3 sometime this week. The changes listed
> > for
> > > the release are as follows:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > minimal
> > > applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > available
> > > as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > lowercased
> > > all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > point in
> > > keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> >
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > hierarchies
> > >
> > > Cheers,
> > > Clinton
> > >
> >
>
>
Re: [VOTE] Release iBATIS 2.3
Posted by Clinton Begin <cl...@gmail.com>.
We can vote for GA anytime, even after another release makes it to GA. The
beta, alpha, GA status is always flexible.
We could vote for GA on 2.2. right now actually.
Cheers,
Clinton
On 11/20/06, j-lists <ja...@gmail.com> wrote:
>
> Does this mean 2.2 will never be a GA release or that it already is?
>
> On 11/21/06, Clinton Begin <cl...@gmail.com> wrote:
> > Hi all,
> >
> > I'd like to release iBATIS 2.3 sometime this week. The changes listed
> for
> > the release are as follows:
> >
> > o DEPRECATED All PaginatedList related features due to misuse, minimal
> > applicability and inflexibility
> > o DEPRECATED DAO Framework -- Removed from primary distribution,
> available
> > as a separate download
> > o Removed DAO framework from Subversion source tree (tagged before
> removal)
> > o Changed deployment file naming convention, dropped "DBL" and
> lowercased
> > all
> > o Merged common and sqlmap jar files (no more DAO means there's no
> point in
> > keeping commons separate)
> > o Implemented transaction level PreparedStatement caching
> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
> >
> > Cheers,
> > Clinton
> >
>
Re: [VOTE] Release iBATIS 2.3
Posted by j-lists <ja...@gmail.com>.
Does this mean 2.2 will never be a GA release or that it already is?
On 11/21/06, Clinton Begin <cl...@gmail.com> wrote:
> Hi all,
>
> I'd like to release iBATIS 2.3 sometime this week. The changes listed for
> the release are as follows:
>
> o DEPRECATED All PaginatedList related features due to misuse, minimal
> applicability and inflexibility
> o DEPRECATED DAO Framework -- Removed from primary distribution, available
> as a separate download
> o Removed DAO framework from Subversion source tree (tagged before removal)
> o Changed deployment file naming convention, dropped "DBL" and lowercased
> all
> o Merged common and sqlmap jar files (no more DAO means there's no point in
> keeping commons separate)
> o Implemented transaction level PreparedStatement caching
> o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
>
> Cheers,
> Clinton
>
Re: [VOTE] Release iBATIS 2.3
Posted by Jeff Butler <je...@gmail.com>.
+1 on releasing 2.3 on November 30.
I'd be happy to do the build.
Jeff Butler
On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Okay, I've fixed iBATIS-369. It was a simple omission on my part.
>
> Jeff, you seem to have the best handle on what is outstanding and what
> could be finished by November 30th.
>
> Would you like to be the build master for iBATIS 2.3?
>
> Cheers,
> Clinton
>
>
>
Re: [VOTE] Release iBATIS 2.3
Posted by Clinton Begin <cl...@gmail.com>.
Okay, I've fixed iBATIS-369. It was a simple omission on my part.
Jeff, you seem to have the best handle on what is outstanding and what could
be finished by November 30th.
Would you like to be the build master for iBATIS 2.3?
Cheers,
Clinton
On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>
> Having looked through the issues, I think you're definitely right about
> #3. I've logged it in JIRA (IBATIS-369).
>
> The other issues I'm not hung up on, but I'm happy to wait until after the
> weekend. I think for the most part people are looking for a release date.
>
> Can we target for November 30th?
>
> Cheers,
> Clinton
>
>
> On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> >
> > I don't want to hold this release up for any non-critical fixes.
> >
> > The reason I'm putting this up for vote now is that people have been
> > waiting for this release for a long time. I'd be happy to release 2.3and then roll the grouping of JIRA issues you mentioned into
> > 2.4 or 2.3.1, whichever makes sense.
> >
> > The current list is already pretty significant, not in quantity, but in
> > size of the changes.
> >
> > Cheers,
> > Clinton
> >
> > On 11/20/06, Jeff Butler <je...@gmail.com> wrote:
> > >
> > > Since there's nothing in this relase so far that the community is
> > > really wanting/needing, I think it would be worthwhile to take a look at
> > > some of the other open issues before doing another release. Specifically:
> > >
> > > 1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a
> > > serious triage).
> > >
> > > 2. I think we should allow a <resultMap> with no <result> sub elements
> > > per this conversation (I ran into this issue myself recently in one of my
> > > projects):
> > >
> > > http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html
> > >
> > > 3. Someone should take a serious look at this potential issue with
> > > prepared statement caching - at least make the error message more
> > > helpful than "this is likely a bug":
> > >
> > > http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html
> > >
> > > 4. Lastly (my continuing prodding) - any new feature that is added
> > > should be documented in the PDF. iBATIS is in wide enough use that we need
> > > to be more serious about our documentation. I'm thinking specifically of
> > > prepared statement caching, multiple result sets, and Oracle cursor
> > > support. Each of these things have generated multiple questions on the user
> > > list. We can't say "RTFM" if we don't have any FM :) Also, the PDF should
> > > be updated to reflect the new packaging for 2.3.
> > >
> > > I will have time over the holiday weekend to work on some of these,
> > > so I propose waiting at least another week or two.
> > >
> > > I'm -1 until some of these other issues are resolved one way or
> > > another.
> > >
> > > Jeff Butler
> > >
> > >
> > >
> > > On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > > >
> > > > Hi all,
> > > >
> > > > I'd like to release iBATIS 2.3 sometime this week. The changes
> > > > listed for the release are as follows:
> > > >
> > > > o DEPRECATED All PaginatedList related features due to misuse,
> > > > minimal applicability and inflexibility
> > > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > > available as a separate download
> > > > o Removed DAO framework from Subversion source tree (tagged before
> > > > removal)
> > > > o Changed deployment file naming convention, dropped "DBL" and
> > > > lowercased all
> > > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > > point in keeping commons separate)
> > > > o Implemented transaction level PreparedStatement caching
> > > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value
> > > > specified
> > > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > > hierarchies
> > > >
> > > > Cheers,
> > > > Clinton
> > > >
> > >
> > >
> >
>
Re: [VOTE] Release iBATIS 2.3
Posted by Clinton Begin <cl...@gmail.com>.
Having looked through the issues, I think you're definitely right about #3.
I've logged it in JIRA (IBATIS-369).
The other issues I'm not hung up on, but I'm happy to wait until after the
weekend. I think for the most part people are looking for a release date.
Can we target for November 30th?
Cheers,
Clinton
On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>
> I don't want to hold this release up for any non-critical fixes.
>
> The reason I'm putting this up for vote now is that people have been
> waiting for this release for a long time. I'd be happy to release 2.3 and
> then roll the grouping of JIRA issues you mentioned into 2.4 or 2.3.1,
> whichever makes sense.
>
> The current list is already pretty significant, not in quantity, but in
> size of the changes.
>
> Cheers,
> Clinton
>
> On 11/20/06, Jeff Butler <je...@gmail.com> wrote:
> >
> > Since there's nothing in this relase so far that the community is really
> > wanting/needing, I think it would be worthwhile to take a look at some of
> > the other open issues before doing another release. Specifically:
> >
> > 1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a
> > serious triage).
> >
> > 2. I think we should allow a <resultMap> with no <result> sub elements
> > per this conversation (I ran into this issue myself recently in one of my
> > projects):
> >
> > http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html
> >
> > 3. Someone should take a serious look at this potential issue with
> > prepared statement caching - at least make the error message more
> > helpful than "this is likely a bug":
> >
> > http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html
> >
> > 4. Lastly (my continuing prodding) - any new feature that is added
> > should be documented in the PDF. iBATIS is in wide enough use that we need
> > to be more serious about our documentation. I'm thinking specifically of
> > prepared statement caching, multiple result sets, and Oracle cursor
> > support. Each of these things have generated multiple questions on the user
> > list. We can't say "RTFM" if we don't have any FM :) Also, the PDF should
> > be updated to reflect the new packaging for 2.3.
> >
> > I will have time over the holiday weekend to work on some of these, so I
> > propose waiting at least another week or two.
> >
> > I'm -1 until some of these other issues are resolved one way or another.
> >
> > Jeff Butler
> >
> >
> >
> > On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > >
> > > Hi all,
> > >
> > > I'd like to release iBATIS 2.3 sometime this week. The changes listed
> > > for the release are as follows:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > > minimal applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > available as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > > lowercased all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > point in keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > >
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > hierarchies
> > >
> > > Cheers,
> > > Clinton
> > >
> >
> >
>
Re: [VOTE] Release iBATIS 2.3
Posted by Brice Ruth <bd...@gmail.com>.
+0
On 11/20/06, Clinton Begin <cl...@gmail.com> wrote:
>
> I don't want to hold this release up for any non-critical fixes.
>
> The reason I'm putting this up for vote now is that people have been
> waiting for this release for a long time. I'd be happy to release 2.3 and
> then roll the grouping of JIRA issues you mentioned into 2.4 or 2.3.1,
> whichever makes sense.
>
> The current list is already pretty significant, not in quantity, but in
> size of the changes.
>
> Cheers,
> Clinton
>
> On 11/20/06, Jeff Butler <je...@gmail.com> wrote:
> >
> > Since there's nothing in this relase so far that the community is really
> > wanting/needing, I think it would be worthwhile to take a look at some of
> > the other open issues before doing another release. Specifically:
> >
> > 1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a
> > serious triage).
> >
> > 2. I think we should allow a <resultMap> with no <result> sub elements
> > per this conversation (I ran into this issue myself recently in one of my
> > projects):
> >
> > http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html
> >
> > 3. Someone should take a serious look at this potential issue with
> > prepared statement caching - at least make the error message more
> > helpful than "this is likely a bug":
> >
> > http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html
> >
> > 4. Lastly (my continuing prodding) - any new feature that is added
> > should be documented in the PDF. iBATIS is in wide enough use that we need
> > to be more serious about our documentation. I'm thinking specifically of
> > prepared statement caching, multiple result sets, and Oracle cursor
> > support. Each of these things have generated multiple questions on the user
> > list. We can't say "RTFM" if we don't have any FM :) Also, the PDF should
> > be updated to reflect the new packaging for 2.3.
> >
> > I will have time over the holiday weekend to work on some of these, so I
> > propose waiting at least another week or two.
> >
> > I'm -1 until some of these other issues are resolved one way or another.
> >
> > Jeff Butler
> >
> >
> >
> > On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> > >
> > > Hi all,
> > >
> > > I'd like to release iBATIS 2.3 sometime this week. The changes listed
> > > for the release are as follows:
> > >
> > > o DEPRECATED All PaginatedList related features due to misuse,
> > > minimal applicability and inflexibility
> > > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > > available as a separate download
> > > o Removed DAO framework from Subversion source tree (tagged before
> > > removal)
> > > o Changed deployment file naming convention, dropped "DBL" and
> > > lowercased all
> > > o Merged common and sqlmap jar files (no more DAO means there's no
> > > point in keeping commons separate)
> > > o Implemented transaction level PreparedStatement caching
> > > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > >
> > > o Fixed IBATIS-353 - Probe exception when using inheritance
> > > hierarchies
> > >
> > > Cheers,
> > > Clinton
> > >
> >
> >
>
--
Brice Ruth
Software Engineer, Madison WI
Re: [VOTE] Release iBATIS 2.3
Posted by Clinton Begin <cl...@gmail.com>.
I don't want to hold this release up for any non-critical fixes.
The reason I'm putting this up for vote now is that people have been waiting
for this release for a long time. I'd be happy to release 2.3 and then roll
the grouping of JIRA issues you mentioned into 2.4 or 2.3.1, whichever makes
sense.
The current list is already pretty significant, not in quantity, but in size
of the changes.
Cheers,
Clinton
On 11/20/06, Jeff Butler <je...@gmail.com> wrote:
>
> Since there's nothing in this relase so far that the community is really
> wanting/needing, I think it would be worthwhile to take a look at some of
> the other open issues before doing another release. Specifically:
>
> 1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a
> serious triage).
>
> 2. I think we should allow a <resultMap> with no <result> sub elements per
> this conversation (I ran into this issue myself recently in one of my
> projects):
>
> http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html
>
> 3. Someone should take a serious look at this potential issue with
> prepared statement caching - at least make the error message more
> helpful than "this is likely a bug":
>
> http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html
>
> 4. Lastly (my continuing prodding) - any new feature that is added should
> be documented in the PDF. iBATIS is in wide enough use that we need to be
> more serious about our documentation. I'm thinking specifically of prepared
> statement caching, multiple result sets, and Oracle cursor support. Each of
> these things have generated multiple questions on the user list. We can't
> say "RTFM" if we don't have any FM :) Also, the PDF should be updated to
> reflect the new packaging for 2.3.
>
> I will have time over the holiday weekend to work on some of these, so I
> propose waiting at least another week or two.
>
> I'm -1 until some of these other issues are resolved one way or another.
>
> Jeff Butler
>
>
>
> On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
> >
> > Hi all,
> >
> > I'd like to release iBATIS 2.3 sometime this week. The changes listed
> > for the release are as follows:
> >
> > o DEPRECATED All PaginatedList related features due to misuse, minimal
> > applicability and inflexibility
> > o DEPRECATED DAO Framework -- Removed from primary distribution,
> > available as a separate download
> > o Removed DAO framework from Subversion source tree (tagged before
> > removal)
> > o Changed deployment file naming convention, dropped "DBL" and
> > lowercased all
> > o Merged common and sqlmap jar files (no more DAO means there's no
> > point in keeping commons separate)
> > o Implemented transaction level PreparedStatement caching
> > o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> > o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
> >
> > Cheers,
> > Clinton
> >
>
>
Re: [VOTE] Release iBATIS 2.3
Posted by Jeff Butler <je...@gmail.com>.
Since there's nothing in this relase so far that the community is really
wanting/needing, I think it would be worthwhile to take a look at some of
the other open issues before doing another release. Specifically:
1. JIRA 349, 357, 366, and 367 (maybe others too - I haven't done a serious
triage).
2. I think we should allow a <resultMap> with no <result> sub elements per
this conversation (I ran into this issue myself recently in one of my
projects):
http://www.mail-archive.com/dev@ibatis.apache.org/msg02026.html
3. Someone should take a serious look at this potential issue with prepared
statement caching - at least make the error message more helpful than "this
is likely a bug":
http://www.mail-archive.com/user-java@ibatis.apache.org/msg06919.html
4. Lastly (my continuing prodding) - any new feature that is added should
be documented in the PDF. iBATIS is in wide enough use that we need to be
more serious about our documentation. I'm thinking specifically of prepared
statement caching, multiple result sets, and Oracle cursor support. Each of
these things have generated multiple questions on the user list. We can't
say "RTFM" if we don't have any FM :) Also, the PDF should be updated to
reflect the new packaging for 2.3.
I will have time over the holiday weekend to work on some of these, so I
propose waiting at least another week or two.
I'm -1 until some of these other issues are resolved one way or another.
Jeff Butler
On 11/20/06, Clinton Begin <clinton.begin@gmail.com > wrote:
>
> Hi all,
>
> I'd like to release iBATIS 2.3 sometime this week. The changes listed for
> the release are as follows:
>
> o DEPRECATED All PaginatedList related features due to misuse, minimal
> applicability and inflexibility
> o DEPRECATED DAO Framework -- Removed from primary distribution,
> available as a separate download
> o Removed DAO framework from Subversion source tree (tagged before
> removal)
> o Changed deployment file naming convention, dropped "DBL" and lowercased
> all
> o Merged common and sqlmap jar files (no more DAO means there's no point
> in keeping commons separate)
> o Implemented transaction level PreparedStatement caching
> o Fixed IBATIS-335 - Don't call setQueryTimeout if no value specified
> o Fixed IBATIS-353 - Probe exception when using inheritance hierarchies
>
> Cheers,
> Clinton
>