+1 On Fri, Aug 9, 2019 at 9:38 AM Jason Huynh <jhu...@pivotal.io> wrote:
> +1 > > On Thu, Aug 8, 2019 at 7:12 PM Owen Nichols <onich...@pivotal.io> wrote: > > > Hi Juan and Sai, thank you for bringing your concern. > > > > Geode's release process dictates a time-based schedule < > > https://cwiki.apache.org/confluence/display/GEODE/Release+Schedule> to > > cut release branches. The release/1.10.0 < > > https://github.com/apache/geode/tree/release/1.10.0> branch was already > > cut 1 week ago, but the “critical fixes” rule does allow critical fixes > to > > be brought to the release branch by proposal on the dev list, as you have > > done here. > > > > If there is consensus from the Geode community that your proposed change > > satisfies the “critical fixes” rule, I will be happy to bring it to the > > 1.10.0 release branch. > > > > Regards > > - Owen > > > > > On Aug 8, 2019, at 6:53 PM, Sai Boorlagadda <sai.boorlaga...@gmail.com > > > > wrote: > > > > > > +1 for getting this into 1.10 > > > > > > On Thu, Aug 8, 2019 at 11:29 AM Juan José Ramos <jra...@pivotal.io> > > wrote: > > > > > >> I'd like to propose including the fix for *GEODE-7022 [1]* in release > > >> 1.10.0. > > >> The fix basically improves our own implementation of the > > >> *RMIClientSocketFactory* to fully support the GEODE SSL settings, > > allowing > > >> our users to specify a default alias when opening an RMI connection. > > >> Best regards. > > >> > > >> [1]: https://issues.apache.org/jira/browse/GEODE-7022 > > >> > > >> -- > > >> Juan José Ramos Cassella > > >> Senior Software Engineer > > >> Email: jra...@pivotal.io > > >> > > > > >
