Vadim Gritsenko wrote:
Pier Fumagalli wrote:
In the current xml-cocoon2 cvs module there are two branches:
cocoon_20_branch and cocoon_2_0_3_branch
Which one is the current branch used for 2.0 (I suspect 2_0_3)...
You suspect correctly.
cocoon_2_0_3_branch is the "real" 2.0 branch.
If we (Well
Pier Fumagalli wrote:
In the current xml-cocoon2 cvs module there are two branches:
cocoon_20_branch and cocoon_2_0_3_branch
Which one is the current branch used for 2.0 (I suspect 2_0_3)...
You suspect correctly.
cocoon_2_0_3_branch is the "real" 2.0 branch.
Vadim
Pier
In the current xml-cocoon2 cvs module there are two branches:
cocoon_20_branch and cocoon_2_0_3_branch
Which one is the current branch used for 2.0 (I suspect 2_0_3)...
Pier
Carsten Ziegeler wrote:
> > David Crossley wrote:
> >
> > Would someone please clarify what needs to happen
> > with documentation in regard to the CVS branches.
> >
> > I have been updating some documents and adding some
> > new ones. I have been addin
> -Original Message-
> From: David Crossley [mailto:[EMAIL PROTECTED]]
> Sent: Friday, May 10, 2002 8:47 AM
> To: [EMAIL PROTECTED]
> Subject: clarification of CVS branches
>
>
> Would someone please clarify what needs to happen
> with documentation in
David Crossley wrote:
> Would someone please clarify what needs to happen
> with documentation in regard to the CVS branches.
>
> I have been updating some documents and adding some
> new ones. I have been adding this only to the HEAD of
> CVS and not into the 2.0.3 branch.
Would someone please clarify what needs to happen
with documentation in regard to the CVS branches.
I have been updating some documents and adding some
new ones. I have been adding this only to the HEAD of
CVS and not into the 2.0.3 branch.
I gather that only code bugfixes need to go into the
