Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 08/08/14 17:57, Chuck Short wrote:
> An issue was discovered with Keystone 2014.1.2 stable release
> tarball shortly after it was uploaded on the release page at: 
> https://launchpad.net/keystone/icehouse/2014.1.2
> 
> A new tarball corresponding to 2014.1.2 code was generated and
> uploaded: md5sum: c8a85fc2ac76679eb1b674e0c2c65e36
> keystone-2014.1.2.tar.gz sha1sum:
> c1d481d8b330e50da5ace19c23e5909c04fa1cba  keystone-2014.1.2.tar.gz
> 
> Please double-check that you got the right one.

I wonder whether it's better to handle those kind of issues with
releasing another minor release like 2014.1.2.1 for that specific
package. Modifying tarballs in place sounds similar to e.g. amending
git commit in place instead of fixing an issue in consequent patches.

/Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBCgAGBQJT6Ia0AAoJEC5aWaUY1u57dHsIAIzF0vlYtF1G+lCDQFe6ROAJ
KAK87BUplMFBQiBwwbhnOx74aQYCITdwW/jjBYi0iae/4pZpd5fY50awKGNPo2XV
m2DWp20SDLgVbUlBq4PSRmbN4LIMjvjfhxm/3qfK4qJBunmqVYHIbAZ8DRNWX/nZ
i4KkYa+i6MRvPUlp9iZTbjSL4q2EA010X0uo9dkmEbjFVguNqzKAgZxQ0b9V+GII
4vl7uu5OzEoCZuWYjcCIk9zOJgaFso9kGoZlFHe4CQC4389jyyfIJYnETSMtDvId
Ni16n5d7w0TXsZKvpp5lTyvS6zrZwQATUAIQ6g2Gt/pjbIFKAA3W0asPMG++2V0=
=2GZ+
-----END PGP SIGNATURE-----