Reviews run for a minimum of one week. The outcome of the review is decided on this date. This is the last day to make comments or ask questions about this review.
The Eclipse Simultaneous Release, i.e., SimRel, has been operating effectively as an Eclipse Project for many years. With the recent migration of SimRel's Git repositories to a top-level GitHub organization, it's time to formally create it as the project associated with the eclipse-simrel GitHub organization:
SimRel provides infrastructure for coordinating the release of projects used to build Eclipse IDE and RCP applications. It produces one of the primary inputs for building the Eclipse IDEs:
The Eclipse SimRel (Simultaneous Release) provides a formal description for aggregating multiple p2 repositories, i.e., project contributions, into a single, cohesive, self-contained p2 repository. It provides infrastructure for validating project contributions and for producing and managing the aggregated p2 update sites.
The Eclipse Simultaneous Release process works as follows:
- The simrel.aggr model specifies precisely what is to be aggregated.
- The simrel.build change-requests jobs validate each pull request to the simrel.aggr model before the change is committed to the main branch.
- The simrel.build main job promotes each succesfull aggregation build of the current simrel.aggr model on the main branch to the appropriate current subdirectory of staging to produce the SimRel p2 Staging Repository.
- The Eclipse Packaging Product's CI jobs produce an EPP p2 Repository and corresponding EPP Products using the SimRel p2 Repository as input.
- Various Releng jobs periodically promote staging repositories to more permanent locations.
SimRel has been operating effectively as an Eclipse Project for many years.
SimRel will continue to operate as it has for many years, producing the Eclipse IDE quarterly releases.
We plan to provide improved documentation and to migration away from deprecated infrastructure such as wiki.eclipse.org.