KDevelop 4.0 Release

[Andreas Pakulat]

On 09.09.08 17:34:28, Hamish Rodda wrote:
> On Monday 08 September 2008 04:58:49 Andreas Pakulat wrote:
> > Hi,
> >
> > yes its that time of the year again, while KDE 4.1 has "just" been
> > released that Release team decided that a KDE 4.2 release happening
> > earlier would be good (reasoning is to release KDE 4.3 earlier so it
> > happens before akademy next year). Details on the release plans can be
> > found here:
> >
> > http://techbase.kde.org/Schedules/KDE4/4.2_Release_Schedule
> > http://techbase.kde.org/Schedules/KDE4/4.3_Release_Schedule
> >
> > If you look at the 4.2 plan closely you'll notice that it gives us not
> > even 2 months of feature-development (provided that we put all our stuff
> > into the feature plan before that).
> >
> > The question I have is: Do we feel we can make that for our 4.0 release,
> > without having to tell everybody that "yeah, 4.0 is kind of an
> > early-adopters release, so expect a lot of bugs and missing features".
> 
> I think we can make a reasonable go of it.  I don't think it will be 
> everything that kdevelop 3.x is, because we're still a way off that, but I 
> don't think it has to be either.

If we look again at the schedule, we'll see that release-team was talked
into reverting their change. So this is the original 4.2 schedule laid
out before the 4.1 release. We have time basically until November 17th
to finish all features - or remove/disable them from/in the source.

> In terms of stability, we have the extra time after the feature freeze to get 
> that right, and we're doing pretty well as it is (afaik there are no more 
> editor crash bugs remaining, just possibly some minor misbehaviours).

I agree.

> Of course we wouldn't guarantee API compatibility with this release, so we'd 
> probably do well to call the platform a 0.1 release, so we can release 
> kdevplatform 1.0 when we feel the api is ready.

We currently use 1.0, but we don't make any promises re BC. I can change
that to 0.x but we should decide on that sooner rather than later as it
can cause a small hickup (people might need to remove all kdevplatform
libs and clean their builddirs).

I don't have a strong opinion either way here.

To conclude: With the original 4.2 schedule we might be able to pull a
4.0 release, so I'd like to try to do that. First thing to do for that
is look at the feature plan page we have and adjust that as needed.
Check what of the stuff is already working, what might be possible to
push into 4.1 without causing our users to scream :)

Then we can follow the release cycle and when we see that important
parts won't be ready before Nov. 17th I'll just let the release team
know they need to leave out kdevelop of the rest of the cycle or
coordinate releasing a KDevelop4 Beta1 with KDE 4.2..

Andreas

-- 
You will be divorced within a year.