Thanks for starting this conversation, guys! I want to ask this: is revamped CI is the mast to have for this release?
Cause, I honestly think that gating the release on the CI cleanup will put the release even farther down the road. Right now we have the old CI in somewhat bearable state where we can produce a set of testable bits. I'd rather get 0.8.0 out of the doors, then start working on the CI and prep for 0.9.0 with Hadoop 2.5 within a few weeks from now. My 2 cents. Cos On Mon, Aug 11, 2014 at 11:45AM, jay vyas wrote: > Hi roman and others: > > how do you feel about this: > > i think it might be ** better for the bigtop community** if we **gated > release** on **fully cleaned up CI**.... even if that means delaying things > a few weeks. > > do you folks think this might be a good idea? > > after all, maybe the best way to force ourselves to clean it up is to get > 0.8.0 release on functioning CI ! > and then , with a functioning CI, the time saved will allow to release > 0.9.0 way faster, so the time will be > made up shortly/// > > opinions on this +1/-1/0 ? if others think maybe its a good idea , maybe we > can schedule a g+ hangout for wednesday, after work, to carve a path > forward. > > > > On Mon, Aug 11, 2014 at 2:25 AM, Roman Shaposhnik <[email protected]> wrote: > > > With the latest changes that went in over the weekend > > I'm happy to report that at least on the minimum set of > > package tests we're down to one issue only: > > > > http://bigtop01.cloudera.org:8080/view/Bigtop-trunk/job/Bigtop-trunk-packagetest/label=lucid-slave/lastCompletedBuild/testReport/ > > > > Various hive-* packages seem to fail on install > > on Ubuntu 10.04. > > > > If anybody can take a look -- it'll be greatly appreciated. > > > > Also, the Jenkins EC2 issues still remains and it > > seems to consistently affect only 2 of our dynamic > > slaves: fedora18 and opensuse12. The rest are fine. > > > > Thanks, > > Roman. > > > > > > -- > jay vyas
