+1 I will fix Ignite - I know about this problem since 1.2.0 and was meant to work on, but other things took a priority.
In general I completely agree that we don't have to keep struggling with components without active maintenance. We've been through this conversation before, which resulted in the introduction of MAINTAINERS file. However, it hasn't fully fixed the issue. Thanks, Cos -- Take care, Konstantin (Cos) Boudnik 2CAC 8312 4870 D885 8616 6115 220F 6980 1F27 E622 Disclaimer: Opinions expressed in this email are those of the author, and do not necessarily represent the views of any company the author might be affiliated with at the moment of writing. On Sun, Jun 4, 2017 at 9:32 PM, Evans Ye <[email protected]> wrote: > Hi Bigtopers, > > I've shared this on my Apache Big Data talk, but haven't got a chance to > share with you yet. > This is a Jenkins matrix job to show the healthy status of our component > deployment code. > Each run deploys hdfs + Y on X, where X is the OS and Y is the component > shown on the matrix: > > https://ci.bigtop.apache.org/view/Provisioner/job/Bigtop-trunk-deployments/45/ > > Generally speaking, the status of our deployment code needs a lot of effort > to polish. > So, for 1.2.1 release, I think we should make some changes: > > 1). Remove unmaintained failing components > 2). Get maintained components fixed > > 1) might be easier to achieve, while 2) takes time. > In order to maintain a good code quality, I suggest proceed with 1). > > Any different thoughts?
