[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Where to put post-2.2 development
From:       Neil Stevens <neil () qualityassistant ! com>
Date:       2001-09-24 16:58:13
[Download RAW message or body]

On Monday September 24, 2001 09:39, Thomas Zander wrote:
> On Sun, Sep 23, 2001 at 09:21:44PM -0700, Neil Stevens wrote:
> > On Sunday September 23, 2001 08:57, Waldo Bastian wrote:
> > > I suggest to use KDE_2_X_BRANCH and branch that off from the current
> > > KDE_2_2_BRANCH, but only for those applications that intend to make
> > > a release of their own.
> >
> > So if we tag admin, each app with new features, and the top level
> > files for each module with a branched app, then someone who does cvs
> > co -r KDE_2_X_BRANCH will get all at once the apps that have new
> > features since 2.2.
>
> Just the apps that intend to release, as Waldo said. So let the
> maintainer of each app decide. I.e. minimum branching ;)
> And yes, the admin/toplevel file tagging sounds logical.
>
> ps, you naturally mean 2.2.1 in your last sentence..

correct.  But 2.2.1 isn't supposed to have new features since 2.2, right? 
:-)

> for those users; (not tested)
> cd kdeSomePacakge
> cvs up -r KDE_2_2_BRANCH
> cvs tag -b KDE_2_X_BRANCH admin
> cvs tag -bl KDE_2_X_BRANCH
>
> cd myProject/
> cvs tag -b KDE_2_X_BRANCH
> cvs up -r KDE_2_X_BRANCH

thanks

-- 
Neil Stevens
neil@qualityassistant.com
"I fear all we have done is to awaken a sleeping giant and fill
him with a terrible resolve." - Yamamoto Isoroku

[prev in list] [next in list] [prev in thread] [next in thread]