From 4ccacf509f8056c98b065cccca00f94e73992b36 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Sam=20Minn=C3=A9e?= Date: Mon, 21 May 2018 14:08:52 +1200 Subject: [PATCH] Add semver reference in core committers guide --- docs/en/05_Contributing/09_Core_committers.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/en/05_Contributing/09_Core_committers.md b/docs/en/05_Contributing/09_Core_committers.md index caee7afd1..a9cb9a163 100644 --- a/docs/en/05_Contributing/09_Core_committers.md +++ b/docs/en/05_Contributing/09_Core_committers.md @@ -27,6 +27,7 @@ With great power comes great responsibility, so we have agreed on certain expect * Only merge code you have tested and fully understand. If in doubt, ask for a second opinion. * Ensure contributions have appropriate [test coverage](../developer_guides/testing), are documented, and pass our [coding conventions](/getting_started/coding_conventions) * Keep the codebase "releasable" at all times (check our [release process](release_process)) + * Follow [Semantic Versioning](code/#picking-the-right-version) by putting any changes into the correct branch * API changes and non-trivial features should not be merged into release branches. * API changes on master should not be merged until they have the buy-in of at least two Core Committers (or better, through the [core mailing list](https://groups.google.com/forum/#!forum/silverstripe-dev)) * Be inclusive. Ensure a wide range of SilverStripe developers can obtain an understanding of your code and docs, and you're not the only one who can maintain it.