You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by Stephen Mallette <sp...@gmail.com> on 2015/10/07 17:24:52 UTC
[DISCUSS] Remaining Issues on 3.0.2
There are currently 5 unresolved issues assigned to 3.0.2:
http://bit.ly/1Q7Ez8O
In summary we have:
https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned - probably
me/Kuppitz)
https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
My point in bringing these up is to open up dialog on any issues with these
final tickets as we'd previously discussed closing the doors on 3.0.2 on
10/19. I'd also like to ask if anyone is aware of any other critical
issues not on the general 3.0.2 list - if so, please raise them for
discussion.
For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
really clear what we need to do. Mr. Kuppitz, can you help us come to some
concrete steps to take for that issue please? If time is an issue and you
have SEO research to do, let's consider pushing this issue forward to 3.1.0
and get stuff right at that point. Any SEO folks on the list who can help
on that one?
I'd also like to make sure the road is clear to finish up 319. As I
recall, that issue was blocked by:
https://issues.apache.org/jira/browse/TINKERPOP3-828
but that is complete now, so 319 should be clear. All good there, Daniel?
Thanks, everyone - Please feel free to chime in with any issues related to
3.0.2.
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Had to tack in this one for 3.0.2:
https://issues.apache.org/jira/browse/TINKERPOP3-870
a small bug in the java-driver. It has a workaround, but it's not nice.
Shouldn't be too hard to fix - diagnosing it in the first place was the
hard part.
On Wed, Oct 7, 2015 at 11:24 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> There are currently 5 unresolved issues assigned to 3.0.2:
> http://bit.ly/1Q7Ez8O
>
> In summary we have:
>
> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
> probably me/Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>
> My point in bringing these up is to open up dialog on any issues with
> these final tickets as we'd previously discussed closing the doors on 3.0.2
> on 10/19. I'd also like to ask if anyone is aware of any other critical
> issues not on the general 3.0.2 list - if so, please raise them for
> discussion.
>
> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
> really clear what we need to do. Mr. Kuppitz, can you help us come to some
> concrete steps to take for that issue please? If time is an issue and you
> have SEO research to do, let's consider pushing this issue forward to 3.1.0
> and get stuff right at that point. Any SEO folks on the list who can help
> on that one?
>
> I'd also like to make sure the road is clear to finish up 319. As I
> recall, that issue was blocked by:
>
> https://issues.apache.org/jira/browse/TINKERPOP3-828
>
> but that is complete now, so 319 should be clear. All good there, Daniel?
>
>
> Thanks, everyone - Please feel free to chime in with any issues related to
> 3.0.2.
>
>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Just wanted to wrap up this thread now that the VOTE is out for
3.0.2-incubating. I think that having this thread running during the week
was helpful to me as the "release manager". Hopefully, it was helpful to
others so that it was clear on where things were and what needed to be done
to finish up the release.
On Mon, Oct 19, 2015 at 7:57 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> Release work on the tp30 branch is underway. Please consider that branch
> frozen at this point.
>
> On Fri, Oct 16, 2015 at 6:31 PM, Marko Rodriguez <ok...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I manually reviewed the docs and they look good. The
>> BulkLoaderVertexProgram split between graph-computer.asciidoc and the
>> Hadoop section was crucial and looks good. I'm right now building and
>> publishing the master/ docs so we know that 3.1.0-SNAPSHOT looks pretty too.
>>
>> Thanks for your hard work today. Appreciate your patience on the matter.
>>
>> Marko.
>>
>> http://markorodriguez.com
>>
>> On Oct 16, 2015, at 2:19 PM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>>
>> > I've just published SNAPSHOT docs for 3.0.2-SNAPSHOT. I would say that
>> > this validates that doc generation is good to go for Monday:
>> >
>> > http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/
>> > http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/upgrade.html
>> >
>> > Looks like we're still trying to get the review complete on Jason's
>> issue.
>> > After that, please consider tp30 frozen for the weekend as I intend to
>> > start release work first thing Monday morning and would like to have a
>> > happy day of it. Enjoy the weekend folks!
>> >
>> >
>> > On Thu, Oct 15, 2015 at 10:12 AM, Marko Rodriguez <okrammarko@gmail.com
>> >
>> > wrote:
>> >
>> >> Hi,
>> >>
>> >> Everyone, please update the CHANGELOG with your * …. notes of what you
>> >> accomplished. We have JIRA itemizations, but also put them into the
>> >> CHANGELOG too.
>> >>
>> >> In general, every time you commit to a release branch, be sure to add
>> your
>> >> CHANGELOG notes.
>> >>
>> >> Thanks,
>> >> Marko.
>> >>
>> >> http://markorodriguez.com
>> >>
>> >> On Oct 15, 2015, at 8:00 AM, Stephen Mallette <sp...@gmail.com>
>> >> wrote:
>> >>
>> >>> Another quick status check for the 3.0.2 countdown. There are just
>> two
>> >>> issues left open in JIRA on this version. As both are under
>> development
>> >>> right now, I would think we can get them through our new RTC process
>> by
>> >> end
>> >>> of day tomorrow so that I can just wake up with a fresh mind on Monday
>> >> and
>> >>> just head right to the release process. Please yell if you're
>> working on
>> >>> those issues and don't think that is possible for some reason.
>> >>>
>> >>> If you have not done so already, please take a look at our upgrade
>> docs
>> >> and
>> >>> make changes as needed (again, nice to have this all squared away by
>> the
>> >>> weekend):
>> >>>
>> >>>
>> >>
>> https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
>> >>>
>> >>> Thanks,
>> >>>
>> >>> Stephen
>> >>>
>> >>>
>> >>>
>> >>> On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <
>> spmallette@gmail.com
>> >>>
>> >>> wrote:
>> >>>
>> >>>> Hi all, just a quick reminder that we're about a week a way from
>> getting
>> >>>> the 3.0.2 release process going. As you may have noted from another
>> >> thread
>> >>>> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
>> >>>> preparation for that release. Looks like we are down to just three
>> open
>> >>>> issues with 3.0.2. :)
>> >>>>
>> >>>> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <
>> spmallette@gmail.com>
>> >>>> wrote:
>> >>>>
>> >>>>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I
>> >> just
>> >>>>> completed that bug fix to 870 which was pretty simple after all the
>> >> work I
>> >>>>> had to do to just initially identify the problem.
>> >>>>>
>> >>>>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru>
>> >> wrote:
>> >>>>>
>> >>>>>> I'm currently working on 852, I think I will be done
>> today/tomorrow.
>> >> Once
>> >>>>>> that's done, I can work on 319 - this only means: verify that the
>> >>>>>> TinkerGraph persistence works well with BLVP and write
>> >> unit/integration
>> >>>>>> tests for it. The other pending things in 319 are subject to 3.1.0.
>> >>>>>>
>> >>>>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to
>> solve
>> >> it
>> >>>>>> (unless someone else comes up with some ideas).
>> >>>>>>
>> >>>>>> Cheers,
>> >>>>>> Daniel
>> >>>>>>
>> >>>>>>
>> >>>>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <
>> >> spmallette@gmail.com>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>> There are currently 5 unresolved issues assigned to 3.0.2:
>> >>>>>>> http://bit.ly/1Q7Ez8O
>> >>>>>>>
>> >>>>>>> In summary we have:
>> >>>>>>>
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned
>> -
>> >>>>>>> probably
>> >>>>>>> me/Kuppitz)
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>> >>>>>>>
>> >>>>>>> My point in bringing these up is to open up dialog on any issues
>> with
>> >>>>>> these
>> >>>>>>> final tickets as we'd previously discussed closing the doors on
>> 3.0.2
>> >>>>>> on
>> >>>>>>> 10/19. I'd also like to ask if anyone is aware of any other
>> critical
>> >>>>>>> issues not on the general 3.0.2 list - if so, please raise them
>> for
>> >>>>>>> discussion.
>> >>>>>>>
>> >>>>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but
>> I'm
>> >> not
>> >>>>>>> really clear what we need to do. Mr. Kuppitz, can you help us
>> come
>> >> to
>> >>>>>> some
>> >>>>>>> concrete steps to take for that issue please? If time is an issue
>> >> and
>> >>>>>> you
>> >>>>>>> have SEO research to do, let's consider pushing this issue
>> forward to
>> >>>>>> 3.1.0
>> >>>>>>> and get stuff right at that point. Any SEO folks on the list who
>> can
>> >>>>>> help
>> >>>>>>> on that one?
>> >>>>>>>
>> >>>>>>> I'd also like to make sure the road is clear to finish up 319.
>> As I
>> >>>>>>> recall, that issue was blocked by:
>> >>>>>>>
>> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828
>> >>>>>>>
>> >>>>>>> but that is complete now, so 319 should be clear. All good there,
>> >>>>>> Daniel?
>> >>>>>>>
>> >>>>>>> Thanks, everyone - Please feel free to chime in with any issues
>> >>>>>> related to
>> >>>>>>> 3.0.2.
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>
>> >>
>>
>>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Release work on the tp30 branch is underway. Please consider that branch
frozen at this point.
On Fri, Oct 16, 2015 at 6:31 PM, Marko Rodriguez <ok...@gmail.com>
wrote:
> Hi,
>
> I manually reviewed the docs and they look good. The
> BulkLoaderVertexProgram split between graph-computer.asciidoc and the
> Hadoop section was crucial and looks good. I'm right now building and
> publishing the master/ docs so we know that 3.1.0-SNAPSHOT looks pretty too.
>
> Thanks for your hard work today. Appreciate your patience on the matter.
>
> Marko.
>
> http://markorodriguez.com
>
> On Oct 16, 2015, at 2:19 PM, Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > I've just published SNAPSHOT docs for 3.0.2-SNAPSHOT. I would say that
> > this validates that doc generation is good to go for Monday:
> >
> > http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/
> > http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/upgrade.html
> >
> > Looks like we're still trying to get the review complete on Jason's
> issue.
> > After that, please consider tp30 frozen for the weekend as I intend to
> > start release work first thing Monday morning and would like to have a
> > happy day of it. Enjoy the weekend folks!
> >
> >
> > On Thu, Oct 15, 2015 at 10:12 AM, Marko Rodriguez <ok...@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> Everyone, please update the CHANGELOG with your * …. notes of what you
> >> accomplished. We have JIRA itemizations, but also put them into the
> >> CHANGELOG too.
> >>
> >> In general, every time you commit to a release branch, be sure to add
> your
> >> CHANGELOG notes.
> >>
> >> Thanks,
> >> Marko.
> >>
> >> http://markorodriguez.com
> >>
> >> On Oct 15, 2015, at 8:00 AM, Stephen Mallette <sp...@gmail.com>
> >> wrote:
> >>
> >>> Another quick status check for the 3.0.2 countdown. There are just two
> >>> issues left open in JIRA on this version. As both are under
> development
> >>> right now, I would think we can get them through our new RTC process by
> >> end
> >>> of day tomorrow so that I can just wake up with a fresh mind on Monday
> >> and
> >>> just head right to the release process. Please yell if you're working
> on
> >>> those issues and don't think that is possible for some reason.
> >>>
> >>> If you have not done so already, please take a look at our upgrade docs
> >> and
> >>> make changes as needed (again, nice to have this all squared away by
> the
> >>> weekend):
> >>>
> >>>
> >>
> https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
> >>>
> >>> Thanks,
> >>>
> >>> Stephen
> >>>
> >>>
> >>>
> >>> On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <
> spmallette@gmail.com
> >>>
> >>> wrote:
> >>>
> >>>> Hi all, just a quick reminder that we're about a week a way from
> getting
> >>>> the 3.0.2 release process going. As you may have noted from another
> >> thread
> >>>> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
> >>>> preparation for that release. Looks like we are down to just three
> open
> >>>> issues with 3.0.2. :)
> >>>>
> >>>> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <
> spmallette@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I
> >> just
> >>>>> completed that bug fix to 870 which was pretty simple after all the
> >> work I
> >>>>> had to do to just initially identify the problem.
> >>>>>
> >>>>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru>
> >> wrote:
> >>>>>
> >>>>>> I'm currently working on 852, I think I will be done today/tomorrow.
> >> Once
> >>>>>> that's done, I can work on 319 - this only means: verify that the
> >>>>>> TinkerGraph persistence works well with BLVP and write
> >> unit/integration
> >>>>>> tests for it. The other pending things in 319 are subject to 3.1.0.
> >>>>>>
> >>>>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to
> solve
> >> it
> >>>>>> (unless someone else comes up with some ideas).
> >>>>>>
> >>>>>> Cheers,
> >>>>>> Daniel
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <
> >> spmallette@gmail.com>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> There are currently 5 unresolved issues assigned to 3.0.2:
> >>>>>>> http://bit.ly/1Q7Ez8O
> >>>>>>>
> >>>>>>> In summary we have:
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
> >>>>>>> probably
> >>>>>>> me/Kuppitz)
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
> >>>>>>>
> >>>>>>> My point in bringing these up is to open up dialog on any issues
> with
> >>>>>> these
> >>>>>>> final tickets as we'd previously discussed closing the doors on
> 3.0.2
> >>>>>> on
> >>>>>>> 10/19. I'd also like to ask if anyone is aware of any other
> critical
> >>>>>>> issues not on the general 3.0.2 list - if so, please raise them for
> >>>>>>> discussion.
> >>>>>>>
> >>>>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm
> >> not
> >>>>>>> really clear what we need to do. Mr. Kuppitz, can you help us come
> >> to
> >>>>>> some
> >>>>>>> concrete steps to take for that issue please? If time is an issue
> >> and
> >>>>>> you
> >>>>>>> have SEO research to do, let's consider pushing this issue forward
> to
> >>>>>> 3.1.0
> >>>>>>> and get stuff right at that point. Any SEO folks on the list who
> can
> >>>>>> help
> >>>>>>> on that one?
> >>>>>>>
> >>>>>>> I'd also like to make sure the road is clear to finish up 319. As
> I
> >>>>>>> recall, that issue was blocked by:
> >>>>>>>
> >>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828
> >>>>>>>
> >>>>>>> but that is complete now, so 319 should be clear. All good there,
> >>>>>> Daniel?
> >>>>>>>
> >>>>>>> Thanks, everyone - Please feel free to chime in with any issues
> >>>>>> related to
> >>>>>>> 3.0.2.
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>
> >>
>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Marko Rodriguez <ok...@gmail.com>.
Hi,
I manually reviewed the docs and they look good. The BulkLoaderVertexProgram split between graph-computer.asciidoc and the Hadoop section was crucial and looks good. I'm right now building and publishing the master/ docs so we know that 3.1.0-SNAPSHOT looks pretty too.
Thanks for your hard work today. Appreciate your patience on the matter.
Marko.
http://markorodriguez.com
On Oct 16, 2015, at 2:19 PM, Stephen Mallette <sp...@gmail.com> wrote:
> I've just published SNAPSHOT docs for 3.0.2-SNAPSHOT. I would say that
> this validates that doc generation is good to go for Monday:
>
> http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/
> http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/upgrade.html
>
> Looks like we're still trying to get the review complete on Jason's issue.
> After that, please consider tp30 frozen for the weekend as I intend to
> start release work first thing Monday morning and would like to have a
> happy day of it. Enjoy the weekend folks!
>
>
> On Thu, Oct 15, 2015 at 10:12 AM, Marko Rodriguez <ok...@gmail.com>
> wrote:
>
>> Hi,
>>
>> Everyone, please update the CHANGELOG with your * …. notes of what you
>> accomplished. We have JIRA itemizations, but also put them into the
>> CHANGELOG too.
>>
>> In general, every time you commit to a release branch, be sure to add your
>> CHANGELOG notes.
>>
>> Thanks,
>> Marko.
>>
>> http://markorodriguez.com
>>
>> On Oct 15, 2015, at 8:00 AM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>>
>>> Another quick status check for the 3.0.2 countdown. There are just two
>>> issues left open in JIRA on this version. As both are under development
>>> right now, I would think we can get them through our new RTC process by
>> end
>>> of day tomorrow so that I can just wake up with a fresh mind on Monday
>> and
>>> just head right to the release process. Please yell if you're working on
>>> those issues and don't think that is possible for some reason.
>>>
>>> If you have not done so already, please take a look at our upgrade docs
>> and
>>> make changes as needed (again, nice to have this all squared away by the
>>> weekend):
>>>
>>>
>> https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
>>>
>>> Thanks,
>>>
>>> Stephen
>>>
>>>
>>>
>>> On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <spmallette@gmail.com
>>>
>>> wrote:
>>>
>>>> Hi all, just a quick reminder that we're about a week a way from getting
>>>> the 3.0.2 release process going. As you may have noted from another
>> thread
>>>> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
>>>> preparation for that release. Looks like we are down to just three open
>>>> issues with 3.0.2. :)
>>>>
>>>> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <sp...@gmail.com>
>>>> wrote:
>>>>
>>>>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I
>> just
>>>>> completed that bug fix to 870 which was pretty simple after all the
>> work I
>>>>> had to do to just initially identify the problem.
>>>>>
>>>>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru>
>> wrote:
>>>>>
>>>>>> I'm currently working on 852, I think I will be done today/tomorrow.
>> Once
>>>>>> that's done, I can work on 319 - this only means: verify that the
>>>>>> TinkerGraph persistence works well with BLVP and write
>> unit/integration
>>>>>> tests for it. The other pending things in 319 are subject to 3.1.0.
>>>>>>
>>>>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve
>> it
>>>>>> (unless someone else comes up with some ideas).
>>>>>>
>>>>>> Cheers,
>>>>>> Daniel
>>>>>>
>>>>>>
>>>>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <
>> spmallette@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> There are currently 5 unresolved issues assigned to 3.0.2:
>>>>>>> http://bit.ly/1Q7Ez8O
>>>>>>>
>>>>>>> In summary we have:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
>>>>>>> probably
>>>>>>> me/Kuppitz)
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>>>>>>>
>>>>>>> My point in bringing these up is to open up dialog on any issues with
>>>>>> these
>>>>>>> final tickets as we'd previously discussed closing the doors on 3.0.2
>>>>>> on
>>>>>>> 10/19. I'd also like to ask if anyone is aware of any other critical
>>>>>>> issues not on the general 3.0.2 list - if so, please raise them for
>>>>>>> discussion.
>>>>>>>
>>>>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm
>> not
>>>>>>> really clear what we need to do. Mr. Kuppitz, can you help us come
>> to
>>>>>> some
>>>>>>> concrete steps to take for that issue please? If time is an issue
>> and
>>>>>> you
>>>>>>> have SEO research to do, let's consider pushing this issue forward to
>>>>>> 3.1.0
>>>>>>> and get stuff right at that point. Any SEO folks on the list who can
>>>>>> help
>>>>>>> on that one?
>>>>>>>
>>>>>>> I'd also like to make sure the road is clear to finish up 319. As I
>>>>>>> recall, that issue was blocked by:
>>>>>>>
>>>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828
>>>>>>>
>>>>>>> but that is complete now, so 319 should be clear. All good there,
>>>>>> Daniel?
>>>>>>>
>>>>>>> Thanks, everyone - Please feel free to chime in with any issues
>>>>>> related to
>>>>>>> 3.0.2.
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>
>>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
I've just published SNAPSHOT docs for 3.0.2-SNAPSHOT. I would say that
this validates that doc generation is good to go for Monday:
http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/
http://tinkerpop.incubator.apache.org/docs/3.0.2-SNAPSHOT/upgrade.html
Looks like we're still trying to get the review complete on Jason's issue.
After that, please consider tp30 frozen for the weekend as I intend to
start release work first thing Monday morning and would like to have a
happy day of it. Enjoy the weekend folks!
On Thu, Oct 15, 2015 at 10:12 AM, Marko Rodriguez <ok...@gmail.com>
wrote:
> Hi,
>
> Everyone, please update the CHANGELOG with your * …. notes of what you
> accomplished. We have JIRA itemizations, but also put them into the
> CHANGELOG too.
>
> In general, every time you commit to a release branch, be sure to add your
> CHANGELOG notes.
>
> Thanks,
> Marko.
>
> http://markorodriguez.com
>
> On Oct 15, 2015, at 8:00 AM, Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > Another quick status check for the 3.0.2 countdown. There are just two
> > issues left open in JIRA on this version. As both are under development
> > right now, I would think we can get them through our new RTC process by
> end
> > of day tomorrow so that I can just wake up with a fresh mind on Monday
> and
> > just head right to the release process. Please yell if you're working on
> > those issues and don't think that is possible for some reason.
> >
> > If you have not done so already, please take a look at our upgrade docs
> and
> > make changes as needed (again, nice to have this all squared away by the
> > weekend):
> >
> >
> https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
> >
> > Thanks,
> >
> > Stephen
> >
> >
> >
> > On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <spmallette@gmail.com
> >
> > wrote:
> >
> >> Hi all, just a quick reminder that we're about a week a way from getting
> >> the 3.0.2 release process going. As you may have noted from another
> thread
> >> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
> >> preparation for that release. Looks like we are down to just three open
> >> issues with 3.0.2. :)
> >>
> >> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <sp...@gmail.com>
> >> wrote:
> >>
> >>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I
> just
> >>> completed that bug fix to 870 which was pretty simple after all the
> work I
> >>> had to do to just initially identify the problem.
> >>>
> >>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru>
> wrote:
> >>>
> >>>> I'm currently working on 852, I think I will be done today/tomorrow.
> Once
> >>>> that's done, I can work on 319 - this only means: verify that the
> >>>> TinkerGraph persistence works well with BLVP and write
> unit/integration
> >>>> tests for it. The other pending things in 319 are subject to 3.1.0.
> >>>>
> >>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve
> it
> >>>> (unless someone else comes up with some ideas).
> >>>>
> >>>> Cheers,
> >>>> Daniel
> >>>>
> >>>>
> >>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <
> spmallette@gmail.com>
> >>>> wrote:
> >>>>
> >>>>> There are currently 5 unresolved issues assigned to 3.0.2:
> >>>>> http://bit.ly/1Q7Ez8O
> >>>>>
> >>>>> In summary we have:
> >>>>>
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
> >>>>> probably
> >>>>> me/Kuppitz)
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
> >>>>>
> >>>>> My point in bringing these up is to open up dialog on any issues with
> >>>> these
> >>>>> final tickets as we'd previously discussed closing the doors on 3.0.2
> >>>> on
> >>>>> 10/19. I'd also like to ask if anyone is aware of any other critical
> >>>>> issues not on the general 3.0.2 list - if so, please raise them for
> >>>>> discussion.
> >>>>>
> >>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm
> not
> >>>>> really clear what we need to do. Mr. Kuppitz, can you help us come
> to
> >>>> some
> >>>>> concrete steps to take for that issue please? If time is an issue
> and
> >>>> you
> >>>>> have SEO research to do, let's consider pushing this issue forward to
> >>>> 3.1.0
> >>>>> and get stuff right at that point. Any SEO folks on the list who can
> >>>> help
> >>>>> on that one?
> >>>>>
> >>>>> I'd also like to make sure the road is clear to finish up 319. As I
> >>>>> recall, that issue was blocked by:
> >>>>>
> >>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828
> >>>>>
> >>>>> but that is complete now, so 319 should be clear. All good there,
> >>>> Daniel?
> >>>>>
> >>>>> Thanks, everyone - Please feel free to chime in with any issues
> >>>> related to
> >>>>> 3.0.2.
> >>>>>
> >>>>
> >>>
> >>>
> >>
>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Marko Rodriguez <ok...@gmail.com>.
Hi,
Everyone, please update the CHANGELOG with your * …. notes of what you accomplished. We have JIRA itemizations, but also put them into the CHANGELOG too.
In general, every time you commit to a release branch, be sure to add your CHANGELOG notes.
Thanks,
Marko.
http://markorodriguez.com
On Oct 15, 2015, at 8:00 AM, Stephen Mallette <sp...@gmail.com> wrote:
> Another quick status check for the 3.0.2 countdown. There are just two
> issues left open in JIRA on this version. As both are under development
> right now, I would think we can get them through our new RTC process by end
> of day tomorrow so that I can just wake up with a fresh mind on Monday and
> just head right to the release process. Please yell if you're working on
> those issues and don't think that is possible for some reason.
>
> If you have not done so already, please take a look at our upgrade docs and
> make changes as needed (again, nice to have this all squared away by the
> weekend):
>
> https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
>
> Thanks,
>
> Stephen
>
>
>
> On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <sp...@gmail.com>
> wrote:
>
>> Hi all, just a quick reminder that we're about a week a way from getting
>> the 3.0.2 release process going. As you may have noted from another thread
>> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
>> preparation for that release. Looks like we are down to just three open
>> issues with 3.0.2. :)
>>
>> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>>
>>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I just
>>> completed that bug fix to 870 which was pretty simple after all the work I
>>> had to do to just initially identify the problem.
>>>
>>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru> wrote:
>>>
>>>> I'm currently working on 852, I think I will be done today/tomorrow. Once
>>>> that's done, I can work on 319 - this only means: verify that the
>>>> TinkerGraph persistence works well with BLVP and write unit/integration
>>>> tests for it. The other pending things in 319 are subject to 3.1.0.
>>>>
>>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it
>>>> (unless someone else comes up with some ideas).
>>>>
>>>> Cheers,
>>>> Daniel
>>>>
>>>>
>>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <sp...@gmail.com>
>>>> wrote:
>>>>
>>>>> There are currently 5 unresolved issues assigned to 3.0.2:
>>>>> http://bit.ly/1Q7Ez8O
>>>>>
>>>>> In summary we have:
>>>>>
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
>>>>> probably
>>>>> me/Kuppitz)
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>>>>>
>>>>> My point in bringing these up is to open up dialog on any issues with
>>>> these
>>>>> final tickets as we'd previously discussed closing the doors on 3.0.2
>>>> on
>>>>> 10/19. I'd also like to ask if anyone is aware of any other critical
>>>>> issues not on the general 3.0.2 list - if so, please raise them for
>>>>> discussion.
>>>>>
>>>>> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
>>>>> really clear what we need to do. Mr. Kuppitz, can you help us come to
>>>> some
>>>>> concrete steps to take for that issue please? If time is an issue and
>>>> you
>>>>> have SEO research to do, let's consider pushing this issue forward to
>>>> 3.1.0
>>>>> and get stuff right at that point. Any SEO folks on the list who can
>>>> help
>>>>> on that one?
>>>>>
>>>>> I'd also like to make sure the road is clear to finish up 319. As I
>>>>> recall, that issue was blocked by:
>>>>>
>>>>> https://issues.apache.org/jira/browse/TINKERPOP3-828
>>>>>
>>>>> but that is complete now, so 319 should be clear. All good there,
>>>> Daniel?
>>>>>
>>>>> Thanks, everyone - Please feel free to chime in with any issues
>>>> related to
>>>>> 3.0.2.
>>>>>
>>>>
>>>
>>>
>>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Another quick status check for the 3.0.2 countdown. There are just two
issues left open in JIRA on this version. As both are under development
right now, I would think we can get them through our new RTC process by end
of day tomorrow so that I can just wake up with a fresh mind on Monday and
just head right to the release process. Please yell if you're working on
those issues and don't think that is possible for some reason.
If you have not done so already, please take a look at our upgrade docs and
make changes as needed (again, nice to have this all squared away by the
weekend):
https://github.com/apache/incubator-tinkerpop/blob/master/docs/src/upgrade-release-3.0.x-incubating.asciidoc
Thanks,
Stephen
On Mon, Oct 12, 2015 at 11:03 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> Hi all, just a quick reminder that we're about a week a way from getting
> the 3.0.2 release process going. As you may have noted from another thread
> I just posted, I'm in the process of reviewing LICENSE/NOTICE in
> preparation for that release. Looks like we are down to just three open
> issues with 3.0.2. :)
>
> On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <sp...@gmail.com>
> wrote:
>
>> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I just
>> completed that bug fix to 870 which was pretty simple after all the work I
>> had to do to just initially identify the problem.
>>
>> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru> wrote:
>>
>>> I'm currently working on 852, I think I will be done today/tomorrow. Once
>>> that's done, I can work on 319 - this only means: verify that the
>>> TinkerGraph persistence works well with BLVP and write unit/integration
>>> tests for it. The other pending things in 319 are subject to 3.1.0.
>>>
>>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it
>>> (unless someone else comes up with some ideas).
>>>
>>> Cheers,
>>> Daniel
>>>
>>>
>>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <sp...@gmail.com>
>>> wrote:
>>>
>>> > There are currently 5 unresolved issues assigned to 3.0.2:
>>> > http://bit.ly/1Q7Ez8O
>>> >
>>> > In summary we have:
>>> >
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
>>> > probably
>>> > me/Kuppitz)
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>>> >
>>> > My point in bringing these up is to open up dialog on any issues with
>>> these
>>> > final tickets as we'd previously discussed closing the doors on 3.0.2
>>> on
>>> > 10/19. I'd also like to ask if anyone is aware of any other critical
>>> > issues not on the general 3.0.2 list - if so, please raise them for
>>> > discussion.
>>> >
>>> > For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
>>> > really clear what we need to do. Mr. Kuppitz, can you help us come to
>>> some
>>> > concrete steps to take for that issue please? If time is an issue and
>>> you
>>> > have SEO research to do, let's consider pushing this issue forward to
>>> 3.1.0
>>> > and get stuff right at that point. Any SEO folks on the list who can
>>> help
>>> > on that one?
>>> >
>>> > I'd also like to make sure the road is clear to finish up 319. As I
>>> > recall, that issue was blocked by:
>>> >
>>> > https://issues.apache.org/jira/browse/TINKERPOP3-828
>>> >
>>> > but that is complete now, so 319 should be clear. All good there,
>>> Daniel?
>>> >
>>> > Thanks, everyone - Please feel free to chime in with any issues
>>> related to
>>> > 3.0.2.
>>> >
>>>
>>
>>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Hi all, just a quick reminder that we're about a week a way from getting
the 3.0.2 release process going. As you may have noted from another thread
I just posted, I'm in the process of reviewing LICENSE/NOTICE in
preparation for that release. Looks like we are down to just three open
issues with 3.0.2. :)
On Thu, Oct 8, 2015 at 8:24 AM, Stephen Mallette <sp...@gmail.com>
wrote:
> Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I just
> completed that bug fix to 870 which was pretty simple after all the work I
> had to do to just initially identify the problem.
>
> On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru> wrote:
>
>> I'm currently working on 852, I think I will be done today/tomorrow. Once
>> that's done, I can work on 319 - this only means: verify that the
>> TinkerGraph persistence works well with BLVP and write unit/integration
>> tests for it. The other pending things in 319 are subject to 3.1.0.
>>
>> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it
>> (unless someone else comes up with some ideas).
>>
>> Cheers,
>> Daniel
>>
>>
>> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <sp...@gmail.com>
>> wrote:
>>
>> > There are currently 5 unresolved issues assigned to 3.0.2:
>> > http://bit.ly/1Q7Ez8O
>> >
>> > In summary we have:
>> >
>> > https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
>> > https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
>> > probably
>> > me/Kuppitz)
>> > https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
>> > https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
>> > https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>> >
>> > My point in bringing these up is to open up dialog on any issues with
>> these
>> > final tickets as we'd previously discussed closing the doors on 3.0.2 on
>> > 10/19. I'd also like to ask if anyone is aware of any other critical
>> > issues not on the general 3.0.2 list - if so, please raise them for
>> > discussion.
>> >
>> > For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
>> > really clear what we need to do. Mr. Kuppitz, can you help us come to
>> some
>> > concrete steps to take for that issue please? If time is an issue and
>> you
>> > have SEO research to do, let's consider pushing this issue forward to
>> 3.1.0
>> > and get stuff right at that point. Any SEO folks on the list who can
>> help
>> > on that one?
>> >
>> > I'd also like to make sure the road is clear to finish up 319. As I
>> > recall, that issue was blocked by:
>> >
>> > https://issues.apache.org/jira/browse/TINKERPOP3-828
>> >
>> > but that is complete now, so 319 should be clear. All good there,
>> Daniel?
>> >
>> > Thanks, everyone - Please feel free to chime in with any issues related
>> to
>> > 3.0.2.
>> >
>>
>
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Stephen Mallette <sp...@gmail.com>.
Ok - moved 838 off of 3.0.1 barring any SEO experts stepping up. I just
completed that bug fix to 870 which was pretty simple after all the work I
had to do to just initially identify the problem.
On Wed, Oct 7, 2015 at 12:59 PM, Daniel Kuppitz <me...@gremlin.guru> wrote:
> I'm currently working on 852, I think I will be done today/tomorrow. Once
> that's done, I can work on 319 - this only means: verify that the
> TinkerGraph persistence works well with BLVP and write unit/integration
> tests for it. The other pending things in 319 are subject to 3.1.0.
>
> Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it
> (unless someone else comes up with some ideas).
>
> Cheers,
> Daniel
>
>
> On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <sp...@gmail.com>
> wrote:
>
> > There are currently 5 unresolved issues assigned to 3.0.2:
> > http://bit.ly/1Q7Ez8O
> >
> > In summary we have:
> >
> > https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
> > https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
> > probably
> > me/Kuppitz)
> > https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
> > https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
> > https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
> >
> > My point in bringing these up is to open up dialog on any issues with
> these
> > final tickets as we'd previously discussed closing the doors on 3.0.2 on
> > 10/19. I'd also like to ask if anyone is aware of any other critical
> > issues not on the general 3.0.2 list - if so, please raise them for
> > discussion.
> >
> > For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
> > really clear what we need to do. Mr. Kuppitz, can you help us come to
> some
> > concrete steps to take for that issue please? If time is an issue and
> you
> > have SEO research to do, let's consider pushing this issue forward to
> 3.1.0
> > and get stuff right at that point. Any SEO folks on the list who can
> help
> > on that one?
> >
> > I'd also like to make sure the road is clear to finish up 319. As I
> > recall, that issue was blocked by:
> >
> > https://issues.apache.org/jira/browse/TINKERPOP3-828
> >
> > but that is complete now, so 319 should be clear. All good there,
> Daniel?
> >
> > Thanks, everyone - Please feel free to chime in with any issues related
> to
> > 3.0.2.
> >
>
Re: [DISCUSS] Remaining Issues on 3.0.2
Posted by Daniel Kuppitz <me...@gremlin.guru>.
I'm currently working on 852, I think I will be done today/tomorrow. Once
that's done, I can work on 319 - this only means: verify that the
TinkerGraph persistence works well with BLVP and write unit/integration
tests for it. The other pending things in 319 are subject to 3.1.0.
Let's push 838 to 3.1.0, since I have absolutely no idea how to solve it
(unless someone else comes up with some ideas).
Cheers,
Daniel
On Wed, Oct 7, 2015 at 5:24 PM, Stephen Mallette <sp...@gmail.com>
wrote:
> There are currently 5 unresolved issues assigned to 3.0.2:
> http://bit.ly/1Q7Ez8O
>
> In summary we have:
>
> https://issues.apache.org/jira/browse/TINKERPOP3-852 (Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-838 (Unassigned -
> probably
> me/Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-319 (Kuppitz)
> https://issues.apache.org/jira/browse/TINKERPOP3-865 (Jason)
> https://issues.apache.org/jira/browse/TINKERPOP3-858 (Jason)
>
> My point in bringing these up is to open up dialog on any issues with these
> final tickets as we'd previously discussed closing the doors on 3.0.2 on
> 10/19. I'd also like to ask if anyone is aware of any other critical
> issues not on the general 3.0.2 list - if so, please raise them for
> discussion.
>
> For me, I'm concerned about 838 which I'm somewhat tied to, but I'm not
> really clear what we need to do. Mr. Kuppitz, can you help us come to some
> concrete steps to take for that issue please? If time is an issue and you
> have SEO research to do, let's consider pushing this issue forward to 3.1.0
> and get stuff right at that point. Any SEO folks on the list who can help
> on that one?
>
> I'd also like to make sure the road is clear to finish up 319. As I
> recall, that issue was blocked by:
>
> https://issues.apache.org/jira/browse/TINKERPOP3-828
>
> but that is complete now, so 319 should be clear. All good there, Daniel?
>
> Thanks, everyone - Please feel free to chime in with any issues related to
> 3.0.2.
>