1.6/2.0 release schedule request

Christian Stimming stimming@tuhh.de
Sun, 1 Apr 2001 10:23:27 -0700


-----BEGIN PGP SIGNED MESSAGE-----

The current CVS offers quite a bunch of cool new features, and it seems 
the number is growing big enough to justify a new major release soon. 

Recently I posted an article on IRC, "Why KDE works", written by 
well-known Telsa, http://www.linux.org.uk/~telsa/Trips/Talks/lca-kde.html 
and upon other things the article emphasizes the importance of a 
release schedule: "Schedules: not a popular word in free software. But you 
need them in big projects. The KDE I release was painful enough that now 
they have a release guy whose job is to flame any developer who keeps 
changing things after dates. So now, 2.1 has passed feature freeze, passed 
string freeze, then it's bug-fixing, then the "four eyes principle": any 
change, any at all, must be looked at by four eyes before hitting CVS. "

I would like to ask Dave and/or Bill to set up a release schedule for a 
new stable release. IMHO it is realistic to schedule a feature freeze for 
mid-May.

BTW I think we would have had enough features to justify a 1.6 release 
already some weeks ago: New file format, new reporting infrastructure, QIF 
import, Guppi integration, to name a few, would have totally justified a 
stable release called 1.6. We could have postponed more features to a 
later release, e.g. pricedb, configurable main window, compiled scheme 
etc. Now we are going to change quite a lot of things in one batch. Maybe 
this in turn justifies the version number 2.0 for the upcoming release.

Why do I ask for this? Because I finally want to have a stable version to 
work with which has all those nifty reports that I contributed over the 
last 6 months. And because I like GnuCash.

Christian
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)

iQCVAwUBOsdkD2XAi+BfhivFAQHyxwQAqcinVeCmZXiMCivRUA9gN0mYV9L2QXws
IfwmZf2PK0ooEFCGHAdht/ue0B2JW7Sfpno16Ei3BbF22ky1k0K6V95KBZiIsQYe
0/nDM5JR6l20jiaZugUiAJBrYp8eDl47XTzFJmrlLPQYobSOq0Wp8KSXvjgZZ/NN
Dl7QKO/QbV4=
=/YUt
-----END PGP SIGNATURE-----