Differences

This shows you the differences between two versions of the page.

--- devel:release_process [2018-04-21 08:07] – andi
+++ devel:release_process [2023-09-24 20:46] (current) – andi
@@ Line 3: / Line 3: @@
 ===== Release cycle =====
-We run a time-based release cycle with two releases every year. The releases are done after a fixed schedule feature freeze giving necessary time to fix bugs. Thus releases will be spring and autumn.
+We lack the man power to manage a strict release cycle. We usually release about once a year with hotfixes when important security patches are needed.
-  * 1st February / 1st August: Feature Freeze (Triggered by automated mail)
-    * release team: Create tickets for removing outdated deprecations
-    * release team (might be done by Bug/Wishlist Review Team): Collect todo tickets for release
-    * release team: Create changelog
-    * release team and quality team: Run unit tests((also check http://test.dokuwiki.org/)), coding standard checks, check HTML
-    * i18n team: Update Translation (Assume stable string set from now on)
-    * documentation team: Update documentation (Assume stable from now on)
-    * plugin & template team: Write plugin / template developer infos (what got deprecated, what was removed, what is new)
-  * Release / RC (Transition to this step as soon as all todo tickets are closed, ca 1 week after last transition at minimum)
-    * If RC:
-      * release team: Manage new tickets (Mark as todo)
-      * release team: test upgrade last stable installation, Inform / update derivatives
-      * release team and quality team: Run unit tests((also check http://test.dokuwiki.org/)), coding standard checks, check HTML
-      * i18n team: Take a look at bad translations, exclude them? (Here?)
-      * release team: inform plugin & template team, documentation team, i18n team on changes relevant to them
-      * andi or Guy: install RC on dokuwiki.org :)
-    * If Release:
-      * release team: Create tarball
-      * marketing team: Update profiles
 ==== Security ====
@@ Line 36: / Line 15: @@
 The following steps have to be taken for building a new release.
+FIXME: many tasks below have been automated by the GitHub [[devel:release workflows]]. Needs to be refactored.
+==== Version Naming Conventions ====
+  * Release Candidates use the date on which they are released, prefixed with ''rc''
+    * rc2022-06-26 "Igor"
+    * rc2022-07-01 "Igor"
+  * Releases use the date on which they are released, no prefixes or postfixes
+    * 2022-08-12 "Igor"
+  * Hotfixes add a letter to the date of the release they fix
+    * 2022-08-12a "Igor"
+    * 2022-08-12b "Igor"
 ==== Preparation ====
   - find a code name
     * [[http://wiki.lspace.org/mediawiki/Category:Discworld_characters|Discworld Character]] starting with a letter alphabetically after the first letter of the last release name
-    * add RC1(-9) for release candidate
+  - check https://github.com/dokuwiki/dokuwiki/issues for new bugs
-  - check https://github.com/splitbrain/dokuwiki/issues for new bugs
   - prepare [[:changes]] summary
   - update release name and changes summary on [[devel:releases]]