GPA-0.5 ???

[Marc Mutz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 22 March 2002 22:59, Benedikt Wildenhain wrote:
<snip>
> > > Peter> There was a deadline to meet. Keeping the CVS in sync and
> > > Peter> discussing everything on this list would have meant to miss =
it.
> >
> > I don't see why.
>
> Because discussing about certain features can consume a lot of time: I
> am currently subscribed to around five mailing lists with some traffic
> (and some ones with only few posts per month) and I need around one hou=
r
> per day to read them and write answers to some of the mails on the
> mailing lists and to private ones. And at the moment I am not really
> involved in the development of really important programs and do not use
> mails in business (I am still a pupil at a German "Gymnasium" as you
> might still now from my first post on one fsfeurope - list); it had
> probably costed Peter much more time to discuss every change of the GPA=
=2E
<snip>

Sorry to burst into the discussion as an outsider, but let me get things=20
straight here: Using CVS _does not_ mean that you have to discuss every=20
commit. Nor does it slow you down. On the contrary: It speeds you up. See=
=20
KDE's use of CVS in non-feature-freeze times:
- - You commit your changes.
- - If it's something big or something you are uncertain about, you post =
a patch=20
first.
- - While waiting for comments you are free to work on other parts.
- - If not comments arrived after a day or so, you employ the implicit "n=
o=20
comment means OK" rule and go ahead.
- - If something goes wrong after a commit, someone will complain, most o=
f the=20
time even quite shortly after the commit.

Care to explain how this slows you down? Oh, yes: you have to deal with t=
hose=20
fscking lusers who complain that your work of art has bugs. Stuff like th=
at.

Marc

- --=20
Marc Mutz <mutz@kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8m8KD3oWD+L2/6DgRAutcAKCQwgnKTNaRx3u2BDAHL/eR5t4MgQCgpQMt
piNO2JNqMVa1BAI9zot1eyY=3D
=3DYux/
-----END PGP SIGNATURE-----