On Wed, Dec 2, 2015 at 3:19 PM, Sean Busbey <bus...@cloudera.com> wrote:
> > > On Wed, Dec 2, 2015 at 3:06 PM, Michael Armbrust <mich...@databricks.com> > wrote: > >> >>> >> The release is theoretically several weeks behind plan on what's >>> intended to be a fixed release cycle too. This is why I'm not sure why >>> today it's suddenly potentially ready for release. >>> >> >> Up until today various committers have told me that there were known >> issues with branch-1.6 that would cause them to -1 the release. Whenever >> this happened, I asked them to ensure there was a properly targeted blocker >> JIRA open so people could publicly track the status of the release. As >> long as such issues were open, I only published a preview since making an >> RC is pretty high cost. >> >> I'm sorry that it felt sudden to you, but as of last night all such known >> issues were resolved and thus I cut a release as soon as this was the case. >> >> > > It would help me, and I'm sure other less-active folks, if this kind of > feedback cycle were visible on dev@spark. It would also have the benefit > of getting feedback from non-committers who might e.g. have some issue that > they see in their own production deployments. > > > Sorry for a second email so soon. I meant to also ask, what keeps the cost of making an RC high? Can we bring it down with better tooling? -- Sean
