Hi Jun, We should do a release in order to push out changes which accumulate over the time. So I you have my +1
But bigtop needs some cleanup: 1) How do we handle failing packages? My vote is to simply remove them: Candidates are crunch, oozie, pig I only looked at oozie right now: oozie seems to be broken by conflicting requirements by log4j and shared libraries between hive and oozie see BIGTOP-2986 IMHO hive2 is way more important than having oozie, so I would say either oozie is fixed or out. There is another issue related to oozie packaging, though easy fixable: BIGTOP-3051. Looking at that I have to conclude that oozie never worked correctly in 1.2.x Putting all that together I would recommend to remove oozie from Bigtop for now. 2) I have a bad feeling for staying at hadoop-2.8.1. But since I do not have any productive environment any more I cannot judge why we should not upgrade to 2.8.4 thanks, olaf > Am 07.08.2018 um 18:11 schrieb Jun HE <[email protected]>: > > Hi, folks, > > As you may read from previous thread, I'm proposing to do a new release, > 1.3.0, before ApacheCon in Sept. > I'm a +1 for this because: > * quite a few fixes/improvements for building and deployment > * important components upgrade > * x86 and non-x86 platforms are aligned in master > > If there are enough votes for a release I'd like to volunteer to be the RM > for 1.3.0. > > Evans has initiated a well-defined release BOM ( > https://issues.apache.org/jira/browse/BIGTOP-2945), and I did some minor > modifications mainly about components versions in 1.3.0. > And issues might need fix: https://s.apache.org/Ja7e > > Your comments/thoughts are mostly welcomed! > > Regards, > > Jun
signature.asc
Description: Message signed with OpenPGP
