Changes between Initial Version and Version 1 of ReleaseProcessDraft

Timestamp:

May 24, 2014, 8:02:21 PM (10 years ago)

Author:

Yves

Comment:

First draft of a page that could be used to better organize the process of release new alpha versions.

ReleaseProcessDraft

@@ +1 @@
+= Standard schedule
+ 1. Day 0: Feature freeze
+ 1. Day 3: String freeze
+ 1. Day 6: Translation freeze
+ 1. Day 6: Commit freeze
+ 1. Day 7: Packaging
+ 1. Day 9: Release
+
+= Phases
+|| Name || Tasks to complete ||
+|| Development || ||
+|| Feature freeze || ||
+|| String freeze || ||
+|| Translation freeze || ||
+|| Packaging || ||
+|| Release || ||
+
+= Release progress table
+Put your name into the "Accepted by" column to take over a task and agree to completed it in time (according to the "Deadline" column).
+Update the status column regularly enough to keep team member informed. Especially note if you are waiting for input or are otherwise prevented from working on the task.
+
+Next release: Alpha 17
+|| Task shortname || Accepted by || Deadline || Status ||
+|| ReleaseProcessDraft#Startreleaseprocess || || || ||
+
+= Task descriptions = 
+
+== Start release process
+'''Description:''' [[BR]]
+The team decides that there are enough new features and that it's time to release a new alpha version. Usually in a team meeting, we decide when the regular schedule starts and if there are any differences to the predefined schedule.
+[[BR]]'''Can be completed in phase:''' Development
+[[BR]]'''Candidates:''' Whole team (usually at the meeting)
+
+== Update release progress on Trac
+Description:[[BR]]
+Remove all content from the  Release progress table and replace "Next release" with the right version number.
+[[BR]]Can be completed in phase: Development
+[[BR]]Candidates: Everyone
+