Hello MifOS Software Development Community, (please note that Emily just made some updates on the features for 1.1 and we made an update on the target release milestone dates.)
we've reached the February 1st patch submission deadline that has been posted on the mifos.org roadmap for a while: http://mifos.org/developers/roadmap/ What this means is that we need to stop accepting code submissions for features that are not on the v1.1 roadmap or that are not fixes for defects. We will open it up again after the v1.1 release. Development for some of the features on the roadmap is still ongoing, heading towards wrapping up to get to a MifOS v1.1 General Availability (GA) release as soon as possible. We want MifOS to have as many useful features as possible over time, and we want to be open in allowing any members of the developer community to influence the direction of the product through code submissions, but we need to achieve a stable v1.1 release and taper down the risk of integrating new features as we get closer to that release, so that is why we have a patch submission deadline. The upcoming dates of importance to the developer community still include feature freeze and code freeze. Also there is a proposed schema freeze date and the idea there is to finish any remaining changes to the database schema for MifOS v1.1 earlier rather than later, since they can impact other dependencies. Again, the principle is to keep reducing the risk of missing the GA date as we get closer and closer to it. During the process of working towards the v1.1 release, we have gained greater visibility into the remaining work and speed of development, and so we have provided new targets for the feature freeze and code freeze dates based on that, seen on the roadmap page: http://mifos.org/developers/roadmap/product-roadmap#v1.1 It is important to note that these dates are target dates, for the purpose of having the entire MifOS development community working towards the same release checkpoints. If your business needs committed dates, those will be later dates, and you should discuss them with your MifOS business liaison. For any of these developer dates of note, there may be a few specific exceptions that we can accommodate, but we will likely need to say "no" to these to reduce the overall timeline and risk for v1.1. Once v1.1 is deployed it will be much easier to update it with new functionality. Feel free to email Emily and me if you feel that an exception may be warranted. Once we hit feature freeze, the plan is that our core teams of 15+ developers will launch into a one-month bug fixing sprint. Our Quality Assessment (QA) teams will be continuously verifying bug fixes during this time, and our Program Management (PM) team will be continuously prioritizing defects to fix. More details on the release process to follow. I'm happy to be part of the community that is producing the highest quality MifOS software release so far. thanks, 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
