Moving this to dev -- That's good, that'll help. Technically there's still a Blocker bug: https://issues.apache.org/jira/browse/SPARK-12000
The 'race' doesn't matter that much, but release planning remains the real bug-bear here. There are still, for instance, 52 issues targeted at 1.6.0, 42 of which were raised and targeted by committers. For example, I count 6 'umbrella' JIRAs in ML alone that are still open. 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. I'm just curious, am I the only one that thinks this isn't roughly normal, or do other people manage releases this way? I know the real world is messy and this is better than in the past, but I still get surprised by how each 1.x release actually comes about. On Wed, Dec 2, 2015 at 8:12 PM, marmbrus <g...@git.apache.org> wrote: > Github user marmbrus commented on the pull request: > > https://github.com/apache/spark/pull/10108#issuecomment-161420041 > > Sorry if this seemed arbitrary, I cut the release as soon as all the > blocker issues were resolve. In the future I'll announce on the dev list > first. > > > --- > If your project is set up for it, you can reply to this email and have your > reply appear on GitHub as well. If your project does not have this feature > enabled and wishes so, or if the feature is enabled but not working, please > contact infrastructure at infrastruct...@apache.org or file a JIRA ticket > with INFRA. > --- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org > For additional commands, e-mail: reviews-h...@spark.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org For additional commands, e-mail: dev-h...@spark.apache.org
