also, I took your suggestion and added this improvement to the roadmap page. It is not clear to me whether this would occur in the next major release (which is tentatively called 2.0) or the next minor release (which is tentatively called 1.15). Please note that as we wrap-up Mifos v1.1, those tentative names for the next releases will likely change, and the roadmap and plans for the next releases are likely to change significantly, and are certainly open to input from the entire community -- let's wait until v1.1 is ready to share with the world before we start shifting the community discussion to what those next releases should look like, but that will be a very productive discussion for everyone to join at that time.
thank you, Sam On 3/7/08 7:57 AM, "Sam Birney" <[EMAIL PROTECTED]> wrote: > > Hi Max, et. al., > > we certainly understand having no bandwidth for this change, we are in the > same boat. > > It is agreed, let us not make this a first-order objective for Mifos v1.1 due > to bandwidth limitations. Let's not consider it an additional task. > > However, if it turns out to be the path of least resistance to move away from > Mayfly for addressing the unit-test issues in the way of finishing the > hibernate work, and that would be the lowest effort and least risky solution, > you have our blessing to use that approach. > > thanks, > Sam > > > On 3/7/08 3:37 AM, "Massimiliano Parlione" <[EMAIL PROTECTED]> wrote: > >> Hi Van, >> from our side there is no bandwidth to do this change. We all agree that we >> need to review the overall architecture of the test cases. >> >> Personally I think all the test cases should be executed against an >> in-memory database such as Derby or others as suggested by Stephen to >> execute the tests quickly and without requiring an external database >> installed on the machine. >> I addition the test suite should have a configuration file that allows to >> switch from the in-memory database to the database supported by the >> product. In this way it is possible to verify if the code is actually >> working with MySQL without slowing down the development activity or the >> build server. >> >> The current situation in not brilliant because we have some tests executed >> against myFly and others against MySQL. >> >> - Would you like to track this issue on the issue tracker ? Otherwise we >> can add this activity for the next release in the product roadmap in the >> unscheduled features section (Architecture enhancements) >> We could add something like this at the end >> (http://mifos.org/developers/roadmap/product-roadmap): >> >> - test cases re-engineering (choice of an in-memory db, decrease the >> execution time, ....), >> >> Regards, >> Max >> ----------------------------------------------------- >> Massimiliano Parlione - >> http://w4.ibm.com/bluepages/html/[EMAIL PROTECTED] >> Current Project: https://w3.webahead.ibm.com/w3ki/display/MIFOS/Home >> Building 6, Innovation Center, Meeting Room 1 >> IBM Technology Campus >> Damastown Industrial Estate >> Mulhuddart >> Dublin 15 >> Ireland >> Phone (external): +35318152394 >> Extension Number: 512394 >> IBM International Holdings BV registered in Ireland with number 903924. >> Registered office: Oldbrook House, 24-32 Pembroke Road, Ballsbridge, Dublin >> 4 >> ------------------------------------------------------- >> >> >> >> "Van >> Mittal-Henkle" >> <[EMAIL PROTECTED] To >> ndation.org> "Stephen Horgan" >> <[EMAIL PROTECTED]>, Chico >> 06/03/2008 23:16 Charlesworth/Ireland/Contr/[EMAIL >> PROTECTED] >> E >> cc >> "Sam Birney" >> <[EMAIL PROTECTED]>, >> "Adam Monsen" <[EMAIL PROTECTED]>, >> Roberto >> Musso/Ireland/Contr/[EMAIL PROTECTED], >> Massimiliano >> Parlione/Ireland/[EMAIL PROTECTED] >> Subject >> Mayfly replacements >> >> >> >> >> >> >> >> >> >> >> Hi All, >> >> I was reviewing the discussion on irc from yesterday about Mayfly, MySQL >> and HSQLDB. I definitely agree that it would help us to move forward >> faster if we did not have this dependency. On more than one occasion I >> have come close to diving in and making this change. >> >> One suggestion is that as a first step you might try generalizing the >> code such that we could plug in MySQL as a replacement for Mayfly in the >> current tests, since we know will MySQL will work. Of course, this will >> be slower than an in-memory db, but at least we know that it can be used >> to unblock us if we run into Mayfly issues. Once the code is general >> enough to plug in a MySQL replacement, then it should be in a state >> where a HSQLDB replacement could also be tried. >> >> --Van >> >> >> ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
