Hi All, This all sounds good!
On Mon, Sep 6, 2010 at 11:54 PM, Richard Mansfield <[email protected]> wrote: > 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. For the future I think we could conceivably have this sort of behaviour on master, and focus all efforts on testing and stabilising the codebase there. Perhaps this could be facilitated better by having strict 'guidelines' for the freeze period? If possible I think its beneficial that developers respect the 'cycle' which the software is in so we don't give the impression that master is a 'free-for-all' and rely on branching for stabilisation? > 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. I agree - I think this works really well in moodle-land, if nothing else it provides a communication channel for conveying how to improve a commit, or suggest that it might not be appropriate and helps open discussions. Also it helps developers get a feel for the changes happening by following bugs. Dan _______________________________________________ Mailing list: https://launchpad.net/~mahara-core Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-core More help : https://help.launchpad.net/ListHelp
