Hi, I personally would like the release to go ahead and an issue for this to be opened in Jira as its verified to work on your side and has issues in my instance ( which involves docker, arm architecture and other such factors)
I'm going to test this further during this weekend and get back with more information. Regards Kaushik Srinivasan On 22 Jul 2017 2:02 p.m., "Mike Jumper" <[email protected]> wrote: > Hi all, > > As it's now been ~2 weeks since this vote started, with no solid > progress one way or the other in verifying the existence/severity of > the issue with the new CAS auth. Regardless of whether that issue > should be release-blocking, that's effectively what it's become. > > Does anyone feel strongly that the release should not proceed without > further verification of CAS? If so, let's get an actual -1, I'll > cancel the vote, and we'll refocus on identifying and resolving that > issue. If not, let's open an issue in JIRA to track this and not let > it block the release itself, which is greater in scope than simply CAS > auth. > > Thanks, > > - Mike > > On Fri, Jul 14, 2017 at 9:12 AM, Kaushik Srinivasan > <[email protected]> wrote: > > Hi Mike, > > > > I haven't had the time yet to test it. I'll be working on it this weekend > > and will be able to confirm it by Monday. > > > > (Sorry abt the delay) > > > > Regards > > Kaushik Srinivasan > > > > On 14 Jul 2017 11:53 a.m., "Mike Jumper" <[email protected]> > wrote: > > > > On Thu, Jul 13, 2017 at 7:59 AM, Kaushik Srinivasan > > <[email protected]> wrote: > >> That clearly explains the problem. > >> > >> Thanks Mike. > >> > > > > If you switch to a build of RC1 of 0.9.13-incubating, does CAS work as > > expected? > > > > Thanks, > > > > - Mike >
