ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Kai Grabfelder <nos...@kinokai.de>
Subject Re: [ANNOUNCE] iBATIS 2.3.3 ... Beta is the new Production
Date Fri, 18 Jul 2008 16:58:35 GMT
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
> 


Mime
View raw message