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

List:       kde-core-devel
Subject:    Re: Upcoming 2.2 release schedule, bickering and bugs
From:       Harri Porten <porten () trolltech ! com>
Date:       2001-06-21 10:09:38
[Download RAW message or body]

On Thu, 21 Jun 2001, George Staikos wrote:

> I'm not promoting adding any new features.  Just 
> cleaning up what we have... tying up loose ends...  finishing incomplete code.
> 
[.....]
>    Finally, on a related note pertaining to the future, I think we should 
> start making more detailed release plans including target feature lists.  I 
> know that many [perhaps most] features develop closer to the middle or end of 
> the development schedule, but I think it would help give us a better picture 
> of where each release is going and what should be focussed on.  People who 
> work on various components always have ideas on where things should go and 
> can at least give some input on what should be targetted for an upcoming 
> release.

I know everybody is working very hard but I have one comment: Waldo has
posted the release schedule a loooong time ago. Many developers (including
me) have tried to adjust to that (including the inevitable small delays)
by making realistic goals in terms of planned features. Now, some other
parts of the project are lagging behind and the respective maintainers ask
for further delays. Technical or spare-time problems ?
Misjudgement of the required amount of work ? Unrealistic target, i.e. too
many features at once ? I don't know. Certainly different in each case.
But until we have some mechanism for feature plans (your proposal above) I
urge every developer to a) set himself realistic goals (safe side
calculation, there *will* be another release) and b) speak up in time when
things get out of control.

The fact that we lost some code and maintainers is an unforseeable
incident that might require special actions, of course.

Harri.

P.S. I would like to see 2.2 go out of the door as fast as possible. It
contains many improvements already that users should benefit from instead
of reporting long fixed bugs.

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