Right now, 603 issues have been resolved for 1.5.0. 424 are still
targeted for 1.5.0, of which 33 are marked Blocker and 60 Critical.
This count is not supposed to be 0 at this point, but must
conceptually get to 0 at the time of 1.5.0's release. Most will simply
be un-targeted or pushed down the road.
If the plan is to begin meaningful testing on Aug 1 (great) and
release by Aug 15, this seems to be far too large. Yes, it just means
some prioritization has to happen. Target Version and Priority still
seem like the right tools to communicate this.
Let me put up a straw-man: untarget any JIRA targeted to 1.5.0 that
isn't Blocker or Critical on Aug 1. (JIRAs can be explicitly
retargeted in the following week.) This still leaves 93 issues, which
seems unrealistic to address in 2 weeks.
What are additional or alternative steps to handle this?
- Untarget a lot of the remaining 93?
- Push out 1.5 by X weeks to address more items?
- Argue there's another way to manage this?
On Wed, Jul 29, 2015 at 6:46 AM, Reynold Xin r...@databricks.com wrote:
Hey All,
Just a friendly reminder that Aug 1st is the feature freeze for Spark
1.5, meaning major outstanding changes will need to land in the this
week.
After May 1st we'll package a release for testing and then go into the
normal triage process where bugs are prioritized and some smaller
features are allowed on a case by case basis (if they are very low risk/
additive/feature flagged/etc).
As always, I'll invite the community to help participate in code
review of patches in the this week, since review bandwidth is the
single biggest determinant of how many features will get in. Please
also keep in mind that most active committers are working overtime
(nights/weekends) during this period and will try their best to help
usher in as many patches as possible, along with their own code.
As a reminder, release window dates are always maintained on the wiki
and are updated after each release according to our 3 month release
cadence:
https://cwiki.apache.org/confluence/display/SPARK/Wiki+Homepage
Thanks - and happy coding!
- Reynold
-
To unsubscribe, e-mail: dev-unsubscr...@spark.apache.org
For additional commands, e-mail: dev-h...@spark.apache.org
