| |
@@ -0,0 +1,43 @@
|
| |
+ :experimental:
|
| |
+ :toc:
|
| |
+ = Time Tables
|
| |
+
|
| |
+ This document aims at recording the different deadlines that the CPE team
|
| |
+ tries to aim for in its planning.
|
| |
+
|
| |
+ NOTE: Please be aware that all initiatives briefed in will be reviewed by
|
| |
+ our review team which includes: CPE members (manager, project owner,
|
| |
+ technical leads and agile practitioner), Fedora Representative,
|
| |
+ CentOS Representative, who will make a decision to accept this work,
|
| |
+ or decline due to unavailability of time/people, etc.
|
| |
+ All accepted initiatives will be added to our
|
| |
+ link:https://tree.taiga.io/project/amoloney1-cpe-team-projects/kanban?epic=null[backlog]
|
| |
+
|
| |
+ == Current
|
| |
+
|
| |
+ * 2020
|
| |
+
|
| |
+ ** Q2: April to June
|
| |
+ *** Q2 deadline for proposal submission: March 9th
|
| |
+ *** Q2 planning session: March 18th
|
| |
+
|
| |
+ ** Q3: July to September
|
| |
+ *** Q3 deadline for proposal submission: June 9th
|
| |
+ *** Q3 planning session: June 18th
|
| |
+
|
| |
+ ** Q4: October to December
|
| |
+ *** Q4 deadline for proposal submission: September 9th
|
| |
+ *** Q4 planning session: September 18th
|
| |
+
|
| |
+
|
| |
+ IMPORTANT: The closer to the proposal submission deadline we get the less
|
| |
+ time proposals will have to be properly scoped which may result in the
|
| |
+ proposal not being considered or picked for the next quarter. The
|
| |
+ more time a proposal has, the more time it gives us to understand and
|
| |
+ scope it.
|
| |
+
|
| |
+
|
| |
+ == Past
|
| |
+ * 2020
|
| |
+
|
| |
+ ** Q1: January to March
|
| |
Signed-off-by: Pierre-Yves Chibon pingou@pingoured.fr