--===============1193276393==
Content-Type: multipart/signed;
  boundary="nextPart1324058.yHKJupd9iT";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1324058.yHKJupd9iT
Content-Type: text/plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Tuesday, 08. April 2008 16:19:55 Tom Albers wrote:
> > The version number needs to change, that's a basic part of release
> > management.  If it's not done by the app author it should be done by
> > the release manager or just not released at all.
> It can not be done by the release manager as that proposal from me was
> denied (see the evaluation thread on these lists a couple months back).

In that case, it's really pretty simple and as Jonathan wrote: The stuff=20
shouldn't be released then.

It will probably either help getting authors to do at least the most basic=
=20
(!) step of a change and release management or get your proposal=20
reconsidered.

=2D-=20
Best regards, Wulf

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEABECAAYFAkf7qmQACgkQnuVXRcSi+5qCVQCfY0Tn8tPpD9DKdhh0sw3l6GEH
E6EAniVztFs5HgC34AYoGlx1kMkrgU/h
=tloy
-----END PGP SIGNATURE-----

--nextPart1324058.yHKJupd9iT--

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

_______________________________________________
release-team mailing list
release-team@kde.org
https://mail.kde.org/mailman/listinfo/release-team

--===============1193276393==--