Phase 1

- SDK
  - Platform
    - Equinox
      - Native launchers
      - SSO/Keystore/Security integration
    - Workbench
  - SWT
    - We don't know where the builds are for this
  - p2
  - CVS
  - JDT
  - PDE
  - Help
  - there is a zip and p2 repository as output

Phase 2

- API Tooling
- Skip republishing of unchanged bundles
- Building the SDK with itself

Phase 3 (optional)

- Conversion of all project that are part of Juno
  - this is not our problem

Phase 4

- Complete aggregration of Juno
  - Currently this is done by the b3 aggregator
  - Not sure anything needs to change here

---

LTS Usecase
- SAP wants to patch JDT in Indigo SR2
- we official development setup
- we need a version from which to start
- SAP needs to materialize a setup whereby they can make their patch
- SAP needs to build this new distribution
Problems
- how to block version mixture when specific components change
  - do we just stipulate the separation of build repositories