Jump to: navigation, search

Difference between revisions of "Virgo/Future"

(Release Branding)
 
(36 intermediate revisions by 3 users not shown)
Line 6: Line 6:
 
The following plan is subject to change and depends on how much resource is available as the project evolves.  
 
The following plan is subject to change and depends on how much resource is available as the project evolves.  
  
== 3.6.0 (Sky) Release ==
+
== 3.7.0 (Steel) Release ==
  
* Java 7 support
+
* Upgrade to Gemini Blueprint 2.0
* Support Java enterprise APIs (EJB, CDI, JPA, JSF, Web)
+
* TBD, but see the [https://bugs.eclipse.org/bugs/show_bug.cgi?id=396813 Steel bugtrain bug 396813].
* New web admin console
+
 
 +
== 4.0.0 (Cobalt) Release ==
 +
 
 +
* Upgrade to Gemini Management 2.0
 +
* Support Equinox unity (my suggestion, it may now be called something different) - see [https://bugs.eclipse.org/bugs/show_bug.cgi?id=404390 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  ==
 
== Release Branding  ==
Line 17: Line 22:
  
 
{| class="wikitable" border="1" cellpadding="10" cellspacing="0"
 
{| class="wikitable" border="1" cellpadding="10" cellspacing="0"
|+ '''''Virgo Release Branding'''''
+
|+ '''''Virgo Release Branding and Component Versions'''''
 
|-
 
|-
 
! Brand  
 
! Brand  
 
! Runtime
 
! Runtime
! Web Container  
+
! Web Container
 +
! Blueprint
 +
! Spring Framework
 +
! Management
 
! Eclipse IDE Tooling  
 
! Eclipse IDE Tooling  
 
|-
 
|-
| Fern || SpringSource dm Server 1.0 || - || -
+
| 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 || OSGi Web Container 1.0 || -
+
| Emerald || SpringSource dm Server 2.0.x || OSGi Web Container 1.0.x <br> (Embedded Apache Tomcat 6.0.x) || Spring DM 1.2.1 || 3.0.0.RELEASE || - || -
 
|-
 
|-
| Cornflower || Virgo 2.1 || Gemini Web 1.1 || -
+
| Cornflower || Virgo 2.1.x || Gemini Web 1.1.x <br> (Embedded Apache Tomcat 6.0.x) || Spring DM 1.2.1 || 3.0.0.RELEASE || - || -
 
|-
 
|-
| Maya || Virgo 3.0 || Gemini Web 2.0 || -
+
| Maya || Virgo 3.0.x || Gemini Web 2.0.x <br> (Embedded Apache Tomcat 7.0.x) || Spring DM 1.2.1 || 3.0.5.RELEASE || - || -
 
|-
 
|-
| Bondi || Virgo 3.5 || Gemini Web 2.1 || Virgo IDE 3.5
+
| Bondi || Virgo 3.5 || Gemini Web 2.1 <br> (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 || Gemini Web 2.2 || -
+
| 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  || 3.1.0.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  || 3.1.0.RELEASE || Gemini Management 2.0 || Virgo IDE 1.0.1
 
|}
 
|}
  
Line 40: Line 52:
  
 
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.
 
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 ([https://bugs.eclipse.org/bugs/show_bug.cgi?id=358437#c4 rationale]), except for [https://bugs.eclipse.org/bugs/show_bug.cgi?id=358441 generalising the InstallArtifact tree to a DAG] which was implemented in Virgo 3.5.0 (see the Kernel Enhancements section of the [http://www.eclipse.org/virgo/download/release-notes/3.5.0.RELEASE.php Virgo 3.5.0 release notes]).

Latest revision as of 10:37, 11 April 2013


This page summarises the Virgo plan and notes design ideas for future Virgo features.

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

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.

Virgo Release Branding and Component Versions
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 3.1.0.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 3.1.0.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).