Platform split

[Matt Rogers]

On Tue, May 02, 2006 at 10:01:46PM +0300, Andras Mantia wrote:
> On Monday 01 May 2006 22:03, Alexander Dymo wrote:
> > On Sunday 30 April 2006 06:02, Matt Rogers wrote:
> > > also, the platform module will depend on snapshot like everything
> > > else. :)
> >
> > I'd not do that. Really, what is the difference between trunk and
> > snapshot? IMHO one - we will be forced to wait for kdelibs changes
> > and fixes two weeks. That's not right.
> 
> The question: do you alway need the changes from trunk asap? Is KDevelop 
> progressin really that fast and you have enough power to not want help 
> from others, who port the whole KDE tree to the latest snapshot (the 
> most active being Laurent Montel)? 
> 

We do when we ask for them. :)

> > Worry about possible breakages by changes in kdelibs? 
> 
> The real problem is that kdewebdev now requires partly snapshot and 
> partly trunk and I cannot decide to follow either one. ;-) 
> 
> > Yes, that's 
> > annoying. But in fact every two weeks (new kdelibs snapshot) we will
> > be faced to the major breakage inside our code. I'd prefer to fix
> > stuff incrementally and not dig in the kdelibs commit logs to know
> > what was changed back in the time.
> 
> I can understand partly this, but I think you are wrong. The most 
> important changes (like KIO:Job -> KJob) are tracked by some developers 
> and they will fix it "for free". And you know for 2 weeks that you can 
> work on functionality and not fixing compilation bugs. I think the best 
> would be a 1 week syncing of snapshot, to not wait too long, but have a 
> realtively stable base.
> 

I agree with the one week syncing. Perhaps we should propose this on
kde-core-devel?

> > Neither KDevelop nor KDevPlatfrom (and nor Quanta) are stable. Let's
> > spend a bit more time at kdelibs tracking now and let's not slow down
> > development.
> Sincerely here I don't agree with you, but with Jens. Trying to fix 
> compilation error in software that I don't care right now (like the 
> codeview or whatever part), is more annoying than waiting for some new 
> feature 2 weeks (and of course it is usually not two weeks, as that 
> would mean introduction of the feature right after the snapshot is 
> updated).
> 
> Andras

I'm riding the fence a little bit here. I don't want to slow down
development, but at the same time, we need something we can develop
against w/o worrying about fixing compilation errors and things like
that.

We'll make a switch to snapshot starting next week and see how it goes.
Features we need from kdelibs trunk can be backported to snapshot if
needed. We'll see how it works out and go from there, although i don't
anticipate any problems.
--
Matt