You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mark Phippard <ma...@softlanding.com> on 2006/03/06 18:42:10 UTC
Need to create a new branch for OS/400
As many of you are aware, we have recently committed several changes to
trunk so that Subversion can compile and run on OS/400 V5R4+. This is
different than the existing "EBCDIC" port for previous versions of OS/400.
We would like to make a branch where we can manage this version of the
port for Subversion 1.3.x as we will still have a need to produce builds
for those users. Does anyone have any objections to this? Should I just
make it under the existing ebcdic branch, or in a new namespace? I have
no preference. I will also need to make tags eventually. I guess I would
propose creating:
/branches/ebcdic/v5r4/1.3.x
There are already the following branches:
/branches/ebcdic/trunk
/branches/ebcdic/1.2.x
/branches/ebcdic/1.3.x etc..
My plan would be to copy the "normal" 1.3.x branch at HEAD. Then get it
up to date with these patches we have submitted, and finally synch it up
with any merges that happen on that branch between now and 1.3.1. We will
then do a 1.3.1 release and tag when Subversion does.
We will also continue to maintain the older ebcdic branch as before.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Need to create a new branch for OS/400
Posted by Mark Phippard <ma...@softlanding.com>.
james82@gmail.com wrote on 03/06/2006 01:59:33 PM:
> On 3/6/06, Mark Phippard <ma...@softlanding.com> wrote:
> > We would like to make a branch where we can manage this version of the
> > port for Subversion 1.3.x as we will still have a need to produce
builds
> > for those users. Does anyone have any objections to this? Should I
just
> > make it under the existing ebcdic branch, or in a new namespace? I
have
> > no preference. I will also need to make tags eventually. I guess I
would
> > propose creating:
> >
> > /branches/ebcdic/v5r4/1.3.x
>
> Let me see if I understand.
>
> This new branch will contain the EBCDIC changes which you propose for
> 1.3.x. You're creating this branch because you want to quickly cut a
> 1.3.1 release for EBCDIC without burdening the Subversion team with
> the task of reviewing all of your EBCDIC patches in time for 1.3.1.
> If, in future, your EBCDIC patches are integrated into 1.3.x, we can
> retire this branch.
I realize this can be confusing.
We have had a number of patches accepted to trunk for building Subversion
on OS/400 V5R4. Obviously none of these are going to be backported to the
1.3.x branch. However, we still need to produce working builds of
Subversion 1.3.x for users of OS/400 V5R4. We cannot use the existing
EBCDIC branch for this, because that version only works on the older
versions of OS/400.
So I need a "permanent" branch just for Subversion 1.3.x on OS/400 V5R4.
Thanks
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Need to create a new branch for OS/400
Posted by David James <dj...@collab.net>.
On 3/6/06, Mark Phippard <ma...@softlanding.com> wrote:
> We would like to make a branch where we can manage this version of the
> port for Subversion 1.3.x as we will still have a need to produce builds
> for those users. Does anyone have any objections to this? Should I just
> make it under the existing ebcdic branch, or in a new namespace? I have
> no preference. I will also need to make tags eventually. I guess I would
> propose creating:
>
> /branches/ebcdic/v5r4/1.3.x
Let me see if I understand.
This new branch will contain the EBCDIC changes which you propose for
1.3.x. You're creating this branch because you want to quickly cut a
1.3.1 release for EBCDIC without burdening the Subversion team with
the task of reviewing all of your EBCDIC patches in time for 1.3.1.
If, in future, your EBCDIC patches are integrated into 1.3.x, we can
retire this branch.
A "1.4.x" branch for v5r4 will probably not be needed because it is
likely that EBCDIC support will be in place in time for Subversion
1.4. If more patches need to be added for Subversion 1.4.1, etc., they
will likely be incremental in nature and therefore could probably be
handled using our normal backport procedures.
Did I miss anything? Feel free to go ahead and create the branch.
Cheers,
David
--
David James -- http://www.cs.toronto.edu/~james
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org