Hi everyone, this is just a friendly reminder that our release processes changed well over a year ago. To summarize, this meant
Master is always stable Strict semantic versioning; http://semver.org Quarterly stable release cycles. There are no such thing as a developer release The implications of this is also that we can not (intentionally) break compatibility within a major version. Upgrading from 5.0 to 5.1/.2/.3 should not break anything, clear the cache, require plugin recompliation or modify behavior based on configs. The second implication is that we expect master to be stable at all time. Since we do Commit Then Review (CTR), this puts extra burden on both committers and reviewers. Everyone, not just committers, are encouraged to review and test commits as they roll in. Committers are expected to both test their commits thoroughly, ideally adding new regression and unit tests as appropriate, as well as asking for reviews if they feel it to be appropriate. Remember, it is never required to ask for a review before commit, but it is never discouraged. Cheers, — leif
