[
https://issues.apache.org/jira/browse/TINKERPOP-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boxuan Li updated TINKERPOP-2753:
-
Description:
I only have experience in JanusGraph, so my opinion might be biased and this
pr
[
https://issues.apache.org/jira/browse/TINKERPOP-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boxuan Li updated TINKERPOP-2753:
-
Description:
I only have experience in JanusGraph, so my opinion might be biased and this
pr
Boxuan Li created TINKERPOP-2753:
Summary: Create noop() step to avoid eager optimization
Key: TINKERPOP-2753
URL: https://issues.apache.org/jira/browse/TINKERPOP-2753
Project: TinkerPop
Issu
[
https://issues.apache.org/jira/browse/TINKERPOP-2753?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Boxuan Li updated TINKERPOP-2753:
-
Description:
I only have experience in JanusGraph, so my opinion might be biased and this
pr
Stephen
That is a fair point. Labels do tend to deviate and contain typos. However,
there may be scenarios when a code change is trivial enough to be picked by
a new contributor and yet has a priority which is more important than
trivial. That is the reason I would like to disambiguate between the
We've long used "Trivial" priority to denote easy to jump into issues for
new folks.
https://tinkerpop.apache.org/docs/current/dev/developer/#_considering_code_changes
I liked using the priority field this way because labels have a way of
being mistyped from "newbie" to "newbies" to "noobie" to "
