You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user-java@ibatis.apache.org by Clinton Begin <cl...@gmail.com> on 2008/07/16 21:44:52 UTC
[ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Practically moments after promoting iBATIS 2.3.2 to GA, a number of nasty
bugs were discovered, particularly with the Spring integration. We
refactored a lot of "internal" (i.e. non-client) code in these latest
versions, and so as an end-user, you really need to test the Betas. So from
now on, we're going to wait until we get enough confirmation from actual
production implementations (either through test suites or staging
environments) that things are working well. I'm thinking at least 20
responses before moving to GA.
In the long run we'll identify dedicated testers who are willing to update
to the latest beta and run a comprehensive application test suite against
it.
This is necessary to preserve the importance of flagging a release as
"General Availability" (Apache's way of saying "Production Ready-ish").
BETA INSTRUCTIONS:
* From now on, when you see a Beta release like this one, get it!
* Plug it into your app.
* Run your unit test suite.
* Put it on your staging environment.
* If all looks good, roll it out to production (yes, the Beta).
> If your application is doing any less than absolutely mission
critical, deploy the Beta.
> Note: We don't change the release files when promoting to GA. So
when it's out of beta, you just keep using the same software.
* After a week or so, reply to this [ANNOUNCE] marked thread with a +1,
showing your confidence in the framework. Include brief details of your
stack (app server, Spring, JDK version, web framework, etc.)
When we receive 20 replies (a guess at a start), we'll put the vote to the
committers to promote the release to GA.
I'd like to consider making "Beta Tester" a formal role on our project. I'm
not sure of the details yet, but you can start by testing this Beta in your
environment and responding to this thread with results as above.
Cheers
Clinton
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Kai Grabfelder <no...@kinokai.de>.
Hi there,
I was doing the exactly same thing with 2.3.2 beta. I've used it to run our Unit Tests (using Spring 2.0.8
because we are still using Hibernate 2) & Hsqldb) against and also used it on our Testing environment (JBoss
4.0.3) for quite some time. The only thing I encountered was IBATIS-501.
I'm doing the same thing with 2.3.4, the application should go to production within the next three weeks. No
problems so far...
Regards
Kai
--- Original Nachricht ---
Absender: Clinton Begin
Datum: 16.07.2008 21:44
> Practically moments after promoting iBATIS 2.3.2 to GA, a number of nasty
> bugs were discovered, particularly with the Spring integration. We
> refactored a lot of "internal" (i.e. non-client) code in these latest
> versions, and so as an end-user, you really need to test the Betas. So from
> now on, we're going to wait until we get enough confirmation from actual
> production implementations (either through test suites or staging
> environments) that things are working well. I'm thinking at least 20
> responses before moving to GA.
>
> In the long run we'll identify dedicated testers who are willing to update
> to the latest beta and run a comprehensive application test suite against
> it.
>
> This is necessary to preserve the importance of flagging a release as
> "General Availability" (Apache's way of saying "Production Ready-ish").
>
> BETA INSTRUCTIONS:
>
> * From now on, when you see a Beta release like this one, get it!
> * Plug it into your app.
> * Run your unit test suite.
> * Put it on your staging environment.
> * If all looks good, roll it out to production (yes, the Beta).
> > If your application is doing any less than absolutely mission
> critical, deploy the Beta.
> > Note: We don't change the release files when promoting to GA. So
> when it's out of beta, you just keep using the same software.
> * After a week or so, reply to this [ANNOUNCE] marked thread with a +1,
> showing your confidence in the framework. Include brief details of your
> stack (app server, Spring, JDK version, web framework, etc.)
>
> When we receive 20 replies (a guess at a start), we'll put the vote to the
> committers to promote the release to GA.
>
> I'd like to consider making "Beta Tester" a formal role on our project. I'm
> not sure of the details yet, but you can start by testing this Beta in your
> environment and responding to this thread with results as above.
>
> Cheers
> Clinton
>
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Tom Duffey <td...@utilivisor.com>.
On Jul 16, 2008, at 2:44 PM, Clinton Begin wrote:
> * After a week or so, reply to this [ANNOUNCE] marked thread
> with a +1, showing your confidence in the framework. Include brief
> details of your stack (app server, Spring, JDK version, web
> framework, etc.)
+1
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Jeff Butler <je...@gmail.com>.
I've updated the ibator build tests to use ibatis-2.3.3. I've also changed
some of the ibator test cases to use Spring (2.5.5).
Everything looks OK from my tests.
Jeff Butler
On Wed, Jul 16, 2008 at 2:44 PM, Clinton Begin <cl...@gmail.com>
wrote:
> Practically moments after promoting iBATIS 2.3.2 to GA, a number of nasty
> bugs were discovered, particularly with the Spring integration. We
> refactored a lot of "internal" (i.e. non-client) code in these latest
> versions, and so as an end-user, you really need to test the Betas. So from
> now on, we're going to wait until we get enough confirmation from actual
> production implementations (either through test suites or staging
> environments) that things are working well. I'm thinking at least 20
> responses before moving to GA.
>
> In the long run we'll identify dedicated testers who are willing to update
> to the latest beta and run a comprehensive application test suite against
> it.
>
> This is necessary to preserve the importance of flagging a release as
> "General Availability" (Apache's way of saying "Production Ready-ish").
>
> BETA INSTRUCTIONS:
>
> * From now on, when you see a Beta release like this one, get it!
> * Plug it into your app.
> * Run your unit test suite.
> * Put it on your staging environment.
> * If all looks good, roll it out to production (yes, the Beta).
> > If your application is doing any less than absolutely mission
> critical, deploy the Beta.
> > Note: We don't change the release files when promoting to GA. So
> when it's out of beta, you just keep using the same software.
> * After a week or so, reply to this [ANNOUNCE] marked thread with a +1,
> showing your confidence in the framework. Include brief details of your
> stack (app server, Spring, JDK version, web framework, etc.)
>
> When we receive 20 replies (a guess at a start), we'll put the vote to the
> committers to promote the release to GA.
>
> I'd like to consider making "Beta Tester" a formal role on our project.
> I'm not sure of the details yet, but you can start by testing this Beta in
> your environment and responding to this thread with results as above.
>
> Cheers
> Clinton
>
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Clinton Begin <cl...@gmail.com>.
That's a fair point -- for maven users. :-)
I'll see if Brandon is willing to commit to that.
Clinton
On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <ha...@gmail.com> wrote:
> Hi Clinton,
>
> I understand you need more testers, but then, why don't you publish these
> betas in the maven repository?
> It would increase the number of testers (1 at least = me).
>
> Sorry if this topic has been discussed already.
>
> Regards,
> Iwao
>
>
>
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Clinton Begin <cl...@gmail.com>.
Absolutely. The only reason that version 2.x has been so quiet lately is
that I've been focused on version 3.0. Initially I didn't think a
compatibility kit would be possible, but it's looking more and more like it
will be. I'm nearly finished it to a point where I can make a release of an
iBATIS 3.0 Alpha with 2.x compatibility. There are a few features
intentionally left out of 3.0 though, including nullValue substitution,
direct XML mappings and of course the existing deprecated stuff like
PaginatedList etc.
That said, 2.3.3 is a really big release, and I probably should have called
it 2.4. But live and learn... It's not like the mistake hasn't been made
before (Windows 3.1 ... ;-)
iBATIS has been around for 6 years, and we're the only framework of our
kind. So we're not going anywhere.
http://www.javaworld.com/javaworld/jw-07-2008/jw-07-orm-comparison.html
Cheers,
Clinton
On Thu, Jul 17, 2008 at 7:47 AM, Ian Zabel <ia...@ezabel.com> wrote:
> As a new user to iBatis (we just began using it two weeks ago at my
> company!), I just want to give you guys a big thanks for your work on
> the framework. It's made it a lot more comfortable to know that iBatis
> is under active development, and has a lively community around it.
>
> Keep up the good work!
>
> Ian.
>
> On Thu, Jul 17, 2008 at 9:40 AM, Clinton Begin <cl...@gmail.com>
> wrote:
> >
> > No. The Spring integration is using internals of iBATIS which are not
> meant to be publicly consumed. We're not going to stop evolving our code
> just to keep compatible with 3rd party frameworks that reach into the guts
> of iBATIS. Waiting for 2.4 would just delay the inevitable.
> >
> > The solutions is:
> >
> > * Update the Spring plug-in, and
> > * Use 2.3.0 until it is updated.
> >
> > This doesn't happen every day. In fact it's the first time it's happened
> in 4 years. Let's not make it out to be more of an issue than it is.
> Spring will be updated and all will be well.
> >
> > Clinton
>
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Ian Zabel <ia...@ezabel.com>.
As a new user to iBatis (we just began using it two weeks ago at my
company!), I just want to give you guys a big thanks for your work on
the framework. It's made it a lot more comfortable to know that iBatis
is under active development, and has a lively community around it.
Keep up the good work!
Ian.
On Thu, Jul 17, 2008 at 9:40 AM, Clinton Begin <cl...@gmail.com> wrote:
>
> No. The Spring integration is using internals of iBATIS which are not meant to be publicly consumed. We're not going to stop evolving our code just to keep compatible with 3rd party frameworks that reach into the guts of iBATIS. Waiting for 2.4 would just delay the inevitable.
>
> The solutions is:
>
> * Update the Spring plug-in, and
> * Use 2.3.0 until it is updated.
>
> This doesn't happen every day. In fact it's the first time it's happened in 4 years. Let's not make it out to be more of an issue than it is. Spring will be updated and all will be well.
>
> Clinton
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Clinton Begin <cl...@gmail.com>.
No. The Spring integration is using internals of iBATIS which are not meant
to be publicly consumed. We're not going to stop evolving our code just to
keep compatible with 3rd party frameworks that reach into the guts of
iBATIS. Waiting for 2.4 would just delay the inevitable.
The solutions is:
* Update the Spring plug-in, and
* Use 2.3.0 until it is updated.
This doesn't happen every day. In fact it's the first time it's happened in
4 years. Let's not make it out to be more of an issue than it is. Spring
will be updated and all will be well.
Clinton
On Thu, Jul 17, 2008 at 7:34 AM, Dragan Jotanovic <
Dragan.Jotanovic@diosphere.com> wrote:
> Upgrading to newer version of iBatis is becoming more and more
> complicated.
>
> So now we will have to wait for new version of spring in order to get new
> version of iBatis? Isn't it better just to revert all those changes back on
> branch 2.3.x and start new branch with those changes (2.4 or long waiting
> 3.0)?
>
>
>
>
>
> *From:* Clinton Begin [mailto:clinton.begin@gmail.com]
> *Sent:* Thursday, July 17, 2008 2:21 PM
> *To:* user-java@ibatis.apache.org
> *Subject:* Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
>
>
>
> Wooooow...
>
> K, it's looking more and more like we just need to update the Spring
> integration. I'm not willing to roll back all of the simplifications we
> made to the software. We got rid of a lot of internal cruft that just made
> the code harder to read and didn't serve a purpose.
>
> I'll see what I can do to work with the Spring team to get it updated. I
> no longer consider this a bug, it's an evolution.
>
> Clinton
>
> On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <ha...@gmail.com> wrote:
>
> Hi Clinton,
>
> I understand you need more testers, but then, why don't you publish these
> betas in the maven repository?
> It would increase the number of testers (1 at least = me).
>
> Sorry if this topic has been discussed already.
>
> Regards,
> Iwao
>
>
>
RE: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Dragan Jotanovic <Dr...@DIOSPHERE.com>.
Upgrading to newer version of iBatis is becoming more and more
complicated.
So now we will have to wait for new version of spring in order to get
new version of iBatis? Isn't it better just to revert all those changes
back on branch 2.3.x and start new branch with those changes (2.4 or
long waiting 3.0)?
From: Clinton Begin [mailto:clinton.begin@gmail.com]
Sent: Thursday, July 17, 2008 2:21 PM
To: user-java@ibatis.apache.org
Subject: Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Wooooow...
K, it's looking more and more like we just need to update the Spring
integration. I'm not willing to roll back all of the simplifications we
made to the software. We got rid of a lot of internal cruft that just
made the code harder to read and didn't serve a purpose.
I'll see what I can do to work with the Spring team to get it updated.
I no longer consider this a bug, it's an evolution.
Clinton
On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <ha...@gmail.com> wrote:
Hi Clinton,
I understand you need more testers, but then, why don't you publish
these betas in the maven repository?
It would increase the number of testers (1 at least = me).
Sorry if this topic has been discussed already.
Regards,
Iwao
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Clinton Begin <cl...@gmail.com>.
Wooooow...
K, it's looking more and more like we just need to update the Spring
integration. I'm not willing to roll back all of the simplifications we
made to the software. We got rid of a lot of internal cruft that just made
the code harder to read and didn't serve a purpose.
I'll see what I can do to work with the Spring team to get it updated. I no
longer consider this a bug, it's an evolution.
Clinton
On Thu, Jul 17, 2008 at 4:16 AM, Iwao AVE! <ha...@gmail.com> wrote:
> Hi Clinton,
>
> I understand you need more testers, but then, why don't you publish these
> betas in the maven repository?
> It would increase the number of testers (1 at least = me).
>
> Sorry if this topic has been discussed already.
>
> Regards,
> Iwao
>
>
>
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Iwao AVE! <ha...@gmail.com>.
Hi Clinton,
I understand you need more testers, but then, why don't you publish
these betas in the maven repository?
It would increase the number of testers (1 at least = me).
Sorry if this topic has been discussed already.
Regards,
Iwao
Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Posted by Tom Duffey <td...@utilivisor.com>.
Sorry, I was so excited about this release that I forgot to add
details. See below.
On Jul 16, 2008, at 2:44 PM, Clinton Begin wrote:
> * After a week or so, reply to this [ANNOUNCE] marked thread
> with a +1, showing your confidence in the framework. Include brief
> details of your stack (app server, Spring, JDK version, web
> framework, etc.)
+1
Tomcat 5.5
Spring 2.5.5
Sun JDK 1.6
PostgreSQL 8.2
Spring Web MVC
Proxool data source
Tom