Best practice for versioning eZP v. 3.x and 4.x extensions

Author Message

Eirik Alfstad Johansen

Wednesday 22 October 2008 12:08:53 am

Hi,

What's the best practice for handling different branches of an extension for the 3rd and 4th generation of eZ Publish, while still maintaining the ability to commit new functionality to both branches?

We use Subversion for version control, and I've looked into branches (copies) which seem to be the thing we need, but I wonder how others are doing this with regards to specificis like repository structure, merging workflow, and so on.

Thanks in advance !

Sincerely,

Eirik Alfstad Johansen
http://www.netmaking.no/

Björn Dieding@xrow.de

Wednesday 22 October 2008 5:09:35 am

HI I do it like this

stable/1.0/ <- ez3 version
stable/1.1/ <- ez3 version
stable/2.0/ <- ez4 version
stable/2.1/ <- ez4 version
trunk/ <- latest

Looking for a new job? http://www.xrow.com/xrow-GmbH/Jobs
Looking for hosting? http://hostingezpublish.com
-----------------------------------------------------------------------------
GMT +01:00 Hannover, Germany
Web: http://www.xrow.com/

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.