bloodhound-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Dreimann <>
Subject Re: Getting IPMC members to vote Re: [VOTE] Release Apache Bloodhound 0.4 (incubating)
Date Wed, 23 Jan 2013 19:45:05 GMT
I don't know if it's allowed to combine both votes, but I'm in favour of it if it is.

In relation to the currently stalled voting, I'd like to propose Gary as a future IPMC member.
Is there a process for this?

Also or alternatively, is there a process for recruiting further mentors? Or is it "simply"
a case of picking out potential mentors and asking them?


@jdreimann - Twitter
Sent from my phone

On 23 Jan 2013, at 18:23, Gary Martin <> wrote:

> Hi,
> So, our vote has been stalled in the incubator general list for a few days now. I gave
a prod the other day with no obvious result and I have just made a bit more of a nuisance
of myself by following up on a different thread on a similar theme. Do we have any other means
to encourage more people to review?
> The other thing that springs to mind is that currently we go through two votes which
is clearly the normal process. Are we at a point where we could consider going through a single
vote simultaneously on bloodhound-dev@ and general@? Is this approach allowed?
> Cheers,
>    Gary
> On 17/01/13 22:47, Ryan Ollos wrote:
>> Hi everyone,
>> I would like to initiate the vote for releasing Apache Bloodhound 0.4
>> (incubating)
>> in the incubator following the successful vote of the Bloodhound PPMC.
>> The vote PPMC vote thread:
>> Please find the change log for this proposed release below:
>>  * Replaces ticket edit form with a new 'in-place' edit and workflow control
>>  * Added white-labeling for error messages and basic branding
>>  * Improvements to the quick ticket creation form including ability to
>> specify the select fields and their order
>>  * Various bug fixes
>>  * Not fixed for this release:
>>    * No major outstanding issues
>> 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:
>> The archive is based on the tag:
>> For this release, the archive differs from the tag in that the Trac
>> "contrib" directory has been removed from the archive. The files
>> in that directory currently lack license headers. We are working
>> with the Trac team to clarify the licenses under which the contrib files
>> are released:
>> Please vote:
>> [ ] +1 Release this package as Apache Bloodhound 0.4
>> [ ] +0 Don't care
>> [ ] -1 Do not release this package (please explain)
>> The vote is open for 72 hours.
>> Regards,
>> - Ryan

View raw message