Are these about the right rules of engagement for now until the
release candidate?
- Don't merge new features or improvements into 1.5 unless they're
Important and Have Been Discussed
- Docs and tests are OK to merge into 1.5
- Bug fixes can be merged into 1.5, with increasing conservativeness
as
I agree that it's high time to start changing/removing target versions,
especially if component maintainers have a good idea of what is not needed
for 1.5. I'll start doing that on ML.
On Mon, Aug 3, 2015 at 12:05 PM, Sean Owen so...@cloudera.com wrote:
Are these about the right rules of
Hi Devs,
Just an announcement that I've cut Spark's branch-1.5 to form the basis of
the 1.5 release. Other than a few stragglers, this represents the end of
active feature development for Spark 1.5. *If committers are merging any
features (outside of alpha modules), please shoot me an email so I
Would it be reasonable to start un-targeting non-bug non-blocker
issues? like, would anyone yell if I started doing that? that would
leave ~100 JIRAs, which still seems like more than can actually go
into the release. And anyone can re-target as desired.
I think the maintainers of the
