Thanks for the response Olemis.
The advice from Greg might have been interpreted to mean that all voters
should be checking the release carefully before voting. This seems
helpful as any input into whether the release is fit is better if it is
informed by some level of checking.
I don't have a definitive answer although it would seem sensible for the
Bloodhound PPMC to take particular note of Greg's advice.
Cheers,
Gary
On 02/08/12 01:57, Olemis Lang wrote:
On 8/1/12, Gary Martin <[email protected]> wrote:
On 30/07/12 12:48, Joachim Dreimann wrote:
Just for the record, I have downloaded reviewed the files to my technical
ability.
+1 for the release from me.
I second that . The only thing I can mention is that even if manual
installation procedure works for me , on the other hand all the
attempts I made so as to install it from tarball in a Jenkins build
job have failed . This is mainly because :
1. I'm not a proficient Jenkins user ...
2. it seems there's an issue with virtualenv somewhere and ...
3. I've not been able to dedicate any time to this task after the
few initial experiments
That's obviously not a reason to stop release tarball from being
released , so ...
+1 for release
The following is a short description of how to verify that the package
is signed:
[...]
... and all these checks , well I've not tried them yet . Should I ?
