For the recently-added CM-based service discovery, the service coverage isn't as broad as is it for Ambari. I can prioritize fleshing that coverage out more completely if we think that's important for 1.3.0.
Do you have a timeframe in mind for the release? - Phil On Sat, Jun 22, 2019 at 6:35 PM larry mccay <lmc...@apache.org> wrote: > I've trimmed the outstanding issues for 1.3.0 down to 9. > One or two of these may already be done too. > We should be able to close down on this and get an RC over the next week > and would like to push to do so. > > Here is the current list: > > [image: image.png] > > On Sat, Jun 22, 2019 at 5:58 PM larry mccay <larry.mc...@gmail.com> wrote: > >> All - >> >> I am going to start aggressively moving issues from fixVersion 1.3.0 to >> 1.4.0 in order to close down on a 1.3.0 release. We have a number of >> performance and other bugs fixes that need to find their way into an actual >> release. >> >> Anything that I move out that you feel needs to land in the 1.3.0 release >> and you have cycles and intent to provide a patch - please feel free to >> move it back into 1.3.0 with a comment to that effect. >> >> thanks, >> >> --larry >> >
