summaryrefslogtreecommitdiff
path: root/RELEASES.md
diff options
context:
space:
mode:
authorNikos Mavrogiannopoulos <nmav@gnutls.org>2019-05-26 21:35:19 +0200
committerNikos Mavrogiannopoulos <nmav@gnutls.org>2019-05-26 21:53:16 +0200
commitefeb175a7fc47957ec0d6b3984118638a4199f6d (patch)
treee956f48cc9dad2f6789d0afe64e35bbbd2601a48 /RELEASES.md
parentb7e56693a937f7fda5d825093bea8952c506ef8c (diff)
downloadgnutls-efeb175a7fc47957ec0d6b3984118638a4199f6d.tar.gz
RELEASES.md: document the releases policy [ci skip]tmp-releases
This adds a file to document the policy on releases based on the discussions taken place in the last face to face meeting. https://gitlab.com/gnutls/gnutls/wikis/face2face-meeting-fosdem2019 Signed-off-by: Nikos Mavrogiannopoulos <nmav@gnutls.org>
Diffstat (limited to 'RELEASES.md')
-rw-r--r--RELEASES.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/RELEASES.md b/RELEASES.md
new file mode 100644
index 0000000000..c0a840c2c5
--- /dev/null
+++ b/RELEASES.md
@@ -0,0 +1,18 @@
+# Release policy
+
+In the GnuTLS project there are at most two ongoing releases, one marked as
+'stable' and one marked as 'next'. The former is always present and
+supported, while the latter is introduced on the discretion of the
+development team.
+
+For both release branches all the rules in [CONTRIBUTING.md](CONTRIBUTING.md)
+apply, but in principle the 'stable' release is more conservative in new features,
+while the 'next' branch allows for mild behavioral changes. The 'stable' branch
+always provides API and ABI compatibility, while the 'next' branch may on exceptional
+cases change the API.
+
+
+|Branch|Version|Release interval|
+|:----:|:-----:|:--------------:|
+|stable|3.6.x |bi-monthly |
+|next |- | |