When does incubator-suffix get dropped?
Hi, I’ve been hearing big talky talky that Incubator suffixes are “just handled” — Git, homepage, mailing lists. When does talky talky become doey doey? Thanks, Marko. http://markorodriguez.com
[DISCUSS] ASF Board Draft Report - June 2016
As TinkerPop has graduated from incubator, we no longer need to produce incubator reports. Instead, TinkerPop needs to now provide reports to the ASF Board. Ultimately, as PMC chair it is my responsibility to submit the report when required, but I liked our method of discussing the incubator report prior to submission so I'd like to continue that. The content is largely the same - you can read more about what's required here: http://www.apache.org/foundation/board/reporting and see examples of other project's reports here: https://svn.apache.org/repos/private/foundation/board/board_agenda_2016_05_18.txt Anyway, here's a draft of the June report that I've prepared - please feel free to offer any feedback: ## Description: Apache TinkerPop is a graph computing framework for both graph databases (OLTP) and graph analytic systems (OLAP). This is TinkerPop's first month outside of incubation. We are still awaiting resource transfer changes related to graduation to take place as there are issues preventing the infrastructure team from completing that process. Project development has been building up to two new releases which are expected to be released in July. A key area of focus in this last month has been related to opening TinkerPop to non-JVM programming languages through the concept of Gremlin Language Variants[1]. In taking this direction, TinkerPop becomes more accessible to non-JVM developer communities. ## Issues: There are no issues requiring board attention at this time. ## Releases: - 3.1.2 (April 8, 2016) - 3.2.0 (April 8, 2016) ## PMC/Committer: - Last PMC addition was Dylan Millikin - May 2016 - Last committer addition was Michael Pollmeier - April 2016 [1] http://tinkerpop.apache.org/docs/3.2.1-SNAPSHOT/tutorials/gremlin-language-variants/
[jira] [Commented] (TINKERPOP-1318) java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch
[
https://issues.apache.org/jira/browse/TINKERPOP-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15315476#comment-15315476
]
ASF GitHub Bot commented on TINKERPOP-1318:
---
Github user pluradj commented on the issue:
https://github.com/apache/incubator-tinkerpop/pull/329
This change is simple enough and shouldn't impact anything (short of an
incompatibility between mockito and the version of hamcrest here, but the tests
pass so it should be ok.)
VOTE +1
> java.lang.NoSuchMethodError: org/hamcrest/Matcher.describeMismatch
> --
>
> Key: TINKERPOP-1318
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1318
> Project: TinkerPop
> Issue Type: Bug
> Components: test-suite
>Affects Versions: 3.2.0-incubating, 3.1.2-incubating
>Reporter: Jason Plurad
>Assignee: Jason Plurad
>Priority: Minor
>
> I don't recall specifically how to make this fail with {{gremlin-test}}, but
> I did run into it at one point when writing a graph implementation. This blog
> describes the issue and workaround.
> https://tedvinke.wordpress.com/2013/12/17/mixing-junit-hamcrest-and-mockito-explaining-nosuchmethoderror/
> The error trace looks like this:
> {noformat}
> java.lang.NoSuchMethodError:
> org.hamcrest.Matcher.describeMismatch(Ljava/lang/Object;Lorg/hamcrest/Description;)V
> {noformat}
> There is a dependency conflict created by an older version of {{hamcrest}}
> coming out of {{mockito-all}}. The fix is to use {{mockito-core}} instead.
> I'll submit a patch for this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[GitHub] incubator-tinkerpop issue #329: TINKERPOP-1318: use mockito-core instead of ...
Github user pluradj commented on the issue: https://github.com/apache/incubator-tinkerpop/pull/329 This change is simple enough and shouldn't impact anything (short of an incompatibility between mockito and the version of hamcrest here, but the tests pass so it should be ok.) VOTE +1 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
