diff options
authorXavi Artigas <>2018-08-29 16:15:51 +0200
committerXavi Artigas <>2018-08-29 16:15:51 +0200
commitffedc7bbd28557dae129fa2a91374db1f0c6e4f3 (patch)
parente6e87277c6538fc3f2c0a429a579894e48675130 (diff)
Release cycle descriptiondevs/xartigas/development-cycle
This is still a proposal at this time.
1 files changed, 121 insertions, 0 deletions
diff --git a/pages/contrib/devs/ b/pages/contrib/devs/
new file mode 100644
index 000000000..5ab9d5b53
--- /dev/null
+++ b/pages/contrib/devs/
@@ -0,0 +1,121 @@
1# Release Cycle #
3EFL aims at producing periodic releases of consistent quality. The goal of the release cycle described here is to produce a new release every 3 months (12 weeks), interleaving development periods with testing and bug fixing.
5## Phases
7Every release cycle is divided into the following phases:
9| Week | Phase |
10| ------- | ------------------------------------------------------------- |
11| 10-11* | [Initial Feature Tagging](#Initial_Feature_Tagging) |
12| 12* | [Initial Feature Evaluation](#Initial_Feature_Evaluation) |
13| 1-4 | [Development 1](#Development_1) |
14| 5 | [Mid-Cycle Feature Evaluation](#Mid-Cycle_Feature_Evaluation) |
15| 6-9 | [Development 2](#Development_2) |
16| 10 | [Feature Freeze](#Feature_Freeze) |
17| 11 | [Bug Fixing 1](#Bug_Fixing_1) |
18| 12 | [Bug Fixing 2](#Bug_Fixing_2) |
20> **NOTE:**
21> Weeks marked * happen during the **previous** release cycle. This is, the [Initial Feature Tagging](#Initial_Feature_Tagging) and [Initial Feature Evaluation](#Initial_Feature_Evaluation) phases for release cycle N happen during the [Feature Freeze](#Feature_Freeze) and [Bug Fixing](#Bug_Fixing_1) phases of release cycle N-1.
23### Initial Feature Tagging
24Starting in the last 3 weeks of the previous release cycle, for 2 weeks tickets with TODO priority are created (or re-tagged) with the milestone tag of the next cycle, and the ``work_proposal`` tag is appended. Major features also receive the ``major_changes`` tag.
26> For example, during the last 3 weeks of the ``1.21`` release, remaining TODO tickets are re-tagged with the ``1.22`` tag).
28### Initial Feature Evaluation
29After this period, a 1 week multi-vote is created on Phabricator to evaluate all proposals tagged with ``work_proposal``. Core developers vote to **defer** TODO tickets to a later release.
31> For example, while finishing work on ``1.21``, you have to vote for those tickets you do **NOT** think should be worked during ``1.22``).
33This aims at promoting discussion about work items, and reviewing of anything which might be too radical to accomplish within the next release cycle.
35Any TODO item which receives 5 or more votes from #committers is **deferred** to a later release cycle (That work is not merged into master during this release cycle).
37### Development 1
38Development progresses for 4 weeks as usual.
40### Mid-Cycle Feature Evaluation
41Feature development halts for 1 week (bug tickets on the "urgent" work board are handled as time allows).
43Two polls are created to re-evaluate the features currently under development:
45* A vote to review existing ``active_work_proposal``s.
47 It may be the case that unforeseen difficulties arise in development, so this creates a process by which a work item can be officially deferred.
49* A vote to review other TODO items which are not yet accepted.
51 If some items are deferred then there may be extra time available, or perhaps a proposal for implementing a feature has been reworked to make it fit into the release better.
53### Development 2
54Development progresses for 4 more weeks as usual.
56### Feature Freeze
57Only bug fixing from now on, with these exceptions:
59* Any "major" feature patches submitted before the freeze begins can still be reviewed and landed.
61* Any "major" feature patches submitted after the freeze are unconditionally deferred until the next release cycle.
63* Any "small" feature patches can be landed (with 3+ reviews and no rejects after being on Phabricator for 48+ hours).
65> An Alpha release is produced at end of this phase.
67### Bug Fixing 1
68Only bug fixing during this phase, with this exception:
70* No features of any kind may be landed unless they are "small" and are required in order to fix an urgent (high/showstopper priority) bug.
72> A Beta release is produced at end of this phase.
74### Bug Fixing 2
75Only bug fixing during this phase, with this exception:
77* No features of any kind may be landed unless they are "small" and are required in order to fix an urgent (high/showstopper priority) bug.
79**If release can be executed, release ships at the end of this phase.** Otherwise, perform pre-release and go back to the [Feature Freeze](#Feature_Freeze) phase.
81## Proposals
83If you want a feature to be added to EFL, you write a proposal ticket for it in Phabricator.
85Proposal tickets should:
87* Include a description of the work which you are planning to do.
89* If the work is complex, or the reason for it is non-obvious, explanations should be provided to justify the work.
91* Be tagged with ``efl`` (or a sub-project), ``work_proposal``, and the release cycle you want it merged into master (e.g. ``1.22``). The [Initial Feature Evaluation](#Initial_Feature_Evaluation) phase will then include your proposal in the voting.
93During the voting weeks, proposals being evaluated will be tagged ``voting`` by the release team.
95During the development weeks, proposals being worked on will be tagged ``active_work_proposal`` by the release team.
97## FAQ
99### I didn't write a proposal for work that I am planning to do, what happens now?
100Create a 'work proposal' ticket as described in the [Initial Feature Tagging](#Initial_Feature_Tagging) phase. 5 weeks from now, a second voting session will occur, and any proposals which are not rejected will become features of the next release cycle.
102### What is a proposal?
103See the [Proposals](#Proposals) section.
105### Why proposals?
106Previously, EFL releases were like a giant pile of unrelated and uncoordinated work. There was no big picture and nobody knew what anyone else was doing. This methodology provides solutions to these issues and allows for a framework within which contributors can work cooperatively on features for each release.
108### When do I need a proposal?
109If you are planning to do work which is large or requires a lot of changes, you should create a proposal. This may include things like major refactoring projects, adding features affecting multiple components, adding a feature which fundamentally changes how EFL works/runs/builds, or any other item which may be considered controversial.
111### When do I not need a proposal?
112If you are adding a trivial feature (e.g., a get method for a property) or fixing bugs, you probably do not need a proposal. If in doubt, create one anyway in order to avoid conflict.
114### What happens to already-submitted patches which implement features?
115Patches implementing features which were submitted on Phabricator prior to the 1.21 release will not require proposals and can be reviewed/accepted normally. This is a one-time acceptance to avoid creating more work for people who had completed projects prior to the current development cycle.
117### What do I do about my project for the next 5 weeks if I did not submit a proposal?
118A proposal is for merging features into the master branch, not for working on features. Features should be worked on at any time regardless of proposals, but they are not merged to the master branch and shipped in releases until a proposal for the project has been accepted.
120### So I can work on my tasks without a proposal?
121Yes, though it should be noted that reviews of the eventual proposal may require a rewrite of the implementation in order to comply with those reviews and have the feature merged. For this reason it is highly advised to either submit the proposal prior to beginning work or to expect that the existing implementation be used as an example that can be refined before being merged.