FYI, after enough consideration, we the Hadoop community dropped support for
JDK 6 starting release Apache Hadoop 2.7.x.
Thanks
+Vinod
On Apr 30, 2015, at 12:02 PM, Reynold Xin r...@databricks.com wrote:
This has been discussed a few times in the past, but now Oracle has ended
support for
an inclusive project and we
spend a lot of effort culturally to help make newcomers feel welcome.
- Patrick
On Wed, Apr 22, 2015 at 1:11 PM, Vinod Kumar Vavilapalli
vino...@hortonworks.com wrote:
Actually what this community got away with is pretty much an
anti-pattern compared to every other
I watch these lists, so I have a fair understanding of how things work around
here. I don't give direct input in the day to day activities though, like Greg
Stein on the other thread, so I can understand if it looks like it came from up
above. Apache Members come around and give opinions time
Actually what this community got away with is pretty much an anti-pattern
compared to every other Apache project I have seen. And may I say in a not so
Apache way.
Waiting for a committer to assign a patch to someone leaves it as a privilege
to a committer. Not alluding to anything fishy in
requests on github, which is a newer
friendlier better model given the constraints. We even have tools that
automatically tags a ticket with a link to the pull requests.
On Wed, Apr 22, 2015 at 1:11 PM, Vinod Kumar Vavilapalli
vino...@hortonworks.commailto:vino...@hortonworks.com wrote
With the maintainer model, the process is as follows:
- Any committer could review the patch and merge it, but they would need to
forward it to me (or another core API maintainer) to make sure we also approve
- At any point during this process, I could come in and -1 it, or give
feedback
