1

eZ Publish Community Project BoardRelease policy

http://share.ez.no/blogs/community-project-boardJune 01, 2011

for eZ Publish Community Project

eZ Publish Community Project Board

The eZ Publish Community Project Board

2

h"p://share.ez.no/p/10838

RobinMuilwijk

AndrewDuck

h"p://share.ez.no/p/10567h"p://share.ez.no/p/9710

Ole MariusSmestad

h"p://share.ez.no/p/9804

NicolasPastorino

h"p://share.ez.no/p/90262

GillesGuirand

h"p://share.ez.no/p/11248

Gaetano Giunta

eZ Publish Community Project Board

Open process, continuous improvement

The Community Project Board had proposed a Release Policy for eZ Publish Community Project. This went through a RFC, on which feedback was collected : http://bit.ly/ezcp-rfc. The version of the Release policy presented here incorporates the feedback received.

Improvement has to be a continuous process, baked in openness & transparency, so will feedback collection be. The version presented here is not meant to be written in stone in a definitive fashion : it should adapt to the new needs, constraints that we discover whilst using and participating to the eZ Publish Community Project. Please continue sharing, exchanging your thoughts : • http://share.ez.no/p/111598 (“Direct contact”)• http://share.ez.no/blogs/community-project-board

3

eZ Publish Community Project Board

The Release Policy answers these questions

How can an increasing innovation level be supported ?

How is full migration-ability between eZ CP and Enterprise Edition preserved ?

How do we make sure it does not add barriers to participation ?

How often should eZ Community Project be released ?

How can this Release Policy smoothly work together with the existing heartbeat (releases every 6 months for Enterprise Edition) ?

How can the management load be kept low (merges, branchings, etc) ?

4

Final policy

eZ Publish Community Project Board

Proposed solution - Release policy

6

For eZ Publish Community Project

(Details on the next slide)

eZ Publish Community Project Board

Proposed solution - Release policy

Working togetherBoth eZ Community and eZ Engineering are working on the same, single repository for the kernel, on http://github.com/ezsystems/ezpublish.

Development is always done on the master branch (note : your pull-requests may come from a dedicated branch in your fork. This is recommended).

During the last two months of the heartbeat cycle (the 6 months long Enterprise Edition development cycle), certification and stabilization is done in a branch dedicated to this purpose. The benefit is that development can continue undisturbed on the master branch.

Any large feature (e.g.: replacing the template engine) will warrant a separate feature-branch, and must be approved by the Board.

The community board is responsible for overseeing that builds are done in a manner and frequency as desired. The board can delegate this duty to a “deputy” or task force.

Build schemeMonthly builds will be proposed every month.

Nightly builds will be proposed in a near future, purely for testing purposes. This naturally implies a variable stability & reliability level.

7

For eZ Publish Community Project

eZ Publish Community Project Board

Proposed solution - Release policy

Naming schemeThe monthly builds names will follow this <yyyy>.<m> naming scheme. As an example, the build released in May 2011 was named 2011.5.

Version matching with Enterprise EditionA version map between eZ Publish Community Project and Enterprise Edition will be provided and updated upon every eZ Publish CP build. This will help you keep flexibility in migrating from one to another by guiding your CP version choice when starting a new project.

DocumentationThe documentation for every build should at least contain :• A change-log, listing all fixed bugs and implemented enhancements,• Upgrade documentation, from the previous version to the new one,• Release notes (further incorporated in the documentation on doc.ez.no) about the new features or

changes to existing ones.

8

For eZ Publish Community Project

eZ Publish Community Project Board

Proposed solution - Release policy

Guidance on participationPractical guidelines, How-tos and Resources are provided here http://share.ez.no/about/get-involved/develop including : • A tutorial on how to use Git/Github :

http://share.ez.no/learn/ez-publish/how-to-contribute-to-ez-publish-using-git• Coding standards

(under public review :http://share.ez.no/blogs/bertrand-dunogier/the-ez-coding-standards-need-you)• Guidance on bug reporting• Guidance on feature proposal (ongoing)• Description of the ideal content of a pull-request (ongoing)

9

For eZ Publish Community Project