Changes between Version 12 and Version 13 of DeveloperDocumentation

Timestamp:

10/09/23 11:28:38 (7 months ago)

Author:

flichtenheld

Comment:

update release process description

DeveloperDocumentation

@@ -40 +40 @@
 Prior to making a release the following happens:
 
- * Features to include will be selected from the "testing" tree
- * Features will be stabilized until they don't change much
- * A staging "stable candidate" branch will be created
- * Beta release will be published based on this staging branch (to get people to _really_ test the code)
+ * Features to include will be merged to the '''master''' branch.
+ * Features will be stabilized until they don't change much.
+ * Beta release will be published based on latest '''master''' (to get people to _really_ test the code)
   * This should have most features for the release included, and as such be mostly testing and bug fixing. However, new features could still change as much as needed and old features could be changed if absolutely needed.
- * RC release will published based on this staging branch
-  * This should focus only on stabilisation and bugfixes. At this point we know for sure which features should be included. Only in worst cases should a feature taken out, e.g. if it really is horrendous to stability.
- * Once staging branch is deemed stable enough, an official release will be made
-
-In the IRC meeting on [https://community.openvpn.net/openvpn/wiki/IrcMeetings 22nd July 2010] it was decided to aim for 6-12 month release cycle to keep the need for large-scale testing minimal.
+ * RC release will published based on latest '''master'''
+  * This should focus only on stabilization and bug fixes. At this point we know for sure which features should be included. Only in worst cases should a feature taken out, e.g. if it really is horrendous to stability.
+ * Once the code-base is deemed stable enough, an official release will be made
+ * Once there is need to use the '''master''' branch for the next release version (i.e. new features should be merged that will not go into the current release), a '''release/2.x''' branch will branched off. This might happen at any point during the Beta phase but if there is no need could also be delayed until after the official release.
+
+The project currently aims for a 2 year release cycle. Shorter release cycles don't seem achievable with the current level of test automation.
 
 == Feature deprecation ==