Oops, sorry I didn't aware of that. I guess you plan to push that commit by your local 1.1-snapshot master and 1.0, but since I've pushed a different commit in the master, you're forced to rebase them. I apologize. Next time I'll read your message twice before pushing.
2015-05-30 14:56 GMT+08:00 Konstantin Boudnik <[email protected]>: > Indeed. > > The one hurdle I am facing though is that with BIGTOP-1833 getting pushed > to > the master (which I normally would appreciate ;) I have to fiddle with my > local branches as they already had a commit for this fix. Now, rebasing it > locally presents an issue where I need to fix some unpleasant conflicts > in... > > Oh well, it will be done in a bit. > Cos > > On Fri, May 29, 2015 at 09:37PM, Evans Ye wrote: > > I've committed the BIGTOP-1833 patch. > > It's so exciting that we're at the moment ready to release bigtop 1.0. > > Please ping me if any help needed for release. > > > > Evans > > > > > > 2015-05-29 17:52 GMT+08:00 Konstantin Boudnik <[email protected]>: > > > > > Guys, > > > > > > I have made all preparations for 1.0 RC and changed everything we need > to > > > move > > > to 1.1.0-SNAPSHOT in the master. > > > > > > However, because BIGTOP-1833 hasn't been reviewed yet, I evidently > haven't > > > pushed this change and other commits to the master nor branch-1.0. I > would > > > unblock me immediately if someone can review BIGTOP-1833 changes. Then > > > patch > > > is rather trivial and I have tested it to make sure that the packages > are > > > produced. > > > > > > I'd love to switch off to the vacation mode by the end of the day > today but > > > have to wrap up the RC process (at least the branch preparation part) > > > before > > > that. So if someone in Europe (during the day here) or later in NA can > do > > > this > > > at your early convenience - it'd be just great! > > > > > > Thanks in advance! > > > Cos > > > > > > On Tue, Apr 28, 2015 at 04:03PM, Konstantin Boudnik wrote: > > > > On Tue, Apr 28, 2015 at 03:11PM, Andrew Purtell wrote: > > > > > Also, working on BIGTOP-1851 right now. Please pardon the delay, I > was > > > sick > > > > > over the weekend. > > > > > > > > Thanks Andrew - hopefully are doing better now! > > > > > > > > > > > > > > On Tue, Apr 28, 2015 at 3:09 PM, Andrew Purtell < > [email protected]> > > > wrote: > > > > > > > > > > > Cool, I went over to BIGTOP-1615 and it's already resolved. > > > > > > > > > > > > As for BIGTOP-1827, if it's just a package naming problem we can > just > > > > > > rename it, right? See my comment on the issue. > > > > > > > > > > > > On Tue, Apr 28, 2015 at 2:40 PM, Konstantin Boudnik < > [email protected]> > > > > > > wrote: > > > > > > > > > > > >> Guys > > > > > >> > > > > > >> I think we are in the good shape to cut-off 1.0 branch tonight. > I > > > have ran > > > > > >> full stack build on Ubuntu and everything is building fine now. > Of > > > course > > > > > >> some > > > > > >> testing needs to be done ;) > > > > > >> > > > > > >> One last unresolved blocker is BIGTOP-1827. If I don't hear > from the > > > > > >> Tachyon component's maintainers I will have to remove this from > the > > > > > >> release > > > > > >> 1.0 because the packages are broken and we can release them like > > > this. > > > > > >> > > > > > >> BIGTOP-1615 (another blocker) is in PA state, so if anyone can > take > > > a > > > > > >> look - > > > > > >> it'd be great! > > > > > >> > > > > > >> Thanks! > > > > > >> Cos > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Best regards, > > > > > > > > > > > > - Andy > > > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - > Piet > > > Hein > > > > > > (via Tom White) > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Best regards, > > > > > > > > > > - Andy > > > > > > > > > > Problems worthy of attack prove their worth by hitting back. - Piet > > > Hein > > > > > (via Tom White) > > > > > > > >
