Could you please take a stab at dividing the license check work among the volunteers?
-----Original Message----- From: Hitesh Shah [mailto:[email protected]] Sent: Tuesday, July 07, 2015 10:39 AM To: [email protected] Subject: Re: [DISCUSS] Branch for TEZ-2592? Thanks folks. I will get started on creating the branch and seeding it with an initial patch that I had. We can probably follow a commit then review process for this branch initially and do a full review of the licenses before the final merge to master. @Jeff, to answer your question, this branch would created from master. After a merge back to master, we can backport to 0.7 and use that for the first try for creating binary artifacts. thanks - Hitesh On Jul 7, 2015, at 2:10 AM, Rajesh Balamohan <[email protected]> wrote: > +1. I can help. > > ~Rajesh.B > > On Tue, Jul 7, 2015 at 2:24 PM, Prakash Ramachandran < > [email protected]> wrote: > >> +1 can help >> >> >> >> >> On 7/7/15, 5:00 AM, "Jianfeng (Jeff) Zhang" <[email protected]> >> wrote: >> >>> >>> +1. I can help with manual license checks too. >>> >>> BTW, which branch will this base on ? 0.6 or 0.7 ? >>> >>> >>> >>> Best Regard, >>> Jeff Zhang >>> >>> >>> >>> >>> >>> On 7/7/15, 3:08 AM, "Bikas Saha" <[email protected]> wrote: >>> >>>> +1. I can help with the manual license checks. >>>> >>>> Folks, please also reply mentioning if you can volunteer with some >>>> manual license checks. >>>> >>>> Once we have a volunteer list, perhaps Hitesh could help divide the >>>> jars between volunteers so that we can make quick progress. >>>> >>>> Bikas >>>> >>>> -----Original Message----- >>>> From: Hitesh Shah [mailto:[email protected]] >>>> Sent: Monday, July 06, 2015 11:54 AM >>>> To: [email protected] >>>> Subject: [DISCUSS] Branch for TEZ-2592? >>>> >>>> Hello folks, >>>> >>>> TEZ-2592 is an umbrella jira to track the work needed to make it >>>> easier to generate binary artifacts for user convenience. Given the >>>> work involved, it will likely need help from multiple volunteers to >>>> vet all the dependencies/licenses, etc in addition to all the basic >>>> scripting work to help release managers. With that in mind, I >>>> propose that we create a branch for this work and start looking to >>>> progress on making it easier for users to deploy Tez in various >>>> environments without needing to go through the full build cycle. >>>> >>>> Comments? >>>> >>>> thanks >>>> - Hitesh >>> >> > > > > -- > ~Rajesh.B
