Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Orbit/Transition to Git Plan
Draft / Proposal
This is a draft plan being proposed. Please submit comments/feedback to orbit-dev@eclipse.org.
This is a draft plan being proposed. Please submit comments/feedback to orbit-dev@eclipse.org.
Contents
Goals
- Replace usage of CVS with Git
Plan
- Migrate from hand crafted bundles in CVS to templated approach implemented by EBR
- Publish bundles built from recipes as new (additional) p2 repository
- Leaving all existing Orbit "R" builds in place
- Possibly offer a composite repository (if desired) of old CVS based and new Git based bundles
Proposed Timeline
- (July) Document plan and timeline
- (July) Start publishing p2 repository with recipes on downloads.eclipse.org in addition to existing Orbit repositories
- (August) Maven repository of IP approved libraries hosted at Eclipse.org (instead of consuming libraries from Maven Central)
- (End of August) Announce availability of new "stream" and migration plan via cross-project
- (September) Mars SR1
- (October, after Mars SR1) Freeze CVS, stop building bundles out of CVS
- (October, after Mars SR1) Every change must be done in Git now, i.e. missing recipes must be created first
- (December) archive Orbit CVS
TODOs
- setup Gerrit for recipes repo (bug 472244)
- publish p2 repo from recipe HIPP build on download.eclipse.org
- generate nice HTML download page for download.eclipse.org based of p2 metadata
- consume IP approved libraries from Eclipse.org hosted Maven repository instead of Maven Central
- create and document process for adding IP approved libraries to such an Eclipse.org hosted Maven repositories