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" <[email protected]> wrote: >+1 on creating new branch for working on this change. > >~Rajesh.B > >On Fri, Dec 4, 2015 at 4:13 AM, Siddharth Seth <[email protected]> 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 <[email protected]> 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 < >> > [email protected]> 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 >> > >> > >>
