Some comments:

On Tue, 26 Sep 2000, Matthias Elter wrote:
> KDE2 v1.0 release schedule
> --------------------

s^2 v1.0^v2.0^

> Mon 02/10
>  - CVS tag KDE_2_0_RELEASE
>  - cvs is effectively read-only now
>  - the tag will be moved for _real_ show stoppers only
>  - at least two core developers have to approve a show stopper fix
>  - RC1 tarballs will be released
>
> Mon 09/10
>  - prepare KDE 2.0 final tarballs
>  - release tarballs to the packagers
>
> Fir  13/10
>  - spread source and binary packages to the mirror sites
>
> Mon 16/10
>  - announce KDE2 v1.0
>  - PARTY on irc.kde.org
>
> Yes, this means that KDE2 is going to happen finally. After some
> discussions at the meeting this weekend we came up with a rough post-KDE2
> road map:
>
> - Immediately after the KDE2 v1.0 release a KDE_2_0 branch will be created.
> Fixes to this branch will be released as KDE2 1.0.X versions soon after the
> 1.0 release. The KDE_2_0 branch is not open for feature commits.

I don't think branches are a good idea because they tend to be tested very 
poorly. It effectively splits the developers across two branches. We had that 
situation between KDE 1.1.1 and 1.1.2 and only a few (3? 4?) people did 
actually work on 1.1.2. 

I also would like to see a split up of release schedules based on packages. 
This schedule still seems to be based on "release everything together". We 
want more releases more often and this schedules doesn't reflect that.

> - The HEAD branch is open for feature commits after the 1.0 release. We
> however maintain kdelibs binary compatibility. The base applications will
> probably see the most significant improvements. We aim for incremental
> rather than revolutionary improvements this time.
>
> - February/March 2001 - KDE2 1.1 release.
>
> - March 2001 - HEAD will be moved to Qt3.0 which is scheduled for
> February/March 2001. This means that we will break kdelibs binary
> compatibility for KDE2 1.2, but this will happen anyway due to the new
> compiler ABIs.

This would also be a nice point to introduce MT _IF_ that has proven itself 
in the meantime.

> - Summer 2001 - KDE2 1.2 based on Qt3.0

I can agree with this schedule if it was for 'kdelibs' but not for _ALL OF 
KDE_. E.g. kdemultimedia can release a new version in december and kdenetwork 
can have a release in januar. The pace of development for the different 
packages is quite different and the releases should be adapted to this pace. 

Cheers,
Waldo
-- 
KDE/Linux, you make the choice.