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) > > >
