• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
RFC - Release policy - eZ Publish Community Project Board
 

RFC - Release policy - eZ Publish Community Project Board

on

  • 2,394 views

This is a Request for Comments about the Release Policy of eZ Publish Community Project.

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

Statistics

Views

Total Views
2,394
Views on SlideShare
1,972
Embed Views
422

Actions

Likes
0
Downloads
6
Comments
0

5 Embeds 422

http://share.ez.no 413
http://www.planet-ezpublish.fr 5
http://www.linkedin.com 2
http://static.slidesharecdn.com 1
http://www.gandbox.fr 1

Accessibility

Categories

Upload Details

Uploaded via as Apple Keynote

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

RFC - Release policy - eZ Publish Community Project Board RFC - Release policy - eZ Publish Community Project Board Presentation Transcript

  • eZ Publish Community Project Board RFC : Release policyhttp://share.ez.no/blogs/community-project-boardFeb 23rd, 2011 1
  • Hello WorldThe 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/9804eZ Publish Community Project Board 2
  • RFCRelease Policy of the eZ Publish Community Project
  • Request For Commentshttp://en.wikipedia.org/wiki/Request_for_CommentsThe Community Project Board is sharing its view on a specific topic,related to eZ Publish Community Project (eZ CP). This open processis meant to gather feedback from all of you, and lead to the mostsatisfying decision. An RFC also is informational, and based on apreliminary work by the Board.This is an occasion to get involved in decisions, by sharing yourarguments, appreciation and views.Comments under this post are a good way to do so. Should you prefera private channel, please use the following email : community@ez.noeZ Publish Community Project Board 4
  • The subject
  • The subject : Release policyFor eZ Publish Community ProjectHow can this support an increasing innovation level ?How do we preserve full migration-ability between eZ CP and EnterpriseEdition ?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 (releasesevery 6 months for Enterprise Edition) ?How do we keep management load low (merges, branchings, etc) ?eZ Publish Community Project Board 6
  • Proposed solution
  • Proposed solution - Release policy For eZ Publish Community Project(Details on the next slide)eZ Publish Community Project Board 8
  • Proposed solution - Release policyFor eZ Publish Community ProjectBoth eZ Community and eZ Engineering are working on the same, single repository for thekernel, 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 beaccepted in the master (where QA will take place). Discrimination between bug-fixes andfeatures will be done by the Board, if any doubt. The content of this “Innovation branch” will bemerged back to “master” after the release (ex : 4.6 CP0, matching the Enterprise Editionrelease’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
  • Take-away slideThis is a Request for Comments about the Release Policy ofeZ Publish Community Project. Only the necessary aspectsto kickstart participation are focused on here. More details shallbe discussed later, following the same open process.Please share your feedback on the proposed solution as postsunder this slide, or privately to community@ez.no. We willgladly hear your ideas, arguments, impressions.Thanks !eZ Publish Community Project Board 10