Release engineering work on projects in the IDE WG that are at the root of the dependency charts
Description Release engineering work on projects in the IDE WG that are at the root of the dependency charts
There are various projects which need release engineering work that are at the root of the dependency charts of the SimRel that require additional investment. For this funded dev effort the focus is on these projects, but similar dev efforts in the future may be created for additional projects:
-
Tycho
-
Eclipse Platform
-
EMF
-
Perform release engineering and general project support -
Follow the release engineering steps of the project -
Improve the documentation/checklists for release engineering to reduce the "Bus Factor" of the project to ensure that any committer can perform a release -
Ensure project's conformance to SimRel's participation requirements -
Monitor communications channels to identify users of the project having integration and related issues, and solve those issues. -
Update libraries and other dependencies of projects, to address CVEs or to address goals of the participation requirements, such as removing duplicate third-party libraries
-
-
Depending on the release cycle of the project, the timescale expects 1 day per release cycle of work, plus additional time allocated to the project (e.g. 1 day per week or 1 day per month) -
Expected deliverables/outcomes: -
Perform release of the project on the project's timetables -
Follow along with the standard Eclipse Development Process -
Guided by the project's contribution guidelines.
-
-
The Eclipse Foundation IT Infrastructure does not have any expected impacts for this development effort -
The means of verification of completion will require that the project delivers a release on schedule.
An SoW for this dev effort may cover one or multiple projects, and as such this issue can be duplicated to cover the individual projects as needed.
This dev effort requires the person to be a committer on the project that the release engineering is being performed on. This is because many of the tasks of any project's release engineering requires committer level access to various resources such as projects.eclipse, download.eclipse.org, ci.eclipse.org, bug/issue trackers, etc. as well as proper knowledge and understanding of the Eclipse Development Process such as the IP Policies and review requirements.