Could be from the original statement that I looked at a simple serial version of the plan that did use a 14 day ballot related plan, but that cannot work so now staging vs balloting is decoupled. We can discuss how we want to run ballots around staging tomorrow.
I think some of us were confused and thought the bars on the chart
represented the start and end of the ballot for a spec.
Scott Stark wrote on 7/22/19 5:00 PM:
I was asked to create a worst case scenario plan based on the
maven dependencies that were identified. That is what the 7 day
staging plan represents. It really is independent from any ballot
schedule other than the earliest a ballot could start is when a
spec release is staged and PR submitted. There are a number of PRs
for specs, so we’ll have to see how status progresses as reviews
are started.
I agree we should not hold up spec reviews for
approvals of prerequisite specifications.
Last week at Steering Committee we agreed that
our goals should be:
- We submit for ballot as many specs as
possible, as soon as possible, beginning with specs
that are ready for PMC/Steering Committee review this
week. In other words we should not wait, in general,
until August 5 before submitting specs for ballot.
- We should formally shorten the review
period for specs in the schedule by two weeks,
effectively making July 29 the new “drop dead” date
for specs to be prepared for review by PMC/Steering
Committee prior to the new “drop dead” date of August
5 for specs to be submitted for ballot.
I will not be at the meeting tomorrow, but if
we want to make the Sept 10 target, I think we should be
communicating and working towards the above, vs.
communicating and setting an expectation for an August
14 release review start date.
Will
_______________________________________________
jakarta.ee-spec.committee mailing list
jakarta.ee-spec.committee@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/jakarta.ee-spec.committee
|
