* built from source and ran all unit tests - over 1hr!
* checked LICENSE and NOTICE files
* Noticed things that others have already noted
* Noted that there is no CHANGES file in the release artifact - there is a
CHANGES.txt in
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubati
Thanks Ate!
We still need a few more votes this week the close voting.
--emi
‐‐‐ Original Message ‐‐‐
On 23 May 2018 11:44 PM, Ate Douma wrote:
> On 2018-05-23 20:57, Emilian Bold wrote:
>
> > Ate, could we get a vote on this release?
>
> Sure :-)
>
> > If you look at
> > https://
any more IPMC votes..? Last chance before GDPR! ;)
On Mon, 21 May 2018 10:57:40 +0100, Stian Soiland-Reyes
wrote:
> The Taverna PPMC has voted to release:
>
> Apache Taverna Language 0.16.0-incubating
>
> with +4 PPMC-binding votes. This email is the IPMC vote.
>
>
> Vote thread:
> https
+1 (binding) carried over from dev@pulsar voting thread.
Regards,
Dave
> On May 23, 2018, at 10:21 PM, Matteo Merli wrote:
>
> This is the fifth release candidate for Apache Pulsar, version
> 2.0.0-rc1-incubating.
>
> Pulsar is a highly scalable, low latency messaging platform running on
> com
Hi -
-1 (binding)
There are several files in the source release that are licensed as:
Creative Commons Attribution 3.0 License
http://creativecommons.org/licenses/by/3.0
This is a category B license. [1] I’ll note that Stian is listed as a copyright
holder for some of these … Either these need
This vote passes with 9 binding +1s and one additional +1. Thanks to
everyone for voting!
Billie Rinaldi (binding)
Craig Russell (binding)
Pierre Smits
Henri Yandell (binding)
Vinod Kumar Vavilapalli (binding)
Willem Jiang (binding)
Sergio Fernández (binding)
Josh Elser (binding)
Matt Sicker (bind
+1 (binding), but with one issue ;)
The source release looks fine, as do sigs/xsums. DISCLAIMER, LICENSE and
NOTICE are all fine too.
Only thing I see is that your new additions made in
https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS
must be reflected in
https://dist.
On 24 May 2018 at 22:40, Josh Elser wrote:
> +1 (binding), but with one issue ;)
>
> The source release looks fine, as do sigs/xsums. DISCLAIMER, LICENSE and
> NOTICE are all fine too.
>
> Only thing I see is that your new additions made in
> https://dist.apache.org/repos/dist/dev/incubator/omid/0
The vote has passed by lazy consensus. Thank you
On Sun, May 20, 2018 at 8:56 PM, Wes McKinney wrote:
> Apache Arrow is receiving a code donation of a Ruby language library [1].
>
> Please vote to approve this contribution.
>
> This is a lazy consensus majority vote, per the IP clearance process
+1 (transferred from my dev vote)
On Thu, May 24, 2018 at 6:49 AM, larry mccay wrote:
> * built from source and ran all unit tests - over 1hr!
> * checked LICENSE and NOTICE files
> * Noticed things that others have already noted
> * Noted that there is no CHANGES file in the release artifact -
The vote is now closed and passes with 7 +1 votes and no +0 or -1 votes.
Thanks to everyone who voted.
James
On Thu, May 24, 2018 at 4:03 PM, James Taylor
wrote:
> +1 (transferred from my dev vote)
>
> On Thu, May 24, 2018 at 6:49 AM, larry mccay wrote:
>
>> * built from source and ran all
Willem,
You didn’t cast a vote on the release.
I don’t think test failures is a blocker because README.md tells people to skip
tests.
IPMC,
We still need one more +1, please.
Julian
> On May 23, 2018, at 12:23 AM, Jonas Pfefferle wrote:
>
> Hi,
>
> At the moment there is no way to run th
+1 binding
1. Verified sigs and hashes
2. Built from source
3. incubating in artifacts name
On Thu, May 24, 2018 at 7:08 PM, Julian Hyde wrote:
> Willem,
>
> You didn’t cast a vote on the release.
>
> I don’t think test failures is a blocker because README.md tells people to
> skip tests.
>
> I
I can build the kit after skipping the test and there is a build
instruction in the README. I'm sorry I didn't find it at first check.
Now I have some trouble to find the signing key from the distribution
directory. We normally provide it in the KEY directory.
Willem Jiang
Twitter: willemjiang
I found the KEY file from the PPMC voting mail[1].
According to note of from apache key home[2], the Key for release should
not be the link.
- The KEYS files must be stored in the ASF mirror directories. This
ensures that they are archived along with the releases to which they apply.
- Th
15 matches
Mail list logo
