incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marvin Humphrey <>
Subject Re: [RESULT] [VOTE] Apache TinkerPop 3.0.0.M8-incubating Release (Part Deux)
Date Sun, 10 May 2015 19:20:27 GMT
On Sun, May 10, 2015 at 6:05 AM, John D. Ament <> wrote:

> svn log -v -r {2015-04-01}:HEAD
> I'm noticing that a lot of unapproved releases are ending up in here.
> These are the ones I've identified, with no matching result vote (that I
> can find)

> Apache Sentry

This one looks like a problem.  A vote was taken for Sentry 1.5.0 on the
podling dev list, but there has been no vote on general@incubator.

It would be perfectly understandable for an individual release manager to
misunderstand the incubating release process, but it's troubling that not a
single podling community member spoke up.  What's going on?

> Apache Streams (I can find rc3, but not 0.2)

I find 0.2 here:

The vote for Streams 0.2 rc3 passed.

> Apache Tinkerpop (Probably my biggest concern, I see the vote thread, then
> a cancel thread, yet their website lists the release, though it could be
> the mail issues caused some mails to come in out of order on my side)

It would have been less confusing if Tinkerpop had used RC numbers instead of
"Part Deux" (French for "part two") to indicate that a new vote was being
called on a new release candidate.

Nevertheless, the vote passed:

> Apache REEF

It looks like multiple release candidates for REEF 0.11.0-incubating have been
uploaded to the `releases` dir and then removed.  The podling is currently
voting on RC6, which has been uploaded to the `dev` dir instead -- so it looks
like they've caught on.


In conclusion, I think that Sentry merits further investigation, but that
Streams, Tinkerpop and REEF are OK.

Marvin Humphrey

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message