[fdo-internals] FDO SVN Branches

[Greg Boone]

Please note that there is no need to actively work against the 3.3.0 tag. 3.3.0 is a published (tagged) release only and is closed. All development will now take place either in the 3.3 branch or in the trunk. Any subsequent point release of FDO in the 3.3.x stream will be built off the 3.3 branch.

Greg

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Friday, March 14, 2008 9:46 AM
To: Robert Fortin
Cc: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO SVN Branches

FYI

From: Greg Boone
Sent: Friday, March 14, 2008 9:42 AM
To: Robert Fortin
Subject: RE: [fdo-internals] FDO SVN Branches

They can switch their current branches to the new ones using the 'svn switch' command

http://svnbook.red-bean.com/en/1.1/re27.html

They need to switch from Branch 3.3.1 to branch 3.3.

Greg

From: Robert Fortin
Sent: Friday, March 14, 2008 9:09 AM
To: Greg Boone
Subject: RE: [fdo-internals] FDO SVN Branches

Greg,

How should developer proceed with these new branches?
Do they need to get rid of what they have and resync with the new branches?

RF

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Thursday, March 13, 2008 1:15 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO SVN Branches

Ok.. The branch changes have been made.


1)      Branches/3.3.1 renamed to Branches/3.3

2)      Branches/3.3.0 renamed to Tags/3.3.0

Please avoid committing changes to Branches/3.3 until FDO 3.3.1 is released. Once that is done all necessary changes can be ported to Branches/3.3 on a "as-needed" basis.

Greg

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, March 12, 2008 6:03 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO SVN Branches

I think I would prefer to move away from the .x notation.  My personal take is that leaving this off makes the "branchiness" more explicit.


From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Wednesday, March 12, 2008 14:29
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO SVN Branches

One update...

If we want to follow the 3.2.x process and the MapGuide development process, the branch name should be  3.3.x

Greg

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Jason Birch
Sent: Wednesday, March 12, 2008 4:20 PM
To: FDO Internals Mail List
Subject: RE: [fdo-internals] FDO SVN Branches

Sounds good to me.

From: fdo-internals-bounces at lists.osgeo.org [mailto:fdo-internals-bounces at lists.osgeo.org] On Behalf Of Greg Boone
Sent: Wednesday, March 12, 2008 13:06
To: FDO Internals Mail List
Subject: [fdo-internals] FDO SVN Branches

Hi All,

After taking to the FDO PSC today, a request has arisen to restructure the FDO Braches in SVN for easier maintenance and ongoing support.

Here is the plan that was proposed:


1)      Create a general 3.3 branch that will be the basis for all future development for future 3.3.x releases

2)      Move the code in the existing 3.3.1 branch to the newly created 3.3 branch

3)      Make the 3.3.0 branch a tag'ed build rather than a branch

4)      When 3.3.1 is released, make 3.3.1 a tag as well

5)      Submissions to the 3.3 branch will be limited to priority defects until 3.3.1 is released

6)      Code submitted to the trunk will be ported to the 3.3 branch on a as-needed basis once 3.3.1 is released

NOTE: A tag or a branch in SVN is not a full copy of the source code. Tagged code can be moved to branches or branched code moved to tags quite easily.

Thoughts?

Greg

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/fdo-internals/attachments/20080314/bba2767c/attachment.html