Hi cos I'd like to propose my BIGTOP-1771 moving into 1.0 so that we can have CI testing feature ready to run smoke-tests. The JIRA is also needed by setting BigTop CI infra "IF" we'd like to setup a real-cluster deployment test and smoke-tests.
2015-03-27 9:08 GMT+08:00 Konstantin Boudnik <[email protected]>: > I have reduced the number of the open tickets for the release down to 44. > I think it might go down a little more, but what's left seems to be doable. > Thoughts? Anything we need to move into 1.0 scope? > > Here's the filter https://issues.apache.org/jira/issues/?filter=12331028 > > Cos > > On Sat, Feb 28, 2015 at 06:56PM, Konstantin Boudnik wrote: > > Guys, > > > > It'd be great if we can have the next release ready by ApacheCon in > April. > > Think about all the PR and publicity we can get without any effort on > our own. > > And perhaps from the tactical standpoint we shall call this release 1.0? > > > > I believe the only major hurdle between us and the release is CI. Roman, > I > > understand you're busy elsewhere, but could you please let us know what > else > > needs to be done before we can start doing the regular builds and how the > > community can help. That's the highest priority, IMO. > > > > There a couple of the tickets left unfixed/unassigned on BIGTOP-1480, > and if > > they aren't resolved on time we can move them farther. There's lesser > than a > > half-dozen blockers and none of them look too big, honestly. And we have > a > > whole lot of active committers and contributors to wrap-up the release > in a > > couple of weeks. > > > > Do we want to try upgrade to HBase 1.x for this release or it might be > too big > > of a distortion? Andrew, what do you think and do you have cycles to do > that? > > > > What else we need to get done for this release? Suggestions? > > > > Is there anyone who wants to step up as the RM this time around? RM > doesn't > > mean that you have to do all the job, but rather be an efficient with a > stick ;) > > > > Thoughts? > > Cos >
