Re: [NOTICE] Intending to release 2.2.1

[Brandon Goodin]

I commented on the bug. I can go ahead and mark it deprecated unless you feel we need to put it in front of the team.

https://issues.apache.org/jira/browse/IBATIS-363

Brandon

On 11/3/06, Clinton Begin <[EMAIL PROTECTED]> wrote:

>> https://issues.apache.org/jira/browse/IBATIS-363

I had a look and commented on this issue in JIRA.  Can I request to move forward with 2.3 without this fix?  As you will see in my comments...there are a couple of issues with changing this behavior. 

Would that be okay?

Cheers,
Clinton

On 11/3/06, Brandon Goodin < [EMAIL PROTECTED]> wrote:

I just posted this issue that i'd like to fix for this release. It is a simple fix. But, i wanted to get some feedback as to where we should place it.

https://issues.apache.org/jira/browse/IBATIS-363


Also, I think we need to still make the DAO available on the site for download. Except we need to mark it as deprecated and unsupported. We should also provide upgrade instructions to users if we aren't already going to do so. I can see where this move will be very confusing to some. There are some people who are still using the DAO including our example app.

Brandon

On 11/2/06, Clinton Begin < [EMAIL PROTECTED]> wrote:

Hi everyone,

I would like to release iBATIS 2.2.1 by the end of the weekend if possible. 

It's a pretty significant release, probably more than just a X.X.1 release....we could call it 2.3 if you think that would be more appropriate. 

The changes so far are:

 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

Are there any bugs etc. that should make it into the next release?

Cheers,

Clinton