Ubersetzung will be branching in about a week(ish) so it is still to early to start Voxhumana work, but I thought now would be a good time to start discussion about how to develop the next release as a whole.
The span between hasta-la-qb+ and ubersetzung will end up being a little over 13 months, which is just too long. So as we start to work on voxhumana, lets try to keep it as stable as possible the whole way through. That does not mean we can't introduce big changes, but it does mean we need to do those changes in a way that doesn't break things. Break up your big feature implementation into small steps nobody is going to yell at you for making 30 tiny commits instead of 1 big one-- in fact, you will be applauded for such organization. Breaking up a big change into small parts helps you see how those changes depend on one another, and can expose unexpected side-effects that might have gone unnoticed if you did it all at once. Plus, regressions are easier to find when the changesets are smaller. Also, communication is important. We all have pet projects that we want to see implemented, but those implementations can go more smoothly if we talk about what we want to accomplish either here on the list or on the wiki. http://gilgamesh.hamsterrepublic.com/wiki/ohrrpgce/index.php/Source#Development_Plans --- James _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
