You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Marko Rodriguez <ok...@gmail.com> on 2015/03/16 14:38:38 UTC
Re: [TinkerPop] [TinkerPop3] The TinkerPop3 Roadmap to GA.
Hello David,
We are limiting the degrees of freedom when it comes to arbitrary step definitions. Given that TP3 traversal strategies (which will include TP3 "graph strategies") are only aware of TP3 steps, we are providing a library of step that we feel encompass all desired operations on a graph. When a user wants to create their own DSL, they should have it compile down to the provided set of TP3 steps. This way, known optimizations on those steps and "decorations" (e.g. ReadOnlyStrategy, IdStrategy, etc.) will work. The user is not forced to do so, but then TP3 strategies will not work for their steps and they will have to write their own strategies.
In short, recommended, but not required.
HTH,
Marko.
http://markorodriguez.com
On Mar 14, 2015, at 10:19 PM, Dave <da...@davidcrouchcustomhomes.com> wrote:
> Hi Marko,
>
> 1) re. graph strategies:- I've implemented my own, which satisfies my needs (and appears to address many of the outstanding graph strategy issues on the list)
> 2) I saw the proposal about limiting a DSL's steps to just TP3 steps, which really concerned me if I understood it correctly:-
> https://github.com/tinkerpop/tinkerpop3/issues/592
>
> I assume it was triggered by this one:-
> https://github.com/tinkerpop/tinkerpop3/issues/529
>
> I've implemented several graph strategies with related custom traversal steps (inherit from GraphStrategy). I understand and agree with #529 but am really concerned with what #592 means. I have several "Neo4jGraphTraversal-type" interfaces and classes and would hate to see the functionality that supports this to be closed off/hidden.I think 95% of vendors and developers would want to enhance GraphTraversal rather than replace it.
>
> Thanks,
> Dave
>
>
> On Friday, March 13, 2015 at 9:44:45 AM UTC-7, Marko A. Rodriguez wrote:
> Hello everyone,
>
> Stephen and I spent this morning looking through the issue tracker and determining what is absolutely necessary for GA. Here is our analysis:
>
> https://github.com/tinkerpop/tinkerpop3/issues?q=is%3Aopen+is%3Aissue+milestone%3A3.0.0.GA
>
> We would like to stick to the following timeline:
>
> 1. Coordinate with Apache mentors to get release approval.
> 2. April 5 -- release TP3 M8 (our first Apache TinkerPop release).
> 3. Work with vendors to make sure they are completely happy with core/.
> 4. May 5th -- release TP3 M9 (once released, no more API changes).
> 5. Testing, docs, cleanup…
> 6. May 25th -- release TP3 GA.
>
> Please review the tickets and share your thoughts. Note that we are no longer interested in features going into GA. Instead, we want to ensure there are no API changes down the road for 3.1, 3.2, etc. Thus, this next 2 month push is all about vendors, testing, and docs.
>
> Thank you very much,
> Marko.
>
> http://markorodriguez.com
>
>
> --
> You received this message because you are subscribed to the Google Groups "Gremlin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gremlin-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/gremlin-users/a8d1d24d-c4c7-4696-a6e0-b23a3f020446%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
Re: [TinkerPop] [TinkerPop3] The TinkerPop3 Roadmap to GA.
Posted by Matt Franklin <m....@gmail.com>.
On Tue, Mar 17, 2015 at 5:01 PM Stephen Mallette <sp...@gmail.com>
wrote:
> Mentors, the first item in Marko's list for the "Roadmap to GA" was to
> "Coordinate
> with Apache mentors to get release approval.". I saw some response to this
> as it related to Neo4j and we will certainly sort that out prior to release
> of M8 on 4/5. I was wondering if there was anything else that you all
> needed in trying to decided if M8 is releasable under the "Apache Way"? Is
> there any other information you need? a process you go through?
>
It is the responsibility of the PPMC to execute the release process. While
this could include a mentor, generally one of the other PPMC members acts
as release manager.
The first release a community makes at Apache is generally the most
difficult, as the community is establishing procedures and working through
IP/Licensing issues in their codebase. For more information on the release
process, I encourage you to look at the Apache Incubator release
documentation [1], the Apache Release policy [2] and any existing projects
that have defined a good release process.
[1] http://incubator.apache.org/guides/releasemanagement.html
[2] http://www.apache.org/dev/release.html
>
> Perhaps a more simple way to put it is: aside from the Neo4j issue, what
> other showstoppers do we have that would need to be resolved in order for
> us to successfully release for 4/5?
>
I am sure the other mentors and I can do a once-over through the current
code base, but likely many of the issues will surface during the first
release vote.
>
> Thanks,
>
> Stephen
>
> On Mon, Mar 16, 2015 at 9:38 AM, Marko Rodriguez <ok...@gmail.com>
> wrote:
>
> > Hello David,
> >
> > We are limiting the degrees of freedom when it comes to arbitrary step
> > definitions. Given that TP3 traversal strategies (which will include TP3
> > "graph strategies") are only aware of TP3 steps, we are providing a
> library
> > of step that we feel encompass all desired operations on a graph. When a
> > user wants to create their own DSL, they should have it compile down to
> the
> > provided set of TP3 steps. This way, known optimizations on those steps
> and
> > "decorations" (e.g. ReadOnlyStrategy, IdStrategy, etc.) will work. The
> user
> > is not forced to do so, but then TP3 strategies will not work for their
> > steps and they will have to write their own strategies.
> >
> > In short, recommended, but not required.
> >
> > HTH,
> > Marko.
> >
> > http://markorodriguez.com
> >
> > On Mar 14, 2015, at 10:19 PM, Dave <da...@davidcrouchcustomhomes.com>
> > wrote:
> >
> > Hi Marko,
> >
> > 1) re. graph strategies:- I've implemented my own, which satisfies my
> > needs (and appears to address many of the outstanding graph strategy
> issues
> > on the list)
> > 2) I saw the proposal about limiting a DSL's steps to just TP3 steps,
> > which really concerned me if I understood it correctly:-
> > https://github.com/tinkerpop/tinkerpop3/issues/592
> >
> > I assume it was triggered by this one:-
> > https://github.com/tinkerpop/tinkerpop3/issues/529
> >
> > I've implemented several graph strategies with related custom traversal
> > steps (inherit from GraphStrategy). I understand and agree with #529 but
> am
> > really concerned with what #592 means. I have several
> > "Neo4jGraphTraversal-type" interfaces and classes and would hate to see
> > the functionality that supports this to be closed off/hidden.I think 95%
> of
> > vendors and developers would want to enhance GraphTraversal rather than
> > replace it.
> >
> > Thanks,
> > Dave
> >
> >
> > On Friday, March 13, 2015 at 9:44:45 AM UTC-7, Marko A. Rodriguez wrote:
> >>
> >> Hello everyone,
> >>
> >> Stephen and I spent this morning looking through the issue tracker and
> >> determining what is absolutely necessary for GA. Here is our analysis:
> >>
> >> https://github.com/tinkerpop/tinkerpop3/issues?q=is%3Aopen+
> >> is%3Aissue+milestone%3A3.0.0.GA
> >> <https://github.com/tinkerpop/tinkerpop3/issues?q=is:open+
> is:issue+milestone:3.0.0.GA>
> >>
> >> We would like to stick to the following timeline:
> >>
> >> 1. Coordinate with Apache mentors to get release approval.
> >> 2. *April 5* -- release TP3 M8 (our first Apache TinkerPop release).
> >> 3. Work with vendors to make sure they are completely happy with core/.
> >> 4. *May 5th* -- release TP3 M9 (once released, no more API changes).
> >> 5. Testing, docs, cleanup…
> >> 6. *May 25th* -- release TP3 GA.
> >>
> >> Please review the tickets and share your thoughts. Note that we are no
> >> longer interested in features going into GA. Instead, we want to ensure
> >> there are no API changes down the road for 3.1, 3.2, etc. Thus, this
> next 2
> >> month push is all about vendors, testing, and docs.
> >>
> >> Thank you very much,
> >> Marko.
> >>
> >> http://markorodriguez.com
> >>
> >>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Gremlin-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to gremlin-users+unsubscribe@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/gremlin-users/a8d1d24d-
> c4c7-4696-a6e0-b23a3f020446%40googlegroups.com
> > <https://groups.google.com/d/msgid/gremlin-users/a8d1d24d-
> c4c7-4696-a6e0-b23a3f020446%40googlegroups.com?utm_medium=
> email&utm_source=footer>
> > .
> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Gremlin-users" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to gremlin-users+unsubscribe@googlegroups.com.
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/gremlin-users/FF464862-
> 188D-4F2B-BBA3-59A687417BA2%40gmail.com
> > <https://groups.google.com/d/msgid/gremlin-users/FF464862-
> 188D-4F2B-BBA3-59A687417BA2%40gmail.com?utm_medium=email&utm_source=footer
> >
> > .
> >
> > For more options, visit https://groups.google.com/d/optout.
> >
>
Re: [TinkerPop] [TinkerPop3] The TinkerPop3 Roadmap to GA.
Posted by Stephen Mallette <sp...@gmail.com>.
Mentors, the first item in Marko's list for the "Roadmap to GA" was to
"Coordinate
with Apache mentors to get release approval.". I saw some response to this
as it related to Neo4j and we will certainly sort that out prior to release
of M8 on 4/5. I was wondering if there was anything else that you all
needed in trying to decided if M8 is releasable under the "Apache Way"? Is
there any other information you need? a process you go through?
Perhaps a more simple way to put it is: aside from the Neo4j issue, what
other showstoppers do we have that would need to be resolved in order for
us to successfully release for 4/5?
Thanks,
Stephen
On Mon, Mar 16, 2015 at 9:38 AM, Marko Rodriguez <ok...@gmail.com>
wrote:
> Hello David,
>
> We are limiting the degrees of freedom when it comes to arbitrary step
> definitions. Given that TP3 traversal strategies (which will include TP3
> "graph strategies") are only aware of TP3 steps, we are providing a library
> of step that we feel encompass all desired operations on a graph. When a
> user wants to create their own DSL, they should have it compile down to the
> provided set of TP3 steps. This way, known optimizations on those steps and
> "decorations" (e.g. ReadOnlyStrategy, IdStrategy, etc.) will work. The user
> is not forced to do so, but then TP3 strategies will not work for their
> steps and they will have to write their own strategies.
>
> In short, recommended, but not required.
>
> HTH,
> Marko.
>
> http://markorodriguez.com
>
> On Mar 14, 2015, at 10:19 PM, Dave <da...@davidcrouchcustomhomes.com>
> wrote:
>
> Hi Marko,
>
> 1) re. graph strategies:- I've implemented my own, which satisfies my
> needs (and appears to address many of the outstanding graph strategy issues
> on the list)
> 2) I saw the proposal about limiting a DSL's steps to just TP3 steps,
> which really concerned me if I understood it correctly:-
> https://github.com/tinkerpop/tinkerpop3/issues/592
>
> I assume it was triggered by this one:-
> https://github.com/tinkerpop/tinkerpop3/issues/529
>
> I've implemented several graph strategies with related custom traversal
> steps (inherit from GraphStrategy). I understand and agree with #529 but am
> really concerned with what #592 means. I have several
> "Neo4jGraphTraversal-type" interfaces and classes and would hate to see
> the functionality that supports this to be closed off/hidden.I think 95% of
> vendors and developers would want to enhance GraphTraversal rather than
> replace it.
>
> Thanks,
> Dave
>
>
> On Friday, March 13, 2015 at 9:44:45 AM UTC-7, Marko A. Rodriguez wrote:
>>
>> Hello everyone,
>>
>> Stephen and I spent this morning looking through the issue tracker and
>> determining what is absolutely necessary for GA. Here is our analysis:
>>
>> https://github.com/tinkerpop/tinkerpop3/issues?q=is%3Aopen+
>> is%3Aissue+milestone%3A3.0.0.GA
>> <https://github.com/tinkerpop/tinkerpop3/issues?q=is:open+is:issue+milestone:3.0.0.GA>
>>
>> We would like to stick to the following timeline:
>>
>> 1. Coordinate with Apache mentors to get release approval.
>> 2. *April 5* -- release TP3 M8 (our first Apache TinkerPop release).
>> 3. Work with vendors to make sure they are completely happy with core/.
>> 4. *May 5th* -- release TP3 M9 (once released, no more API changes).
>> 5. Testing, docs, cleanup…
>> 6. *May 25th* -- release TP3 GA.
>>
>> Please review the tickets and share your thoughts. Note that we are no
>> longer interested in features going into GA. Instead, we want to ensure
>> there are no API changes down the road for 3.1, 3.2, etc. Thus, this next 2
>> month push is all about vendors, testing, and docs.
>>
>> Thank you very much,
>> Marko.
>>
>> http://markorodriguez.com
>>
>>
> --
> You received this message because you are subscribed to the Google Groups
> "Gremlin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gremlin-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/gremlin-users/a8d1d24d-c4c7-4696-a6e0-b23a3f020446%40googlegroups.com
> <https://groups.google.com/d/msgid/gremlin-users/a8d1d24d-c4c7-4696-a6e0-b23a3f020446%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Gremlin-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to gremlin-users+unsubscribe@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/gremlin-users/FF464862-188D-4F2B-BBA3-59A687417BA2%40gmail.com
> <https://groups.google.com/d/msgid/gremlin-users/FF464862-188D-4F2B-BBA3-59A687417BA2%40gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>