Participate on the Tracker, through GIT, how?

Sunday 27 February 2011 10:56:23 am

Hi,

Anyone from Engineering that can give me an idea on how a community members could participate on the issue tracker through GIT.

For example; he/she spots an issue, and got a possible fix for it. Does he/she fork on GIT, and create separate branches for each issue, then apply the fix, and do a pull request? So one branch and pull request for a single issue? Or is this done in another way?

Thanks Robin

Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.

LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk

Monday 28 February 2011 1:50:42 am

This is defined in the GIT article as previewed here:

https://docs.google.com/a/ez.no/document/d/1Xm2NIznsHS1n64aEOG1lrj4nz6souZ4Mi4guPJoNr48/edit?hl=en&authkey=CKbN594J#

"A topic branch is a branch specifically created for an issue or a collection of related issues, or even a new feature. From a SVN background this might sound crazy. But with GIT, branching is cheap and makes the whole process simpler, retains history and allows online reviews on github."

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Wednesday 02 March 2011 11:23:49 am

Thanks for the feedback all! Also re-read the GIT tutorial (how could I forget about that one?), and it's all clear. Branches seems very easy, and clean indeed.

Thanks, Robin

Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.

LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk