hello Mifos, we are less than a month away now from our code freeze date of June 30th. This means we'll spend the next couple of weeks fixing the high priority bugs and integrating changes, and then the last two weeks of June wrapping up any loose ends.
For those who are tracking (and helping with) the progress of v1.1, let me highlight a few useful pages found on http://mifos.org: http://mifos.org/developers/roadmap/DevStatus the above page features a "burndown" chart of the remaining development work. we use this to track development trajectory. it shows that we are on track for hitting code freeze, but there is no margin for error, so we need to focus more than ever on shipping v1.1 now. http://mifos.org/developers/testing/v1-1-test-status the above page (thanks to Jeff and IBM Bangalore) has two useful excel spreadsheet links. the first spreadsheet, testing dashboard, shows the current testing coverage and results for various areas of the product. green means tests are passing, yellow means more work is needed, and red means the area needs more work before it can be tested further and completed. the second spreadsheet, issue tracking metrics, shows the ongoing count of total bugs that have been closed (in green) vs. the current number of open bugs (in red). we need the red line to start heading down towards 0 by the time we get to code freeze, so we are focusing on that. over time, we'll add some more explanations on http://mifos.org of how these charts are used in our development process of prioritizing, fixing, and testing bugs. happy June, Sam ------------------------------------------------------------------------- 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/ _______________________________________________ Mifos-functional mailing list Mifos-functional@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-functional
