I've been looking more into the current code base and I see that a number of components are using 3rd party repos, like repository.cloudera.com. Clearly, we shouldn't be pulling Apache projects dependencies from a 3rd party source that could be outdated, contain non-Apache bits or simply have malicious artifacts.
let's get this fixed in in the next release or better yet in the respin of this one before the issue comes to the attention of the incubator. Thanks, Cos On Sat, Nov 07, 2015 at 06:14PM, tog wrote: > That's strange. It is on .. dev@ <[email protected]> > zeppelin.incubator.apache.org <[email protected]> the same > you are posting on if I am not mistaken. > > Cheers > Guillaume > On Nov 7, 2015 6:10 PM, "Konstantin Boudnik" <[email protected]> wrote: > > > So, there's a chance that 0.5.5 would require a respin if some issues are > > found with it during the IPMC vote, but the version has been moved already. > > You see where I am going with it ;) > > > > Could you point me where the vote is happening? I am not getting any > > emails on > > this neither in the dev@ nor private@ list... > > > > Thanks, > > Cos > > > > On Sat, Nov 07, 2015 at 06:03PM, tog wrote: > > > Cos, > > > > > > Voting is ongoing and should finish soon. > > > > > > Cheers > > > Guillaume > > > On Nov 7, 2015 6:01 PM, "Konstantin Boudnik" <[email protected]> wrote: > > > > > > > On Sat, Nov 07, 2015 at 03:59PM, moon soo Lee wrote: > > > > > 0.5.5-incubating has significant improvements in terms of feature and > > > > > stability compare to last release 0.5.0-incubating. > > > > > And i believe Zeppelin community will continue to make subsequent > > release > > > > > 0.5.6, 0.5.7 ... with more improvements and fixes. > > > > > > > > I see that master is on 0.6.0 right now. So, you guys are planning to > > keep > > > > on > > > > doing 0.5.x line, where's master will go to 0.6.x? Just a thought: > > perhaps > > > > it > > > > just makes sense to keep on going with 0.6, 0.7, and so far, instead of > > > > diving > > > > into fractional versioning? After all, the integers are cheap and > > > > plentiful ;) > > > > > > > > > Let me know if there're anything i can help for BIGTOP-1769 > > > > > > > > Right now I am building of branch 0.5.5 as I haven't seen the official > > > > release > > > > bits around yet. I should have the packaging fixed in a day or so and > > if I > > > > step on something in the product I would need some help for sure. > > Thanks > > > > for > > > > the offer! > > > > > > > > > About version, what could be proper version name in branch-0.5.5? > > > > > I thought it's weird to be stay in '0.5.5-incubating' after > > > > > '0.5.5-incubating' is released. > > > > > > > > But 0.5.5 wasn't released yet, was it? May I got confused and/or > > missed the > > > > 0.5.5 voting and release, but if 0.5.5 hasn't been released yet the > > version > > > > should stay at 0.5.5-SNAPSHOT or something? At least this is my > > experience. > > > > > > > > Cheers, > > > > Cos > > > > > > > > > Best, > > > > > moon > > > > > > > > > > On Sat, Nov 7, 2015 at 5:40 AM Konstantin Boudnik <[email protected]> > > > > wrote: > > > > > > > > > > > I also noticed that branch-0.5.5 has version 0.5.6-SNAPSHOT, which > > > > looks a > > > > > > bit > > > > > > weird. > > > > > > > > > > > > Cos > > > > > > > > > > > > On Fri, Nov 06, 2015 at 12:30PM, Konstantin Boudnik wrote: > > > > > > > Guys, > > > > > > > > > > > > > > I am looking at next Zeppelin release from the perspective of > > > > > > BIGTOP-1769. > > > > > > > latest Bigtop stack is sitting on Spark 1.5.1 hence having > > Zeppelin > > > > > > working > > > > > > > with the same is critical for Bigtop 1.1 release we have in > > works. > > > > > > > > > > > > > > Is there any feeling in the community when 0.5.5 will be ready or > > > > stable > > > > > > > enough so we can start massaging it in? > > > > > > > > > > > > > > Thanks in advance for any feedback > > > > > > > Cos > > > > > > > > > > > > > > > > > > > > > > > >
signature.asc
Description: Digital signature
