Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Virgo/Future"
(→Release Branding) |
(→Release Branding: Updated future versions of embedded Spring Framework) |
||
Line 44: | Line 44: | ||
| Sky || Virgo 3.6.x || Gemini Web 2.2.x <br> (Embedded Apache Tomcat 7.0.x) || Gemini Blueprint 1.0.2 || 3.1.0.RELEASE || Gemini Management 1.0.x || Virgo IDE 1.0.1 | | Sky || Virgo 3.6.x || Gemini Web 2.2.x <br> (Embedded Apache Tomcat 7.0.x) || Gemini Blueprint 1.0.2 || 3.1.0.RELEASE || Gemini Management 1.0.x || Virgo IDE 1.0.1 | ||
|- | |- | ||
− | | Steel || Virgo 3.7 || Gemini Web 2.2.x <br> (Embedded Apache Tomcat 7.0.x) || Gemini Blueprint 2.0 || | + | | Steel || Virgo 3.7 || Gemini Web 2.2.x <br> (Embedded Apache Tomcat 7.0.x) || Gemini Blueprint 2.0 || 4.1.x.RELEASE || Gemini Management 1.0.5 || Virgo IDE 1.0.1 |
|- | |- | ||
− | | Cobalt || Virgo 4.0 || Gemini Web 3.0.x <br> (Embedded Apache Tomcat 8.0.x) || Gemini Blueprint 2.0 || | + | | Cobalt || Virgo 4.0 || Gemini Web 3.0.x <br> (Embedded Apache Tomcat 8.0.x) || Gemini Blueprint 2.0 || 4.1.x.RELEASE || Gemini Management 2.0 || Virgo IDE 1.0.1 |
|} | |} | ||
Revision as of 04:32, 1 May 2015
This page summarises the Virgo plan and notes design ideas for future Virgo features.
Contents
Virgo Plan
The following plan is subject to change and depends on how much resource is available as the project evolves.
3.7.0 (Steel) Release
- Upgrade to Gemini Blueprint 2.0
- TBD, but see the Steel bugtrain bug 396813.
4.0.0 (Cobalt) Release
- Upgrade to Gemini Management 2.0
- Support Equinox unity (my suggestion, it may now be called something different) - see bug 404390
- Upgrade to Gemini Web 3.0 (Embedded Apache Tomcat 8.0.x) - this is a plan and it still is not finalized
Release Branding
To accommodate simultaneous releases of Virgo runtime, OSGi Web Container runtime, and Virgo tooling, we are branding each release with the name of a colour, including old releases.
Brand | Runtime | Web Container | Blueprint | Spring Framework | Management | Eclipse IDE Tooling |
---|---|---|---|---|---|---|
Fern | SpringSource dm Server 1.0.x | Embedded Apache Tomcat 6.0.x | Spring DM 1.1.x | 2.5.6.A | - | - |
Emerald | SpringSource dm Server 2.0.x | OSGi Web Container 1.0.x (Embedded Apache Tomcat 6.0.x) |
Spring DM 1.2.1 | 3.0.0.RELEASE | - | - |
Cornflower | Virgo 2.1.x | Gemini Web 1.1.x (Embedded Apache Tomcat 6.0.x) |
Spring DM 1.2.1 | 3.0.0.RELEASE | - | - |
Maya | Virgo 3.0.x | Gemini Web 2.0.x (Embedded Apache Tomcat 7.0.x) |
Spring DM 1.2.1 | 3.0.5.RELEASE | - | - |
Bondi | Virgo 3.5 | Gemini Web 2.1 (Embedded Apache Tomcat 7.0.x) |
Gemini Blueprint 1.0 | 3.0.5.RELEASE | Gemini Management 1.0.2 | Virgo IDE 1.0 |
Sky | Virgo 3.6.x | Gemini Web 2.2.x (Embedded Apache Tomcat 7.0.x) |
Gemini Blueprint 1.0.2 | 3.1.0.RELEASE | Gemini Management 1.0.x | Virgo IDE 1.0.1 |
Steel | Virgo 3.7 | Gemini Web 2.2.x (Embedded Apache Tomcat 7.0.x) |
Gemini Blueprint 2.0 | 4.1.x.RELEASE | Gemini Management 1.0.5 | Virgo IDE 1.0.1 |
Cobalt | Virgo 4.0 | Gemini Web 3.0.x (Embedded Apache Tomcat 8.0.x) |
Gemini Blueprint 2.0 | 4.1.x.RELEASE | Gemini Management 2.0 | Virgo IDE 1.0.1 |
Note 1: we are steering clear of the following "wimp list" of colours: Azure, Indigo.
Note 2: the SpringSource dm Server releases are shades of green because of the SpringSource branding. Virgo has cornflower blue in its logo and admin console styling, so we chose shades of blue for Virgo releases.
Future Directions
Support for the OSGi Subsystems specification is deferred indefinitely (rationale), except for generalising the InstallArtifact tree to a DAG which was implemented in Virgo 3.5.0 (see the Kernel Enhancements section of the Virgo 3.5.0 release notes).