|
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
On 7/22/19 11:15 AM, Scott Stark wrote:
Right, this sheet is about when projects need to be staged and
shows the worst case timeline for that.
I regard the "release review
problem" as being similar to the Eclipse IDE's annual
simultaneous release. By way of (limited) background,
there are at least four levels of dependencies in the ~80
projects that participate in the simultaneous release.
In the the case of the Eclipse IDE Simultaneous Release,
the dependencies are a build problem, not a review
problem. I believe that the same is true here. That is,
I do not believe that there is any requirement to
release upstream specifications before we engage on
downstream specifications. Put another way, a
specification project can engage in a release review and
then release at the same time as all of its prerequisite
specifications.
Based on the JESP revision 1.2, we need to
start the release review on August 14/2019.
This chart of dependencies will be helpful
in in assembling the technical artifacts leading up to
that date.
Wayne
I took the spec
release dependencies that I had sent out to the spec
leads list and put them in a Gantt chart that ran the
project serially through their releases with the current
two week voting period. This has the plane landing Oct
25. Clearly projects will need to release with overlaps
and/or shorter review periods. I have also attached a
version where every spec project is released in 7 days.
This results in the final spec being released on Sep 6.
_______________________________________________
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
--
Wayne Beaton
Director of Open Source Projects | Eclipse Foundation, Inc.
_______________________________________________
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
_______________________________________________
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
|
