+1. Are there any thoughts around test plan/test suite that will gate this and other future releases?
On Thu, Jul 6, 2017 at 11:28 AM Smith, Nathanael P < [email protected]> wrote: > +1 > > - nathanael > > > On Jul 6, 2017, at 9:06 AM, Barona, Ricardo <[email protected]> > wrote: > > > > +1 > > > > On 7/6/17, 10:49 AM, "Edwards, Brandon" <[email protected]> > wrote: > > > > +1 > > > > On 7/6/17, 5:23 AM, "Michael Ridley" <[email protected]> wrote: > > > > +0 (non-binding) > > > > Seems ok to me although I'm not sure that we need a branch for a > release we aren't planning to make. Not totally following the thought > process there, but not something I'm particularly concerned about. > > > > Michael Ridley > > Senior Solutions Architect > > Cloudera > > > > Sent from my mobile. > > Pardon any spelling errors. > > > >> On Jul 5, 2017, at 7:33 PM, Ever Sandoval Apache <[email protected]> > wrote: > >> > >> Hello, > >> > >> As you may already know we’re working on the upcoming release of Apache > >> Spot (Incubating) 1.0 aka SPOT-154. > >> > >> In preparation for the coming release (1.0) we would like to start a > voting > >> process to create a branch Spot 0.9. Since entering the Apache > Incubator we > >> have not officially labeled Spot with a version, In order to make things > >> clear and understandable, we would like to propose the following: > >> > >> - Prior to start the release process we would like to create a branch > >> called Spot-0.9 that will capture the code as it is today. > >> - After the creation of Spot-0.9 we will start the release process in > >> order to merge SPOT-154 to the master branch. > >> > >> > >> > >> This voting process will be open for the next 3 days. Please feel free > to > >> bring up any concerns and let me know your feedback, > >> Regards > > > > > > > > >
