So we've delayed the release a bit to get plans and collections firmly into the release. However, given that many institutions start the school year in early September, we're feeling some pressure to get the release out soon.
Here's what we'd like to propose: - freeze master this weekend - cut the RC early next week (aiming for 31 August) What the freeze would mean is that as of this coming weekend, the stable branch policy [1] would apply and so sites could start upgrading, confident that nothing major would break or change and that only bugfixes would be added after 1.3.0rc1. What do you think? Is it workable? Cheers, Francois & Richard [1] The usual stable branch policy being no new features and important bug fixes only (http://wiki.mahara.org/Developer_Area/Code_Review)
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Mailing list: https://launchpad.net/~mahara-core Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-core More help : https://help.launchpad.net/ListHelp
