Category:Virgo {{DEFAULTCATEGORYSORT:{{SUBPAGENAME}}}}

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.0.0 (Maya) Release

Theme: Eclipse RT integration

Schedule: July/August 2011

Draft Release Notes for 3.0.0

Content:

- Jetty support ( bug 321726)
- Use Equinox config admin instead of that of Felix ( bug 310217)
- Use Equinox log service instead of that of Felix ( bug 310218)
- Use Equinox event admin instead of that of Felix ( bug 310219)
- Upgrade Spring to 3.0.5 ( bug 314282)
- Rebase region support on OSGi framework hooks ( bug 330776)
- Tomcat 7/servlet 3.0 ( bug 332045)
- Make Virgo's web behaviour conform strictly to the OSGi web spec ( bug 326798)
- Support OSGi Log service ( bug 342716)
- Move the Kernel to DS to remove the fixed startup order ( bug 333474)
- Allows PARs to contain plans ( bug 335689)
- Remove entry/exit advice from hashCode() equals() and toString() methods ( bug 328033)
- Critical bug fixes

### Required CQs

5094 APPROVED Tomcat 7.0.12 Version: 7.0.12

5095 APPROVED Tomcat 7.0.12 Version: 7.0.12 (PB CQ5094)

5012 APPROVED Java Unified Expression Language Version: 2.2

5014 APPROVED javax.annotation Version: 1.1

5083 APPROVED Apache Felix Gogo Version: 0.8.01

5092 APPROVED org.apache.mina.core Version: 2.0.2

5091 APPROVED Apache SSHD Version: 0.5.0

4462 APPROVED javassist Version: 3.13.0.GA

## 3.5.0 (Bondi) Release

Theme: p2 and tooling integration

Schedule: July 2012

Draft Release Notes for 3.5.0

Content:

- Provision Virgo with p2 ( bug 343543)
- Virgo distribution based on p2 provisioning - Virgo Nano ( bug 364571)
- Upgrade from Spring DM to Gemini Blueprint ( bug 317943)
- Become a release train project ( bug 374214)
- Support for Virgo IDE tooling
- Critical bug fixes

### Required CQs

List of required CQs - approved

## Nice to Have

The following items currently do not fit in the above plans, but have been raised as desirable by one or more users:

- Admin console administration of remote Virgo instances
- Multiple user regions

## Future Releases

The following features are not currently in plan:

- p2 repository in the repository chain ( bug 309778)
- Support Java enterprise APIs(EJB, CDI, JPA, JSF, Web)
- Integration server
- Batch server

## 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
Brand | Runtime | Web Container | Eclipse IDE Tooling
Fern | SpringSource dm Server 1.0 | - | -
Emerald | SpringSource dm Server 2.0 | OSGi Web Container 1.0 | -
Cornflower | Virgo 2.1 | Gemini Web 1.1 | -
Maya | Virgo 3.0 | Gemini Web 2.0 | -
Bondi | Virgo 3.5 | Gemini Web 2.1 | Virgo IDE 1.0? - TBD | -
Sky | Virgo 3.6 or 4.0 | Gemini Web 2.1 or 2.2 | Virgo IDE 1.0? - TBD

Note 1: the following "wimp list" of colours that we are steering clear of: Azure, Indigo.

Note 2: the SpringSource dm Server releases are shade 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.