release creation

--nextPart50619431.eu0LFLnljn
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

any plans for handling creation of releases ?  we'll of course start with=20
tagging a commit in the git repo for a specific version, but is that where =
we=20
stop ?

i find such releases to be annoying for distro maintainers.  they get a tar=
ball=20
with no pregenerated files so they have to generate everything themselves.

autotools provides a way to easily create & check tarballs:
	make distcheck
now we have to host that tarball somewhere.

i don't think checking in pregenerated files is the answer as timestamps ca=
n=20
easily get skewed, and the tools one dev has on their system vs another can=
=20
vary greatly.  thus everytime someone generates autotools on their system,=
=20
they get a repo full of modified files.
=2Dmike

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

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

iQIcBAABAgAGBQJRcFXeAAoJEEFjO5/oN/WBiFQP/R3AfzUXzJSio2M+PeWnMOHr
aIVwGvOswFs2coJlph2uwYlHblFxSo810oXXP4yvGdEaUa0InNREFxb6fQwIcJ3V
564yEKrQXcdQkYju0GTjf+gP0pnXBb5fXWjuIriwfOz/E/oIG14TZxxoD9rwVkFF
bqaymYrVbM2JxMctX8lXTEnEOi2qZhqBDFsYzaNPtiAY7FdbbKZNMsAVFGaPJ8ix
CIk7e0Rh5xk9PDRWNJR8HIO9Kj2wUyvgborITzOfQwLyNNiw6eTkaG8PGNy2g/2c
K0gCoyNPiXFjAZ5XHKu4Kyy9HeRhZQrWbvAQWgyVa8VahfZinjs1T7ypEeddXZeF
o39OJaDW2AMXbLomG2RaHYWOJ6PzTLZRMYalYjWcP3Gn/Xzoe2nNHylm05/zW/ht
0Z3HAkgJqV4TCeBBDOsmZ2JNegMzk7S7rwm0uU2gWz6gFo+AKWy/zchjkwfnWeAg
tSK8QsCcqLaQrESUWhgu/euy61bog3D/8bPCNZp+zKYvmWIyj4tirtpEftlcyiKk
pT3ZMCKUYTIbx4rKXvLx2GPHlS65szSUMR9w461YG77TN9iWbgpHd5aAG7auTroN
xMLtGg6fiYex7OT1a48VaCqzhDQyuVExYdM9+h0N1ecak0l1akux8QGXX52noTeh
lHZkqpq8u0dgmvpyndNB
=FKNj
-----END PGP SIGNATURE-----

--nextPart50619431.eu0LFLnljn--