inline...
On Thu, Oct 24, 2013 at 12:28 PM, Kevin Minder <[email protected] > wrote: > My preference is to create a 0.3.1 branch from 0.3.0 for this fix as well > as anything discovered over the next week or so. I agree with your > concerns that graduation processes could slow this down so it would be best > to target this before graduation. > This feels right to me. Let's target all patches of 0.3.0 found over the next week or so for 0.3.1 and get that out. We should try and address all the HA related bugs that we find here. > > For 0.4.0 my preference would be to cut this based on feature advancement > and not necessarily doing something artificial based on graduation. > > Can we figure out a set of features for an early release then? A set of HA specific features may be a good theme for that release. > > On 10/24/13 12:16 PM, larry mccay wrote: > >> All - >> >> In light of the one line change required for KNOX-188 >> {TOPOLOGY_NAME}-credentials.**jceks is recreated when topology is >> changed - I >> propose that we create a branch 0.3.1 for patches. >> >> This issue will negatively affect HA deployment scenarios. Even though we >> aren't calling this out as a specifically supported scenario in 0.3.0, we >> are actively working on those usecases and they shouldn't have to wait for >> an 0.4.0 release. >> >> Another interesting consideration is the timing with regard to graduation. >> A release that patches HA and other issues with 0.3.0 may be able to be >> cut >> before graduation process begins and the transfer of the resources and >> infra setup may slow things down. >> >> So, I think that we have two questions to weigh in on: >> >> 1. does it make sense to make the 0.3.1 branch now? >> 2. should we assume a patch release before graduation efforts and target >> an >> 0.4.0 release post graduation? >> >> What are your thoughts? >> >> thanks, >> >> --larry >> >> > > -- > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity > to which it is addressed and may contain information that is confidential, > privileged and exempt from disclosure under applicable law. If the reader > of this message is not the intended recipient, you are hereby notified that > any printing, copying, dissemination, distribution, disclosure or > forwarding of this communication is strictly prohibited. If you have > received this communication in error, please contact the sender immediately > and delete it from your system. Thank You. >
