From kde-panel-devel  Tue Dec 01 21:57:16 2009
From: Sebastian =?iso-8859-15?q?K=FCgler?= <sebas () kde ! org>
Date: Tue, 01 Dec 2009 21:57:16 +0000
To: kde-panel-devel
Subject: Re: Update The Feature Plan! NOW!
Message-Id: <200912012257.17308.sebas () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-panel-devel&m=125970469526411
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============2068215031=="

--===============2068215031==
Content-Type: multipart/signed;
  boundary="nextPart5542539.kgIEPWuuhE";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart5542539.kgIEPWuuhE
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable

On Tuesday 01 December 2009 22:41:55 Martin Gr=E4=DFlin wrote:
> Am Dienstag 01 Dezember 2009 20:28:43 schrieb Andreas Marschke:
> > How about something like the debian devs made they basically add a note
> > to the changelog like :
> > * corrected text file (closes #11111)
> > This works for themas well.
>=20
> And which is in no way a changelog which could be read by endusers.
>  Sometimes we just have to translate our internal tech speak to something
>  understandable by users. Just some examples from kwin:

Actually not a problem, I can "translate" KDE techspeak to something human-
readable just fine, what I cannot do is keep track of all the features that=
=20
do into our six-monthlies.

>  * compositing vs desktop effects
>  * clients vs decorations
>  * Client vs window (yes "client" can mean different things)
>=20
> If we don't give the translation we can as well keep our bad "look at the
>  svn log".

The problem with the SVN log is that it's too fine-grained, and that an=20
feature might not always match an SVN commit.

=46or bugfix releases, some CHANGELOG keyword would be useful, the XML=20
changelog is always edited by the same persons, which means that we usually=
=20
have the okular fixes, the Juk fixes, the KHTML fixes and the KMail fixes,=
=20
but hardly ever get a reasonable picture of how much actually changed.

By now, I've developed the habit of "if you don't care to write the=20
changelog, I don't care about running after your changes", so they just end=
=20
up in the release without anybody talking about.

That's for our bugfix/translation updates. What I'm talking about in this=20
thread are feature releases like 4.4
=2D-=20
sebas

 http://www.kde.org | http://vizZzion.org |  GPG Key ID: 9119 0EF9=20

--nextPart5542539.kgIEPWuuhE
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iQEcBAABAgAGBQJLFZE9AAoJEGdNh9WRGQ75eLcIAOwJtAHut9Q3q46a4S5GonOT
6ialld5bzBaHfbU4n8g89vA2iQG2vJyd//RtI6ahJ9Tby42UmM0f3AXD7jyiPFnU
nEHXT6v8Z6/StCkfSqe6aTjc9oL/VeSuXVLt0VPnvZlgVC9EMrdaP4YIhXt+GmGv
GaDdxjZ8e++Q0s3Q5p5y6bMTLiqgKtPRaN5jUqi8rZgVxVQ5FR4CwAU7pjADExxZ
KWDOQEW2wvKLo7Mgy5XkcTRGLRqh6r43j6XyaWXA2XzLwgZW8M+DvmBmdz3yDbKG
mYl55A4E0Nb/n8n9J0fZGYAOMecNmxRNVfwGRZCKheSkfkd9xHANF7bSRWlQ+nw=
=znjb
-----END PGP SIGNATURE-----

--nextPart5542539.kgIEPWuuhE--

--===============2068215031==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel

--===============2068215031==--