[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 1:49:16
[Download RAW message or body]

On Sunday September 23, 2001 06:38, Cristian Tibirna wrote:
> On Sunday 23 September 2001 19:52, Charles Samuels wrote:
> > On Sunday, Neil Stevens wrote:
> > > On Sunday September 23, 2001 02:31, Charles Samuels wrote:
> > > > I think in programs like Noatun (and Kate?), no commits of plugins
> > > > need to be made.  Just keep them locally and release them
> > > > yourself.  IMO, another Noatun 1.x release is a bad idea,
> > > > especially when it's not part of a larger release.
> > >
> > > So what's the point of having a CVS?  Is it a glorified FTP
> > > repository?
> >
> > You're free to make a branch, it'l just never be part of an actual KDE
> > release.  You'll have to put out your own tarballs.
>
> Well, this is a little bit too radical. Never say never.
>
> Anyways, all this discussion was already purported many times. It is
> visible that the rather strict policy of developing KDE as an integrated
> environment is a hinder for some of the applications involved.

Do we let KDE 2.x development live on in some branch, or do we lop its 
head off, as a warning to any who might consider developing in CVS in the 
future?

> So, perhaps the discussion should go in the direction of finding
> solutions for CVS modularisation, collective CVS administration, more
> advanced CVS packaging tools (starting from the already very good
> kdesdk/scripts/cvs2pack) and so on.

Yes.

-- 
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]