--===============1769161697== Content-Type: multipart/signed; boundary="nextPart2315299.txX1HqvJkC"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart2315299.txX1HqvJkC Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 09 April 2008 14:31:04 Tom Albers wrote: > At Tuesday 08 April 2008 19:24, you wrote: > > 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. =A0If 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 > > shouldn't be released then. > > That means you will not get updated translations. > =A0 > > > It will probably either help getting authors to do at least the most > > basic (!) step of a change and release management or get your proposal > > reconsidered. > > True. So if we consider the last release, nobody updated the version numb= er > iirc, so that would have meant that there would have been only a tarball > for gopher. > > Is that the consensus? Sounds silly to me. > Anyone from the extragear applications want to comment at all, or isn't it > important to you? If so, we better move on, I have other things to do then > creating unwanted tarballs ;-) So why do we create tarballs at all? We want to make it easy to ship those= =20 extragear applications that don't care about their own releases. We do ship= =20 them with updated translations (at least) and bugfixes in the ideal case. The question remains: Who updates the version number? Maybe we can add some= =20 SVN revision string to the version automatically? Or the date ... ? =2D-=20 sebas http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9=20 --nextPart2315299.txX1HqvJkC Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUAR/y+LWdNh9WRGQ75AQIRTggAppUo8Z4YruVpIfa4Vk5yr6inRO9dc7fK 1LINqwytUUNKUF9sPS2YxE5WJAj7zD1hwr8aT3U7hMtR8dY9lHGfM5rFaz8VB9R9 9aKYmLo/Q6cLjK8qghrlq0J+/t5gSMdZyRMP8CvYHFfiKK5yLuVRku03kpzU8DFK k1nq9l5KzqvoqjTNyHtKvxhk+xg0N9u8w0pb2+c4ed70rJJ8td3ShJNzHZO+SYQY BmIPXcpRo22pz9/EdYK9+jdqEChJcx3pq6Grw+cbGwbxMetwoKx9E7vQQQfs3l5Z G9Py2E8cnSzQOZ9w/BlZdM0aqeDNAKb66dz0L3/vhab0tn3S2MCXmg== =uj8L -----END PGP SIGNATURE----- --nextPart2315299.txX1HqvJkC-- --===============1769161697== 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 --===============1769161697==--