These are great points Jay. And we sure should reach out! And we do times and again!
What I can't help but wonder about is if Bigtop discovers a stopper bug in a component build system then how said component could possible can have an official release with such a bug? I am not even talking about the integration issues - this is something we designed to discover. But about the _official release_'s bugs, where the build is outright broken???? In other words, does Bigtop has enough people-power to QA everything in the Hadoop ecosystem? Cos On Sat, Oct 11, 2014 at 11:22PM, Jay Vyas wrote: > the sentiment is probably along these lines: > > pig and mahout would be great to have, ** but ** not sure if either community > is still interested in packaging their bits in bigtop, and indeed both are > broken at the moment. maybe we should reach out on the mailing list to see > how they feel? > i for one would definetly be willing to work with those folks if they want to > help us to > > On Oct 11, 2014, at 11:16 PM, Artem Ervits <[email protected]> wrote: > > > Pig project is thriving, there╧s work on Pig on Tez, Spark and Storm. I am > > curious what would contribute to this sentiment? > > > > On 10/11/14, 9:58 PM, "Konstantin Boudnik" <[email protected]> wrote: > > > >> Looks like it is going slow. so I will continue. To start with... > >> > >> I am proposing the following set of supported platforms (similar to last > >> time) > >> > >> OS: > >> CentOS6, CentOS7, Fedora 20 > >> SLES12, OpenSUSE 13.1 > >> Ubuntu 14.04 LTS > >> > >> Java: > >> OpenJDK 7 > >> > >> Components: > >> > >> Zookeeper 3.4.6 (or later?) > >> Hadoop 2.6.x > >> HBase 0.98.x (latest; I am not sure if 1.0 will be ready in the 2 > >> months?) > >> Hive 0.14 > >> Sqoop 1.99.4 > >> Oozie 4.0.1 > >> Giraph 1.1.0 > >> Groovy 2.3 > >> Hue 3.6.0 > >> DataFU 1.0.0 > >> Solr 4.6.0 > >> Crunch 0.10.0 > >> Spark 1.1.0 > >> Phoenix 4.1.0 > >> Tomcat 6.0.36 > >> jsvc 1.0.15 > >> What other new stuff do we feel like adding? > >> > >> To retire: > >> Pig (is there enough interest in the community to keep it on?) > >> Whirr 0.8.2 (seems to be headed to the Attic) > >> Mahout 0.9 (unless we have a version working w/ Hadoop 2) > >> Flume 1.5.0.1 (the project seems to be winding down?) > >> > >> Thoughts? > >> Cos > >> > >> On Sat, Oct 04, 2014 at 04:10PM, Konstantin Boudnik wrote: > >>> > >>> Now as 0.8.0 is practically done I want to kick of the discussion about > >>> next > >>> release's scope and aim. We already have discussed a number of things > >>> that we > >>> want to address in this round, including > >>> - CI improvements > >>> - build system enhancements > >>> - overhaul of the testing experience > >>> - TBD > >>> > >>> A very important topic to cover here is, of course, the scope of the > >>> next > >>> release. Bigtop has a very powerful ability to help new technologies to > >>> thrive > >>> by wider promoting them across the Apache communities and beyond. > >>> However, > >>> without deliberate help from the perspective projects we can not keep on > >>> supporting them in the Apache Hadoop Stack: after all we are a bunch of > >>> volunteers spending our own time on things we like to do. Hence, we > >>> need to > >>> carefully prioritize what we realistically can or can not support. > >>> > >>> The other side of this coin is to make this project fun where people > >>> want to > >>> contribute something they feel passionate about. Let's say, I am the > >>> only one > >>> contributing fixes and supporting component X. However, for whatever > >>> reason I > >>> couldn't possibly care less about having component X on board. The > >>> question is > >>> - shall I use my limited time on the face of this planet for something > >>> that > >>> makes me tick, instead of wasting it on the dull chores around > >>> component X? > >>> Let's weigh carefully on what we want to carry on and what we'll be > >>> dropping > >>> this time. > >>> > >>> Supported OS spectrum: let's drop the dead weight and carefully > >>> consider what > >>> to add. > >>> > >>> Release cycle: with new docker based CI we should be better equipped for > >>> regular builds testing and build environment which will be _exactly_ > >>> the same > >>> for developers and official Jenkins. Hence, can we have next release in > >>> the > >>> by the end of 2014? We already know that 0.8.0 has a few issues that we > >>> want > >>> to improve upon quickly. > >>> > >>> User facing documentation, wiki, website: let's see where we can get > >>> some help > >>> with this. Shall we try recruiting fresh-grads and students who wants > >>> to start > >>> in on of the projects we support, but they don't know how? How we can > >>> increase > >>> the reach? > >>> > >>> I know this looks like an awful lot of questions and no answers, but > >>> that > >>> what a discussion should be about, right? ;) > >>> > >>> Here's JIRA for the BOM > >>> https://issues.apache.org/jira/browse/BIGTOP-1480 > >>> > >>> Please chime in! > >>> Cos > >>> > >>> -- > >>> Take care, > >>> Cos > >>> 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 > >>> Cos' pubkey: http://people.apache.org/~cos/cos.asc > >>> > >>> ---- Wisdom of the hour ---- > >>> > >>> In Marseilles they make half the toilet soap we consume in America, but > >>> the Marseillaise only have a vague theoretical idea of its use, which > >>> they > >>> have obtained from books of travel. > >>> Mark Twain > >> > >> > > > > This electronic message is intended to be for the use only of the named > > recipient, and may contain information that is confidential or privileged. > > If you are not the intended recipient, you are hereby notified that any > > disclosure, copying, distribution or use of the contents of this message is > > strictly prohibited. If you have received this message in error or are not > > the named recipient, please notify us immediately by contacting the sender > > at the electronic mail address noted above, and delete and destroy all > > copies of this message. Thank you. >
signature.asc
Description: Digital signature
