Giacomo Pati wrote:
>
> Quoting Carsten Ziegeler <[EMAIL PROTECTED]>:
>
> > Giacomo Pati wrote:
> > >
> > > On Mon, 17 Dec 2001, Carsten Ziegeler wrote:
> > >
> > > > Hi Team,
> > > >
> > > > I think it's time to think of a new release which should be
> > > > a maintainance release. We have fixed some bugs, cleaned up
> > > > parts of the docs etc.
> > > >
> > > > Now, what else should be done? I see currently two points:
> > > >
> > > > a) The changing of the directory structure according to the
> > proposal.
> > > >
> > > > b) "Forgetting the 2.0 branch" to maintain only one CVS version.
> > This
> > > >    requires to move all experimental stuff into the scratchpad area.
> > > >    We have to be sure to be compatible with 2.0!
> > > >
> > > > So what do you think about it? Perhaps a volunteer for a)?
> > >
> > > I can do a) in the HEAD (I don't think we should do it in 2.0 branch)
> > >
> > Great!
> > I agree with you here, but we should then make a 2.0.1 release from
> > the HEAD. So then we really do not need to worry about the 2.0 branch
> > anymore.
>
> As we have applied all the patches *also* to the 2.0 branch we
> can (for a 2.0.1
> release) build it from there and stick with HEAD afterwards (no
> more synching)
>
Hm, no I think that we then have the same situation as now. The HEAD and
the 2.0 branch differ in some points. Sooner or later we have to decide
what of the new functions in the HEAD should be in the next release
of Cocoon.
So I think we should move everything which is additional to the 2.0 branch
in the scratchpad area. There might be exceptions for this rule.
We can then directly make a 2.0.1 version from the HEAD and afterwards
move that parts from the scratchpad area back to the src which are
finished.

If we first would do a 2.0.1 from the 2.0 branch, we still need to move
some parts of the HEAD in the scratchpad area.

I feel that making a 2.0.1 from a "cleanup" HEAD is a little bit less work.

Carsten


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to