openerp-doc team mailing list archive
-
openerp-doc team
-
Mailing list archive
-
Message #00156
Re: Merging documentation changes from 5.0 to 6.0
-
To:
Don Kirkby <donkirkby@xxxxxxxxx>
-
From:
Olivier Dony <odo@xxxxxxxxxxx>
-
Date:
Fri, 18 Feb 2011 10:39:40 +0100
-
Cc:
openerp-doc@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<AANLkTimBs5hKR4NA_9aSkHS46n=vu9fHj=+eGbthSN=b@mail.gmail.com>
-
Organization:
OpenERP s.a.
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.13) Gecko/20101208 Thunderbird/3.1.7
Le 17/02/11 19:11, Don Kirkby a écrit :
> Any plans for ongoing merges from 5.0 to 6.0 documentation branches?
Not really, though in most cases it will make sense to merge the changes
indeed.
BTW, the branch organization is a bit strange at the moment (since 5.0
used to be the trunk, while 6.0 was not). I propose to stick with 5.0
and 6.0 only, to avoid having another merge step between 6.0 and a trunk
branch.
Then when it becomes useful to write doc for 6.1, we can duplicate 6.0
and rename one of them to "trunk".
> Unless I hear different, I'll make changes in 5.0 and then immediately
> merge them into 6.0 (assuming the changes apply to the 5.0 version and
> are significant). I think with minor things like typos and formatting
> tweaks, I'll just apply them directly to 6.0 and let 5.0 begin to fall
> behind.
Sounds good to me, hopefully merging 5.0 into 6.0 should work without to
much fuss and conflicts most of the time.
For minor changes you can also merge them normally, but if you simply
apply them on both branch it should not cause problems for later merges,
as bzr will not conflict on exactly identical lines, even if changed in
parallel.