On December 7/2018, the Eclipse Foundation’s Board of Directors approved a new edition of the Eclipse Development Process (EDP) which introduces one particularly significant change, along with a small number of other useful changes. We rolled this new edition out on December 14/2018.
Note that project teams who are familiar with the previous edition of the EDP can just keep doing what they’ve always done: all changes in this new edition are backwards compatible.
The big change is the introduction of Progress Reviews and the recast of Release Reviews as a type of Progress Review. Progress Reviews are basically the same as Release Reviews with the exception that they can occur at any point in the project lifecycle (while the EDP doesn’t explicitly make any specific requirements, Release Reviews are generally accepted to be timed near the end of a release cycle). The basic idea is that a project team can opt to time a Progress Review at their convenience.
Progress Reviews are not in and of themselves interesting. What is interesting is that a project team can declare as many official releases as they’d like for an entire year following a successful Progress Review or Release Review. This should be especially interesting and valuable to projects that need to make very frequent releases.
This change in the nature of how we do releases, required that the statement that “the IP Policy has been followed and all approvals have been received” be moved from being a requirement of a Release Review to being a requirement of a release. That is, the change in the nature of releases does not change the requirement the the Eclipse IP Policy be followed and that projects engage in the full Eclipse IP Due Diligence Process.
Intellectual property must be properly accounted for and tracked at all times. The project team must engage in the Eclipse IP Due Diligence Process on an ongoing basis. The IP Log review and approval that occurs at the time of either a Release Review or Progress Review should be regarded as a means of confirming that intellectual property is being properly managed and not as a trigger to engage in a last minute clean up.
Only intellectual property that has been been approved (or license certified) by the Eclipse IP Team may be included in a release.
In addition to the IP Policy, project teams are expected to continue to engage in the usual sorts of community building activities like open and transparent release planning.
The new edition also includes the following changes:
- A long-missing Terms and Definitions section has been added;
- The Releases section has been restructured and is (hopefully) more easily parsed;
- The content is captured in Asciidoc and rendered using Asciidoctor; and
- All anchors in the document are self-referential links (which make it easier to get links into the document).
A more comprehensive list of the changes is captured in the change log.
I’ll push out updates to the Eclipse Project Handbook that support these changes later this week.