the sync happens automatically. it is already on github i think. Cheers Lei
On Wed, Jun 22, 2016 at 8:48 AM, Radar Da lei <[email protected]> wrote: > Hi Goden, > > I used branch name as '2.0.0-incubating'. > > BTW, this branch is at Apache side, does this need to be sync to GITHUB? > > Thanks. > > Regards, > Radar > > On Wed, Jun 22, 2016 at 8:40 AM, Ting(Goden) Yao <[email protected]> wrote: > > > I don't see a branch named "hawq 2.0.0-incubating" , which name did you > use > > for the branch? > > > > On Mon, Jun 20, 2016 at 10:21 PM Radar Da lei <[email protected]> wrote: > > > > > Hi Vineet, > > > > > > Quicklz already been removed. I will cut a branch now. > > > > > > Thanks. > > > > > > Regards, > > > Radar > > > > > > On Tue, Jun 21, 2016 at 9:27 AM, Vineet Goel <[email protected]> > wrote: > > > > > > > +1 to the proposed release name and cutting a release branch asap. > > > > Sounds like we need to find a good commit point right after the > Apache > > > > release requirements were met (quicklz removal etc). > > > > > > > > -Vineet > > > > > > > > > > > > > > > > On Mon, Jun 20, 2016 at 2:13 PM, Ting(Goden) Yao <[email protected]> > > > wrote: > > > > > > > > > I can start the voting process - Also I'd like to change the > release > > > name > > > > > to "2.0.0-incubating" , removing the beta tag given we've passed > that > > > > point > > > > > in the timeline. > > > > > I also need help to cut a clean release branch as there's been so > > many > > > > > commits coming in which is not in the original scope - can anyone > who > > > > made > > > > > the commits help me on that? > > > > > > > > > > -Goden > > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 9:37 PM Lei Chang <[email protected]> > > > wrote: > > > > > > > > > > > A summary on the JIRAs left: > > > > > > > > > > > > HAWQ-783: it needs catalog changes, so I think it is better to > put > > it > > > > > into > > > > > > following release and the impact is small. > > > > > > HAWQ-460: resolved since thrift library is in. > > > > > > > > > > > > Looks we are ready to go for voting if no other issues left or > > > > concerns! > > > > > > > > > > > > Cheers > > > > > > Lei > > > > > > > > > > > > > > > > > > On Sat, Jun 18, 2016 at 7:47 AM, Ting(Goden) Yao < > [email protected]> > > > > > wrote: > > > > > > > > > > > > > I still have concerns that left out HAWQ-783 is not a clean cut > > for > > > > > this > > > > > > > release. > > > > > > > Guo - can you shed some light on what's the impact of leaving > > this > > > to > > > > > the > > > > > > > future? > > > > > > > I may also go through the previous commits and understand the > > > > changes. > > > > > > > > > > > > > > On Fri, Jun 17, 2016 at 4:26 PM Roman Shaposhnik < > > > > [email protected] > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > On Thu, Jun 16, 2016 at 6:58 PM, Guo Gang <[email protected] > > > > > > wrote: > > > > > > > > > HAWQ-783 (Remove quickly in metadata) is a JIRA for future > > > work. > > > > > This > > > > > > > is > > > > > > > > not > > > > > > > > > for the shortcoming next release. Please remove the jira > from > > > the > > > > > > > > blocking > > > > > > > > > lists. > > > > > > > > > > > > > > > > Ok, if we're down to HAWQ-460 as the only release blocker, > can > > > > > somebody > > > > > > > > please > > > > > > > > provide an update? The last comment on the JIRA was more > than a > > > > month > > > > > > > ago. > > > > > > > > > > > > > > > > Thanks, > > > > > > > > Roman. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
