On 11/22/2011 03:49 PM, Roman Shaposhnik wrote: > On Tue, Nov 22, 2011 at 3:37 PM, Bruno Mahé <[email protected]> wrote: >>>> 1/ Latest openSUSE and Fedora are respectively 12.1 and 16 >>> You're absolutely correct. I specifically didn't say "latest" versions, >>> but stuck with the current ones. Is there any reason you feel >>> so strongly about bumping the versions of these OSes? >> I do all my work on latest Fedora/Mageia. So I will not test Fedora 15 >> at all. So you get support for Fedora 16 for free. > Good point. As long as you're willing to support the neccessary > infrastructure on bigtop Jenkins -- I have no objections to bumping > Fedora version.
I can handle the Fedora side of things. >> Hence my suggestion to have a stable branch for releases based on the >> 0.20.20X generation and having trunk based on the next gen Hadoop. > We had this discussion a couple of month ago and you, yourself, made > a point that trunk should be reserved to changes which are stable. > E.g. putting versions of unreleased Apache projects in trunk is a no-no. > > Any reason you're reversing your position now? > How am I reversing my position? We are talking about released versions of Apache Hadoop 0.23.X which will get increasingly more stable by then. >> The stable branch being there for people wishing to use a stable >> distribution and the coming releases of Bigtop to be used as a solid >> base for helping projects improving their compatibility with Hadoop >> 0.23. > Sure and last time we discussed it, we had a consensus that it is called > trunk. 0.23 is one of its kind :) >> This will also have the added benefit on helping putting Hadoop >> 0.23 in more people's hands and improve Bigtop's Hadoop 23 support. > I don't follow. There's absolutely no difference checking out trunk > or checking out a branch and building the stack. And it is THE only > wait to get Bigtop built for .23. Or you can pull packages from our > Jenkins job -- either way, I don't see how you can make it *easier* > to get .23. Care to elaborate? We cannot call this a release. Whatever we put there, it can be as awesome as we wish, it is pointless if it is not released. >> I wouldn't mind at all having a release of Bigtop with just Hadoop 0.23 >> + HBase + other compatible projects, and reactivating these projects one >> by one as they get compatible with Hadoop 0.23. > I would strongly -1 that decision. And I'm most certainly would not my name > to be associated with such a release. Dropping components willy-nilly > is the biggest threat to Bigtop's credibility as an Apache Bigtdata > distribution. Hence the stable branch with all the components enabled. But you called a vote and we will see what the community wants. I am not the only member of this community :) >> So we don't have to wait mid 2012 to have a release of Bigtop based on >> Hadoop 0.23. > From my stand point -- we absolutely *have* to. Otherwise it will not be > Bigtop we're talking about. > >> I am rather in favour of "release early and often" and therefore the >> later option :) > Now I'm totally confused -- with that motto, why do you NOT want to > release 0.3.0? Who said I don't want to release 0.3.0? I just disagree with the conditions of the release, not releasing in itself :) > Thanks, > Roman.
