I plan to branch for the 1.3.0 release while we close down the last few issues. We will just need to double commit to master and v1.3.0 branches until the release ships.
On Sat, Jun 22, 2019 at 10:59 PM larry mccay <lmc...@apache.org> wrote: > I would say the release is over due. > If the service discovery isn't quite ready, we can add to known issues or > just not document it as ready for prime time. > It can be a preview feature of sorts. > > I am thinking about turning this release around in a week or so and then > we can get started on 1.4.0. > > I could certainly be convinced to put it off for another week or so though. > What are you thinking? > > On Sat, Jun 22, 2019 at 9:31 PM Phil Zampino <pzamp...@apache.org> wrote: > >> 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 >> >> >> > >> >
