Re: release branch created (was: Plans for branching for the release)

[Tatsuro MATSUOKA]

Hello

Thank you for your reply.  

> But again, I ask that no one commit changes to the release branch in
> the archive on savannah.  If you think there is a changeset that
> should be transplanted from the default branch, then let me know.

I see.

I would like to use it for checking and for temporal binary snapshot making.

Regards

Tatsuro


--- "John W. Eaton" wrote:

> On 28-Jan-2011, Tatsuro MATSUOKA wrote:
> 
> | Can I access to Branch for 3.4 via the Mercurial ?
> 
> Yes, by doing
> 
>   hg update release-3-4-x
> 
> Also
> 
>   hg branches
> 
> shows you which branches are available and
> 
>   hg branch
> 
> shows you which one you are on.
> 
> But again, I ask that no one commit changes to the release branch in
> the archive on savannah.  If you think there is a changeset that
> should be transplanted from the default branch, then let me know.
> 
> As of now, I plan to transplant all the changesets from the default
> branch to the release-3-4-x branch since as far as I can tell, they
> have all been bug or documentation fixes that should be applied before
> the release.  So we will have some initial duplication on the branch.
> If I could just move the branch point without causing trouble, I
> would.  But I don't think I can do it anyway without direct access to
> the archive on savannah.  In any case, a small amount of duplication
> won't really hurt anything.
> 
> Finally, since the default branch is currently more up to date than
> the release-3-4-x branch, and I'm planning to transplant all of the
> changset up to now, you might as well just work with the default branch.
> 
> jwe
> 


--------------------------------------
Get the new Internet Explorer 8 optimized for Yahoo! JAPAN
http://pr.mail.yahoo.co.jp/ie8/