Thanks Joe, that is very much appreciated.
I would also plus one on this vote although I am not sure it would be
better to get our binding votes from three people independently of the
release manager and, in particular, with the help of our mentors. In
fact, I was under the impression that the support of our mentors was
pretty much essential.
For those who are less experienced, is there anything you need to know
about the process to help you decide on your vote?
The following is a short description of how to verify that the package
is signed:
http://www.apache.org/dev/release-signing.html#verifying-signature
In summary if you checkout the whole of
https://dist.apache.org/repos/dist/dev/incubator/bloodhound/ there is a
KEYS file, the
signature file, the release tarball itself, allowing you to:
|gpg --import KEYS
||gpg --verify
apache-bloodhound-incubating-0.1.0-RC1.tar.gz.asc||apache-bloodhound-incubating-0.1.0-RC1.tar.gz|||
There is also an md5 file if you wish to verify that against the tarball
too.
Apache Rat, meanwhile, may provide a way to determine what files are
missing apache licence headers. If you are interested in using that,
details can be found here: http://creadur.apache.org/rat/
Cheers,
Gary
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.
Cheers,
Joe
On 30 July 2012 10:49, Gary Martin <[email protected]> wrote:
Hi,
The 72 hours is well past and so it looks like I have failed to mobilise
the potential vote at this point. I have not looked up the rules associated
with votes that are past their sell-by date, but for now I am prepared to
let the vote continue.
In case I haven't mentioned this before, I am particularly interested in
the votes of our mentors. Sorry for any pressure that this puts upon them
but If there are any problems with eligibility for release, I am sure they
will spot them.
Cheers,
Gary
On 25/07/12 21:36, Greg Stein wrote:
Here are the instructions that Subversion uses, so it would be
something similar:
http://subversion.apache.org/**docs/community-guide/**
releasing.html#tarball-signing<http://subversion.apache.org/docs/community-guide/releasing.html#tarball-signing>
You can see the resulting set of signatures for each tarball; for example:
https://dist.apache.org/repos/**dist/release/subversion/**
subversion-1.7.5.tar.bz2.asc<https://dist.apache.org/repos/dist/release/subversion/subversion-1.7.5.tar.bz2.asc>
Cheers,
-g
On Wed, Jul 25, 2012 at 4:19 PM, Mark Poole <[email protected]> wrote:
I'm currently running this version in production.
How would I provide you with my signature to verify the release in
future?
On Wed, Jul 25, 2012 at 7:33 PM, Greg Stein <[email protected]> wrote:
PPMC members have a "binding" vote (ie. it counts).
All others can vote, but those are considered advisory or "non-binding".
People should vote +1 *only* if they have downloaded the tarball and
reviewed it. Including verification of signature(s). In the future, it
would be nice to get additional signatures from those who vote +1, and
attach those signatures to the release.
Cheers,
-g
On Wed, Jul 25, 2012 at 1:19 PM, Ian Wild <[email protected]>
wrote:
Great to see!
Who can vote?
Ian
--
Ian Wild
VP Engineering
WANdisco plc
Mobile +44 (0)7720 093010
Office DDI: +44 (0)114 3030472
US: +1 925 3801734
http://www.wandisco.com
uberSVN: Apache Subversion Made Easy
http://www.uberSVN.com <http://www.ubersvn.com/>
Everything you need to deploy Subversion in the Enterprise
http://www.wandisco.com/**subversion<http://www.wandisco.com/subversion>
<
http://www.wandisco.com/**subversion/multisite<http://www.wandisco.com/subversion/multisite>
Subversion community
http://www.svnforum.org
On Wed, Jul 25, 2012 at 6:18 PM, Gary Martin <[email protected]
wrote:
Hi everyone,
I hope that this is not premature but as the conversation on the
related
[PROPOSAL] thread has died down, I would like to initiate the vote for
releasing Apache Bloodhound 0.1.0 (incubating). If successful this
will
be
the first release of the project and is an important step that I hope
will
generate interest in the project and help the community to grow.
The release candidate this vote relates to provides:
* A patched version of Trac
* A new dashboard view with the dashboard style unifying views of
tickets, milestones and the user's dashboard.
* A re-theming of the interface to use bootstrap
* Preliminary multi-product support as a step towards allowing the
tracking of multiple distinct products (or projects) in a single
environment
* Simplified installation with the inclusion of a number of plugins
as
standard.
As an initial release, of particular importance is that we have taken
proper notice of licensing of code produced as part of this project
and
the
proper acknowledgement of external work packaged with it.
The release candidate artifacts consist of source release as a tar.gz
archive along with the associated MD5 and GPG signature. These can be
found
at:
https://dist.apache.org/repos/****dist/dev/incubator/**bloodhound/<https://dist.apache.org/repos/**dist/dev/incubator/bloodhound/>
<
https://dist.apache.org/repos/**dist/dev/incubator/bloodhound/<https://dist.apache.org/repos/dist/dev/incubator/bloodhound/>
**>
Please vote:
[ ] +1 Release this package as Apache Bloodhound 0.1.0
[ ] +0 Don't care
[ ] -1 Do not release this package (please explain)
The vote is open for 72 hours and, if successful, will be followed by
a
vote on general@incubator for a further 72 hours.
