You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@predictionio.apache.org by Pat Ferrel <pa...@occamsmachete.com> on 2017/05/18 20:49:55 UTC
PIO 0.12.0 and Graduation Time?
Should we apply for graduation to Apache TLP soon, like maybe the next release? I started a Google doc for features we want and any Mentors can add things we need to demonstrate for graduation since some may not be Jira-able.
All user’s should feel free to input.
https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
Re: PIO 0.12.0 and Graduation Time?
Posted by Andrew Purtell <ap...@apache.org>.
Sure, you can always ask. Someone might volunteer their time .
On Mon, Jun 5, 2017 at 11:04 AM, Donald Szeto <do...@apache.org> wrote:
> Hey Andrew, is it possible for us to create non-release binary
> distributions and ask Incubator PMC to help take a look without starting a
> voting thread? This would allow us iron out issues in parallel to working
> on 0.12.
>
> On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell <ap...@apache.org>
> wrote:
>
>> Really glad to see this discussion started, because I think your podling
>> is nearing graduation. The most important determination of that is taking
>> the initiative to propose it.
>>
>> I looked over the spreadsheet and have only this comment: You'll gain
>> from having the incubator picking over your binary artifact release
>> attempt, the first time you try to put one together. You won't have that
>> after graduation. I recommend working through binary artifacts as part of
>> 0.12, then proposing yourselves for graduation.
>>
>>
>> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>
>>> Should we apply for graduation to Apache TLP soon, like maybe the next
>>> release? I started a Google doc for features we want and any Mentors can
>>> add things we need to demonstrate for graduation since some may not be
>>> Jira-able.
>>>
>>> All user’s should feel free to input.
>>>
>>> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>>
>>
>>
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> If you are given a choice, you believe you have acted freely. - Raymond
>> Teller (via Peter Watts)
>>
>
>
--
Best regards,
- Andy
If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)
Re: PIO 0.12.0 and Graduation Time?
Posted by Andrew Purtell <ap...@apache.org>.
Sure, you can always ask. Someone might volunteer their time .
On Mon, Jun 5, 2017 at 11:04 AM, Donald Szeto <do...@apache.org> wrote:
> Hey Andrew, is it possible for us to create non-release binary
> distributions and ask Incubator PMC to help take a look without starting a
> voting thread? This would allow us iron out issues in parallel to working
> on 0.12.
>
> On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell <ap...@apache.org>
> wrote:
>
>> Really glad to see this discussion started, because I think your podling
>> is nearing graduation. The most important determination of that is taking
>> the initiative to propose it.
>>
>> I looked over the spreadsheet and have only this comment: You'll gain
>> from having the incubator picking over your binary artifact release
>> attempt, the first time you try to put one together. You won't have that
>> after graduation. I recommend working through binary artifacts as part of
>> 0.12, then proposing yourselves for graduation.
>>
>>
>> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com>
>> wrote:
>>
>>> Should we apply for graduation to Apache TLP soon, like maybe the next
>>> release? I started a Google doc for features we want and any Mentors can
>>> add things we need to demonstrate for graduation since some may not be
>>> Jira-able.
>>>
>>> All user’s should feel free to input.
>>>
>>> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>>
>>
>>
>>
>> --
>> Best regards,
>>
>> - Andy
>>
>> If you are given a choice, you believe you have acted freely. - Raymond
>> Teller (via Peter Watts)
>>
>
>
--
Best regards,
- Andy
If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)
Re: PIO 0.12.0 and Graduation Time?
Posted by Donald Szeto <do...@apache.org>.
Hey Andrew, is it possible for us to create non-release binary
distributions and ask Incubator PMC to help take a look without starting a
voting thread? This would allow us iron out issues in parallel to working
on 0.12.
On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell <ap...@apache.org> wrote:
> Really glad to see this discussion started, because I think your podling
> is nearing graduation. The most important determination of that is taking
> the initiative to propose it.
>
> I looked over the spreadsheet and have only this comment: You'll gain from
> having the incubator picking over your binary artifact release attempt, the
> first time you try to put one together. You won't have that after
> graduation. I recommend working through binary artifacts as part of 0.12,
> then proposing yourselves for graduation.
>
>
> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> Should we apply for graduation to Apache TLP soon, like maybe the next
>> release? I started a Google doc for features we want and any Mentors can
>> add things we need to demonstrate for graduation since some may not be
>> Jira-able.
>>
>> All user’s should feel free to input.
>>
>> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
>
>
>
> --
> Best regards,
>
> - Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>
Re: PIO 0.12.0 and Graduation Time?
Posted by Donald Szeto <do...@apache.org>.
Hey Andrew, is it possible for us to create non-release binary
distributions and ask Incubator PMC to help take a look without starting a
voting thread? This would allow us iron out issues in parallel to working
on 0.12.
On Wed, May 31, 2017 at 9:08 AM, Andrew Purtell <ap...@apache.org> wrote:
> Really glad to see this discussion started, because I think your podling
> is nearing graduation. The most important determination of that is taking
> the initiative to propose it.
>
> I looked over the spreadsheet and have only this comment: You'll gain from
> having the incubator picking over your binary artifact release attempt, the
> first time you try to put one together. You won't have that after
> graduation. I recommend working through binary artifacts as part of 0.12,
> then proposing yourselves for graduation.
>
>
> On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
>> Should we apply for graduation to Apache TLP soon, like maybe the next
>> release? I started a Google doc for features we want and any Mentors can
>> add things we need to demonstrate for graduation since some may not be
>> Jira-able.
>>
>> All user’s should feel free to input.
>>
>> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
>> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
>
>
>
> --
> Best regards,
>
> - Andy
>
> If you are given a choice, you believe you have acted freely. - Raymond
> Teller (via Peter Watts)
>
Re: PIO 0.12.0 and Graduation Time?
Posted by Andrew Purtell <ap...@apache.org>.
Really glad to see this discussion started, because I think your podling is
nearing graduation. The most important determination of that is taking the
initiative to propose it.
I looked over the spreadsheet and have only this comment: You'll gain from
having the incubator picking over your binary artifact release attempt, the
first time you try to put one together. You won't have that after
graduation. I recommend working through binary artifacts as part of 0.12,
then proposing yourselves for graduation.
On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Should we apply for graduation to Apache TLP soon, like maybe the next
> release? I started a Google doc for features we want and any Mentors can
> add things we need to demonstrate for graduation since some may not be
> Jira-able.
>
> All user’s should feel free to input.
>
> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
--
Best regards,
- Andy
If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)
Re: PIO 0.12.0 and Graduation Time?
Posted by Andrew Purtell <ap...@apache.org>.
Really glad to see this discussion started, because I think your podling is
nearing graduation. The most important determination of that is taking the
initiative to propose it.
I looked over the spreadsheet and have only this comment: You'll gain from
having the incubator picking over your binary artifact release attempt, the
first time you try to put one together. You won't have that after
graduation. I recommend working through binary artifacts as part of 0.12,
then proposing yourselves for graduation.
On Thu, May 18, 2017 at 1:49 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
> Should we apply for graduation to Apache TLP soon, like maybe the next
> release? I started a Google doc for features we want and any Mentors can
> add things we need to demonstrate for graduation since some may not be
> Jira-able.
>
> All user’s should feel free to input.
>
> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
--
Best regards,
- Andy
If you are given a choice, you believe you have acted freely. - Raymond
Teller (via Peter Watts)
Re: Host PIO on Github (not ASF Git)
Posted by Jeff Zhang <zj...@gmail.com>.
AFAIK, some apache projects (spark/zeppelin) use github as mirror but
still based on apache git. People can still use github to submit/review PR.
But they need to call a script to merget this PR.
See https://github.com/apache/zeppelin/blob/master/dev/merge_zeppelin_pr.py
Pat Ferrel <pa...@occamsmachete.com>于2017年5月20日周六 上午12:42写道：
> https://issues.apache.org/jira/browse/INFRA-14191
>
>
> On May 18, 2017, at 4:56 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> Heard it from Mahout. I agree it’s not completely clear. Unless someone
> can illuminate us I’ll follow up with infra and report back.
>
> BTW I forgot my ASF login, does anyone remember the ASF site for forgotten
> passwords?
>
>
> On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
>
> It is not clear to me from the gitbox page that we can move our source out
> of ASF controlled servers and still be covered by ASF Legal. It's a pretty
> big change if true. Did I miss an announcement from ASF?
>
> Personally am happy to have things on GitHub because the flow would be a
> lot simpler.
>
> On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
>
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Jeff Zhang <zj...@gmail.com>.
AFAIK, some apache projects (spark/zeppelin) use github as mirror but
still based on apache git. People can still use github to submit/review PR.
But they need to call a script to merget this PR.
See https://github.com/apache/zeppelin/blob/master/dev/merge_zeppelin_pr.py
Pat Ferrel <pa...@occamsmachete.com>于2017年5月20日周六 上午12:42写道：
> https://issues.apache.org/jira/browse/INFRA-14191
>
>
> On May 18, 2017, at 4:56 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> Heard it from Mahout. I agree it’s not completely clear. Unless someone
> can illuminate us I’ll follow up with infra and report back.
>
> BTW I forgot my ASF login, does anyone remember the ASF site for forgotten
> passwords?
>
>
> On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
>
> It is not clear to me from the gitbox page that we can move our source out
> of ASF controlled servers and still be covered by ASF Legal. It's a pretty
> big change if true. Did I miss an announcement from ASF?
>
> Personally am happy to have things on GitHub because the flow would be a
> lot simpler.
>
> On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
>
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
https://issues.apache.org/jira/browse/INFRA-14191 <https://issues.apache.org/jira/browse/INFRA-14191>
On May 18, 2017, at 4:56 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow up with infra and report back.
BTW I forgot my ASF login, does anyone remember the ASF site for forgotten passwords?
On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
https://issues.apache.org/jira/browse/INFRA-14191 <https://issues.apache.org/jira/browse/INFRA-14191>
On May 18, 2017, at 4:56 PM, Pat Ferrel <pa...@occamsmachete.com> wrote:
Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow up with infra and report back.
BTW I forgot my ASF login, does anyone remember the ASF site for forgotten passwords?
On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow up with infra and report back.
BTW I forgot my ASF login, does anyone remember the ASF site for forgotten passwords?
On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
Heard it from Mahout. I agree it’s not completely clear. Unless someone can illuminate us I’ll follow up with infra and report back.
BTW I forgot my ASF login, does anyone remember the ASF site for forgotten passwords?
On May 18, 2017, at 4:05 PM, Donald Szeto <do...@apache.org> wrote:
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Donald Szeto <do...@apache.org>.
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Re: Host PIO on Github (not ASF Git)
Posted by Donald Szeto <do...@apache.org>.
It is not clear to me from the gitbox page that we can move our source out
of ASF controlled servers and still be covered by ASF Legal. It's a pretty
big change if true. Did I miss an announcement from ASF?
Personally am happy to have things on GitHub because the flow would be a
lot simpler.
On Thu, May 18, 2017 at 3:26 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> BTW there seems now to be a way to host on Github (not ASF Git) by linking
> our ASF accounts to our git accounts. This would make a bunch of things
> much easier like PRs can be reviewed and merged directly, direct merging
> of doc changes by users, lots of nice stuff that is GUI related. This
> would open up a whole new toolchain unless there are some hidden
> restrictions and unless I’m misreading something.
>
> https://gitbox.apache.org/
>
> Even given the risk of GH going down I’d take it over forcing the poor
> Infra people to guarantee some SLA for our own git servers. They must have
> a zillion more interesting things to do.
>
> I’d be happy to shepherd the Infra Jira if people want this. What do
> people think?
>
>
Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
BTW there seems now to be a way to host on Github (not ASF Git) by linking our ASF accounts to our git accounts. This would make a bunch of things much easier like PRs can be reviewed and merged directly, direct merging of doc changes by users, lots of nice stuff that is GUI related. This would open up a whole new toolchain unless there are some hidden restrictions and unless I’m misreading something.
https://gitbox.apache.org/ <https://gitbox.apache.org/>
Even given the risk of GH going down I’d take it over forcing the poor Infra people to guarantee some SLA for our own git servers. They must have a zillion more interesting things to do.
I’d be happy to shepherd the Infra Jira if people want this. What do people think?
Re: PIO 0.12.0 and Graduation Time?
Posted by Sara Asher <sa...@salesforce.com>.
Hi everyone,
I've put all the 0.12 requests into JIRA. Right now we have 21 tickets -
this includes both the ones people added to this doc and tickets that had
previously been tagged for 0.12.
As far as I can tell, the only tickets we should complete for graduation
are documentation / procedural fixes. If that's true, we can start the
graduation process as soon as those tickets are ready and and work on
graduating in parallel to preparing 0.12.
In Pat's doc, I listed the jira tickets and added a column for "Needed for
graduation". Are there other tickets that people feel we need to finish
before starting the graduation process? If so, please update the document
so we can discuss and make a decision on timing for graduation.
Finally, it's seems people are okay with the 2 month release cycle. I
propose we target 7/31 as the release date for 0.12. Thoughts?
Regards,
Sara
On Sat, May 20, 2017 at 12:14 PM, Donald Szeto <do...@apache.org> wrote:
> Thanks Pat for starting this. Added some edits to it. Everyone please feel
> free to comment. PMCs please feel free to request edit access.
>
> Very happy that we started the discussion!
>
> On Thu, May 18, 2017 at 1:50 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > Should we apply for graduation to Apache TLP soon, like maybe the next
> > release? I started a Google doc for features we want and any Mentors can
> > add things we need to demonstrate for graduation since some may not be
> > Jira-able.
> >
> > All user’s should feel free to input.
> >
> >
> > https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
Re: PIO 0.12.0 and Graduation Time?
Posted by Sara Asher <sa...@salesforce.com>.
Hi everyone,
I've put all the 0.12 requests into JIRA. Right now we have 21 tickets -
this includes both the ones people added to this doc and tickets that had
previously been tagged for 0.12.
As far as I can tell, the only tickets we should complete for graduation
are documentation / procedural fixes. If that's true, we can start the
graduation process as soon as those tickets are ready and and work on
graduating in parallel to preparing 0.12.
In Pat's doc, I listed the jira tickets and added a column for "Needed for
graduation". Are there other tickets that people feel we need to finish
before starting the graduation process? If so, please update the document
so we can discuss and make a decision on timing for graduation.
Finally, it's seems people are okay with the 2 month release cycle. I
propose we target 7/31 as the release date for 0.12. Thoughts?
Regards,
Sara
On Sat, May 20, 2017 at 12:14 PM, Donald Szeto <do...@apache.org> wrote:
> Thanks Pat for starting this. Added some edits to it. Everyone please feel
> free to comment. PMCs please feel free to request edit access.
>
> Very happy that we started the discussion!
>
> On Thu, May 18, 2017 at 1:50 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > Should we apply for graduation to Apache TLP soon, like maybe the next
> > release? I started a Google doc for features we want and any Mentors can
> > add things we need to demonstrate for graduation since some may not be
> > Jira-able.
> >
> > All user’s should feel free to input.
> >
> >
> > https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
Re: PIO 0.12.0 and Graduation Time?
Posted by Naoki Takezoe <ta...@gmail.com>.
> I'm working on improving batch/events.json endpoint performance
> by modifying it to use Elasticsearch bulk indexing or JDBC batch inserting.
Created a ticket on JIRA:
https://issues.apache.org/jira/browse/PIO-90
and pull request is here:
https://github.com/apache/incubator-predictionio/pull/386
--
Naoki Takezoe
Re: PIO 0.12.0 and Graduation Time?
Posted by Naoki Takezoe <ta...@gmail.com>.
> I'm working on improving batch/events.json endpoint performance
> by modifying it to use Elasticsearch bulk indexing or JDBC batch inserting.
Created a ticket on JIRA:
https://issues.apache.org/jira/browse/PIO-90
and pull request is here:
https://github.com/apache/incubator-predictionio/pull/386
--
Naoki Takezoe
Re: PIO 0.12.0 and Graduation Time?
Posted by Naoki Takezoe <ta...@gmail.com>.
I'm working on improving batch/events.json endpoint performance
by modifying it to use Elasticsearch bulk indexing or JDBC batch inserting.
This is not necessary for graduation, but I hope to put this into 0.12.
> Finally, it's seems people are okay with the 2 month release cycle. I
> propose we target 7/31 as the release date for 0.12. Thoughts?
Anyway, +1 for 7/31 is the release date for 0.12.
--
Naoki Takezoe
Re: PIO 0.12.0 and Graduation Time?
Posted by Naoki Takezoe <ta...@gmail.com>.
I'm working on improving batch/events.json endpoint performance
by modifying it to use Elasticsearch bulk indexing or JDBC batch inserting.
This is not necessary for graduation, but I hope to put this into 0.12.
> Finally, it's seems people are okay with the 2 month release cycle. I
> propose we target 7/31 as the release date for 0.12. Thoughts?
Anyway, +1 for 7/31 is the release date for 0.12.
--
Naoki Takezoe
Re: PIO 0.12.0 and Graduation Time?
Posted by Sara Asher <sa...@gmail.com>.
Hi everyone,
I've put all the 0.12 requests into JIRA. Right now we have 21 tickets -
this includes both the ones people added to this doc and tickets that had
previously been tagged for 0.12.
As far as I can tell, the only tickets we should complete for graduation
are documentation / procedural fixes. If that's true, we can start the
graduation process as soon as those tickets are ready and and work on
graduating in parallel to preparing 0.12.
In Pat's doc, I listed the jira tickets and added a column for "Needed for
graduation". Are there other tickets that people feel we need to finish
before starting the graduation process? If so, please update the document
so we can discuss and make a decision on timing for graduation.
Finally, it's seems people are okay with the 2 month release cycle. I
propose we target 7/31 as the release date for 0.12. Thoughts?
Regards,
Sara
On Thu, May 25, 2017 at 10:25 PM, Sara Asher <sa...@salesforce.com>
wrote:
>
> ---------- Forwarded message ----------
> From: Donald Szeto <do...@apache.org>
> Date: Sat, May 20, 2017 at 12:14 PM
> Subject: Re: PIO 0.12.0 and Graduation Time?
> To: dev@predictionio.incubator.apache.org, user@predictionio.incubator.
> apache.org
>
>
> Thanks Pat for starting this. Added some edits to it. Everyone please feel
> free to comment. PMCs please feel free to request edit access.
>
> Very happy that we started the discussion!
>
> On Thu, May 18, 2017 at 1:50 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
>
> > Should we apply for graduation to Apache TLP soon, like maybe the next
> > release? I started a Google doc for features we want and any Mentors can
> > add things we need to demonstrate for graduation since some may not be
> > Jira-able.
> >
> > All user’s should feel free to input.
> >
> >
> > https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-
> 1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
>
>
Re: PIO 0.12.0 and Graduation Time?
Posted by Donald Szeto <do...@apache.org>.
Thanks Pat for starting this. Added some edits to it. Everyone please feel
free to comment. PMCs please feel free to request edit access.
Very happy that we started the discussion!
On Thu, May 18, 2017 at 1:50 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> Should we apply for graduation to Apache TLP soon, like maybe the next
> release? I started a Google doc for features we want and any Mentors can
> add things we need to demonstrate for graduation since some may not be
> Jira-able.
>
> All user’s should feel free to input.
>
>
> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-1SwIJBkEonH3Yw4T6pY/edit?usp=sharing
Host PIO on Github (not ASF Git)
Posted by Pat Ferrel <pa...@occamsmachete.com>.
BTW there seems now to be a way to host on Github (not ASF Git) by linking our ASF accounts to our git accounts. This would make a bunch of things much easier like PRs can be reviewed and merged directly, direct merging of doc changes by users, lots of nice stuff that is GUI related. This would open up a whole new toolchain unless there are some hidden restrictions and unless I’m misreading something.
https://gitbox.apache.org/ <https://gitbox.apache.org/>
Even given the risk of GH going down I’d take it over forcing the poor Infra people to guarantee some SLA for our own git servers. They must have a zillion more interesting things to do.
I’d be happy to shepherd the Infra Jira if people want this. What do people think?
Re: PIO 0.12.0 and Graduation Time?
Posted by Donald Szeto <do...@apache.org>.
Thanks Pat for starting this. Added some edits to it. Everyone please feel
free to comment. PMCs please feel free to request edit access.
Very happy that we started the discussion!
On Thu, May 18, 2017 at 1:50 PM Pat Ferrel <pa...@occamsmachete.com> wrote:
> Should we apply for graduation to Apache TLP soon, like maybe the next
> release? I started a Google doc for features we want and any Mentors can
> add things we need to demonstrate for graduation since some may not be
> Jira-able.
>
> All user’s should feel free to input.
>
>
> https://docs.google.com/document/d/1LTlzxH_CcWi67p8kCQPfPyu-1SwIJBkEonH3Yw4T6pY/edit?usp=sharing