This is a Request for Comments about the Release Policy of eZ Publish Community Project. Details on the Board's blog : http://share.ez.no/blogs/community-project-board

1. eZ Publish
Community
Project Board
RFC : Release policy
http://share.ez.no/blogs/community-project-board
Feb 23rd, 2011
1

2. Hello World
The Board members
Robin Andrew
Muilwijk Duck
h"p://share.ez.no/community/profile/10838 h"p://share.ez.no/community/profile/10567
Gaetano Ole Marius
Giunta Smestad
h"p://share.ez.no/community/profile/11248 h"p://share.ez.no/community/profile/9710
Gilles Nicolas
Guirand Pastorino
h"p://share.ez.no/community/profile/90262 h"p://share.ez.no/community/profile/9804
eZ Publish Community Project Board 2

3. RFC
Release Policy of the eZ Publish Community Project

4. Request For Comments
http://en.wikipedia.org/wiki/Request_for_Comments
The Community Project Board is sharing its view on a specific topic,
related to eZ Publish Community Project (eZ CP). This open process
is meant to gather feedback from all of you, and lead to the most
satisfying decision. An RFC also is informational, and based on a
preliminary work by the Board.
This is an occasion to get involved in decisions, by sharing your
arguments, appreciation and views.
Comments under this post are a good way to do so. Should you prefer
a private channel, please use the following email : community@ez.no
eZ Publish Community Project Board 4

5. The subject

6. The subject : Release policy
For eZ Publish Community Project
How can this support an increasing innovation level ?
How do we preserve full migration-ability between eZ CP and Enterprise
Edition ?
How do we make sure it does not add barriers to participation ?
How often should eZ CP be released ?
How can it smoothly work together with the existing heartbeat (releases
every 6 months for Enterprise Edition) ?
How do we keep management load low (merges, branchings, etc) ?
eZ Publish Community Project Board 6

7. Proposed
solution

8. Proposed solution - Release policy
For eZ Publish Community Project
(Details on the next slide)
eZ Publish Community Project Board 8

9. Proposed solution - Release policy
For eZ Publish Community Project
Both eZ Community and eZ Engineering are working on the same, single repository for the
kernel, on http://github.com/ezsystems/ezpublish (details on participation provided separately).
During the 4 first months of the cycle, development is done on the main and only branch :
“master”.
During the last 2 months of the heartbeat cycle, when Quality Assurance (QA) happens,
development of medium-scope features is done in the “Innovation branch”. Bug-fixes will be
accepted in the master (where QA will take place). Discrimination between bug-fixes and
features will be done by the Board, if any doubt. The content of this “Innovation branch” will be
merged back to “master” after the release (ex : 4.6 CP0, matching the Enterprise Edition
release’s kernel).
Any large feature (ex: replacing the template engine) will occasion a separate feature-branch,
and must be approved by the Board.
Intermediate releases (4.5 CP1, 4.5 CP2) are envisaged, every two months.
eZ Publish Community Project Board 9

10. Take-away slide
This is a Request for Comments about the Release Policy of
eZ Publish Community Project. Only the necessary aspects
to kickstart participation are focused on here. More details shall
be discussed later, following the same open process.
Please share your feedback on the proposed solution as posts
under this slide, or privately to community@ez.no. We will
gladly hear your ideas, arguments, impressions.
Thanks !
eZ Publish Community Project Board 10