Hello fellow Mahara developers, I'm starting to feel that we really need to stabilise the code base or we'll never get the final release out. We've got to do that soon because there are a number of users who needed a stable release a week ago, and they still haven't got it.
So I've created a 1.3_STABLE branch, I've been cherry-picking commits to master onto that branch, and we'll eventually create the release from that branch. Now we only want to cherry-pick the patches that are very unlikely to cause more bugs, so I'm not so keen for us to apply commits to stable which add new features, commits with names like 'Refactor blah blah blah...', or pretty much any large commit, unless they're linked to a bug report that describes the issue and has some reasonable argument for why the issue is urgent enough to need fixing on the stable branch. Other new stuff could probably do with more testing, so it can stay on master and wait for the next release. Dan is keen that we mention a bug number in every commit we make. I think that's a noble endeavour, so I've been creating more bug reports recently. I haven't done it for everything I've committed, but I think we should try. If nothing else it gets better discussions going on the tracker. Richard. _______________________________________________ Mailing list: https://launchpad.net/~mahara-core Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-core More help : https://help.launchpad.net/ListHelp
