Not specific to the problem below. But what about providing iBATIS development releases, e.g. after every big round of SVN changes. Most other projects seem to do it.
A few advantages I see: - It's easier to tell people: "test with the development jar files" than "extract the sources from SVN, compile and test" - Better quality of releases as more people would already test/use the development releases. - Less "pressure" to release new versions. Regards, Sven Boden On Tue, 5 Jul 2005 07:29:03 -0600, you wrote: >As soon as brandon gives the go-ahead on IBATIS-148, then we'll be good to >go! > >Cheers, >clinton > >On 7/5/05, Guido García Bernardo <[EMAIL PROTECTED]> wrote: >> >> Hi, >> >> I am facing with this bug: >> http://issues.apache.org/jira/browse/IBATIS-152, solved in 2.1.5 >> >> Is there any release plan for 2.1.5 so that I can decide whether or not >> I'll need to use 2.0.9b or compile the source? >> >> Thank you very much. >> >> -- >> Guido García Bernardo - [EMAIL PROTECTED] >> Tfn. +34 983 54 89 08 >> ITDEUSTO - Valladolid >> >> >>
