apaku at gmx.de
Fri Jul 20 12:19:44 UTC 2007
On 19.07.07 21:59:12, Matt Rogers wrote:
> On Thursday 19 July 2007 20:52, Matt Rogers wrote:
> > On Jul 19, 2007, at 5:23 PM, Roberto Raggi wrote:
> > > Il giorno 19/lug/07, alle ore 23:48, Alexander Dymo ha scritto:
> > >> Looking at commit rates for KDevelop in 2007 I wouldn't say it's a
> > >> dead project ;) But yes, it doesn't look as good. I have been
> > >> thinking
> > >
> > > I know, but I'm talking about KDE/KDevelop users that are trying/
> > > evaluating KDE 4 beta.
> > >
> > >> of using KDev4 every day for a long time to make sure its UI is any
> > >> good... but I never had enough time to start...
> > >
> > > I want to propose an alternative solution. I think part of the
> > > problem is the high commit rate in /trunk. From what I can see /trunk
> > > is very unstable and don't tell me it works for you, because it
> > > doesn't and it is two years that kdev4 does not work :-) So, my
> > > proposal. For one month you don't develop your feature-X in trunk,
> > > but you do it in /branches/kdevelop/whatever/feature-X then when you
> > > think that your code is good enough you ask Matt to merge the change
> > > in /trunk. If you merge only *good* changes in /trunk you will improve
> > > (by definition) the quality and the stability of KDevelop. Branching
> > > in svn is easy and cheep, merging is a different story (more tricky),
> > > but that's OK because you don't have to do it, Matt (as maintainer)
> > > will do it for you ;-) if you don't like svn you can maintain your
> > > branch using git or mercurial.
> btw, if we do decide to go with this route, perhaps we should consider
> branching off from KDE's svn and using git, and perhaps participate in the
> git experimentation stuff as mentioned on kde-core-devel?
> Just an idea I had. :)
>From the thread on kde-core-devel it sounded as learning git is not
really straight forward. So I'm opposing the idea a bit, I don't want to
learn git at the moment and I don't think it should be needed just to
implement a feature for kdevelop4. If you and others however want to try
it out, I don't want to stop you, just don't "force" it on others
(sorry, can't think of a better word).
Reply hazy, ask again later.
More information about the KDevelop-devel