You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tez.apache.org by Sreenath Somarajapuram <sr...@apache.org> on 2016/02/11 14:07:14 UTC
Re: [DISCUSS] Merging Tez UI 2 from TEZ-2980 to master
Hi All,
I would like to notify that Tez UI v2 is in parity with Tez UI v1. All the
required functionalities have been committed, and new features are in
pipeline.
Developments until now was tracked under the umbrella ticket -
https://issues.apache.org/jira/browse/TEZ-2980
Future developments will be tracked under -
https://issues.apache.org/jira/browse/TEZ-3106
Until now v2 development had been happening under TEZ-2980 branch, and
feel this might be the right time to merge it to master.
The initial merge can just put v2 into master. Eventually before the next
release, and after more testing v1 can be replaced with v2.
Please share your thoughts.
Thank you,
Sreenath
On 1/23/16, 2:35 AM, "Sreenath Somarajapuram"
<ssomarajapuram@hortonworks.com on behalf of sree@apache.org> wrote:
>Hi All,
>
>A new version of Tez UI is taking form under branch TEZ-2980. All the
>basic functionalities are in.
>
>Set-up instruction can be found at
>https://github.com/apache/tez/tree/TEZ-2980/tez-ui2
>All the work is tracked under
>https://issues.apache.org/jira/browse/TEZ-2980
>
>Please try, and share your thoughts.
>
>
>Thanks,
>Sreenath
>
>On 12/15/15, 5:30 PM, "Sreenath Somarajapuram" <sr...@apache.org> wrote:
>
>>Hi All,
>>
>>This mail is to notify that branch TEZ-2980 was created, and all the
>>changes made to the branch would be tracked under TEZ-2980.
>>The changes would reside under a new module named tez-ui2 under tez
>>directory.
>>
>>As conveyed in the previous mail, the plan is to go for a "commit and
>>then
>>review approach². A complete review would happen at the end, and the
>>branch would be merged back to master on getting 3 +1s.
>>
>>Thanks,
>>Sreenath
>>
>>On 12/9/15, 11:23 PM, "Sreenath Somarajapuram"
>><ssomarajapuram@hortonworks.com on behalf of sree@apache.org> wrote:
>>
>>>Hi,
>>>
>>>Thanks you Hitesh, Siddharth & Rajesh.
>>>
>>>Please find the umbrella jira for this task at
>>>https://issues.apache.org/jira/browse/TEZ-2980.
>>>
>>>Current plan is to go for a "commit and then review approach" to ease
>>>the
>>>development process.
>>>A new branch would be created for the changes by tomorrow EOD, and the
>>>changes would be added to a new module named "tez-ui2" under tez.
>>>
>>>
>>>Please let me know your comments and concerns.
>>>
>>>
>>>Thanks,
>>>Sreenath
>>>
>>>On 12/4/15, 5:25 AM, "Rajesh Balamohan" <rb...@apache.org> wrote:
>>>
>>>>+1 on creating new branch for working on this change.
>>>>
>>>>~Rajesh.B
>>>>
>>>>On Fri, Dec 4, 2015 at 4:13 AM, Siddharth Seth <ss...@apache.org>
>>>>wrote:
>>>>
>>>>> +1 for using a branch if it's a complicated change. One thing to note
>>>>>is
>>>>> that rebasing branches may not be possible anymore.
>>>>>
>>>>> On Tue, Dec 1, 2015 at 8:42 AM, Hitesh Shah <hi...@apache.org>
>>>>>wrote:
>>>>>
>>>>> > +1 on the idea.
>>>>> >
>>>>> > Given this is a major change and if it cannot be done in a single
>>>>>commit,
>>>>> > I would recommend doing these changes on a branch similar to the
>>>>>work
>>>>>for
>>>>> > TEZ-2003.
>>>>> >
>>>>> > thanks
>>>>> > ‹ Hitesh
>>>>> >
>>>>> >
>>>>> > On Nov 30, 2015, at 10:57 PM, Sreenath Somarajapuram <
>>>>> > ssomarajapuram@hortonworks.com> wrote:
>>>>> >
>>>>> > > Hi All,
>>>>> > >
>>>>> > > As many of you know, Tez UI is build over a JavaScript
>>>>>application
>>>>> > framework named Ember js.
>>>>> > > The framework version that we use currently (1.7) is getting
>>>>>obsolete.
>>>>> > So was wondering about migrating UI code to the latest (2.2)
>>>>>version.
>>>>> > > Please share your thoughts on the same.
>>>>> > >
>>>>> > > Cheers,
>>>>> > > Sreenath
>>>>> >
>>>>> >
>>
>>
Re: [DISCUSS] Merging Tez UI 2 from TEZ-2980 to master
Posted by Sreenath Somarajapuram <sr...@apache.org>.
Hi All,
Given that there are no comments, hope I can assume that things are well
and good.
Shortly I’l start a voting mail thread to merge to master from TEZ-2980.
All the changes are in a separate directory, and the merge will not affect
tez-ui or any other module in the project.
Later on v1 can be replaced with v2.
Thanks,
Sreenath
On 2/11/16, 6:37 PM, "Sreenath Somarajapuram" <sr...@apache.org> wrote:
>Hi All,
>
>I would like to notify that Tez UI v2 is in parity with Tez UI v1. All
>the
>required functionalities have been committed, and new features are in
>pipeline.
>Developments until now was tracked under the umbrella ticket -
>https://issues.apache.org/jira/browse/TEZ-2980
>Future developments will be tracked under -
>https://issues.apache.org/jira/browse/TEZ-3106
>
>Until now v2 development had been happening under TEZ-2980 branch, and
>feel this might be the right time to merge it to master.
>The initial merge can just put v2 into master. Eventually before the next
>release, and after more testing v1 can be replaced with v2.
>
>Please share your thoughts.
>
>Thank you,
>Sreenath
>
>On 1/23/16, 2:35 AM, "Sreenath Somarajapuram"
><ssomarajapuram@hortonworks.com on behalf of sree@apache.org> wrote:
>
>>Hi All,
>>
>>A new version of Tez UI is taking form under branch TEZ-2980. All the
>>basic functionalities are in.
>>
>>Set-up instruction can be found at
>>https://github.com/apache/tez/tree/TEZ-2980/tez-ui2
>>All the work is tracked under
>>https://issues.apache.org/jira/browse/TEZ-2980
>>
>>Please try, and share your thoughts.
>>
>>
>>Thanks,
>>Sreenath
>>
>>On 12/15/15, 5:30 PM, "Sreenath Somarajapuram" <sr...@apache.org> wrote:
>>
>>>Hi All,
>>>
>>>This mail is to notify that branch TEZ-2980 was created, and all the
>>>changes made to the branch would be tracked under TEZ-2980.
>>>The changes would reside under a new module named tez-ui2 under tez
>>>directory.
>>>
>>>As conveyed in the previous mail, the plan is to go for a "commit and
>>>then
>>>review approach². A complete review would happen at the end, and the
>>>branch would be merged back to master on getting 3 +1s.
>>>
>>>Thanks,
>>>Sreenath
>>>
>>>On 12/9/15, 11:23 PM, "Sreenath Somarajapuram"
>>><ssomarajapuram@hortonworks.com on behalf of sree@apache.org> wrote:
>>>
>>>>Hi,
>>>>
>>>>Thanks you Hitesh, Siddharth & Rajesh.
>>>>
>>>>Please find the umbrella jira for this task at
>>>>https://issues.apache.org/jira/browse/TEZ-2980.
>>>>
>>>>Current plan is to go for a "commit and then review approach" to ease
>>>>the
>>>>development process.
>>>>A new branch would be created for the changes by tomorrow EOD, and the
>>>>changes would be added to a new module named "tez-ui2" under tez.
>>>>
>>>>
>>>>Please let me know your comments and concerns.
>>>>
>>>>
>>>>Thanks,
>>>>Sreenath
>>>>
>>>>On 12/4/15, 5:25 AM, "Rajesh Balamohan" <rb...@apache.org> wrote:
>>>>
>>>>>+1 on creating new branch for working on this change.
>>>>>
>>>>>~Rajesh.B
>>>>>
>>>>>On Fri, Dec 4, 2015 at 4:13 AM, Siddharth Seth <ss...@apache.org>
>>>>>wrote:
>>>>>
>>>>>> +1 for using a branch if it's a complicated change. One thing to
>>>>>>note
>>>>>>is
>>>>>> that rebasing branches may not be possible anymore.
>>>>>>
>>>>>> On Tue, Dec 1, 2015 at 8:42 AM, Hitesh Shah <hi...@apache.org>
>>>>>>wrote:
>>>>>>
>>>>>> > +1 on the idea.
>>>>>> >
>>>>>> > Given this is a major change and if it cannot be done in a single
>>>>>>commit,
>>>>>> > I would recommend doing these changes on a branch similar to the
>>>>>>work
>>>>>>for
>>>>>> > TEZ-2003.
>>>>>> >
>>>>>> > thanks
>>>>>> > ‹ Hitesh
>>>>>> >
>>>>>> >
>>>>>> > On Nov 30, 2015, at 10:57 PM, Sreenath Somarajapuram <
>>>>>> > ssomarajapuram@hortonworks.com> wrote:
>>>>>> >
>>>>>> > > Hi All,
>>>>>> > >
>>>>>> > > As many of you know, Tez UI is build over a JavaScript
>>>>>>application
>>>>>> > framework named Ember js.
>>>>>> > > The framework version that we use currently (1.7) is getting
>>>>>>obsolete.
>>>>>> > So was wondering about migrating UI code to the latest (2.2)
>>>>>>version.
>>>>>> > > Please share your thoughts on the same.
>>>>>> > >
>>>>>> > > Cheers,
>>>>>> > > Sreenath
>>>>>> >
>>>>>> >
>>>