 |
OSS/J APIs Release Process and Dates
The OSS/J release process has been designed to allow the release of the OSS/J APIs in a consistent and progressive way.
All OSS/J functional APIs are based on the Common API that specifies common interfaces and common data (CBEs) for at least two functional APIs.
A new version of the Common API is released only if functional APIs require changes in the CBEs or applied design guidelines. Otherwise the current version of the Common API has to be used. A new version of the Common API is released once a year at the most.
The Functional API Spec Leader has the responsibility to declare the parts of the Common API used as "stable": these parts are then consider "frozen" for the next version of the Common API.
APIs Release schedule
APIs based on JSR144 - Common API, Maintenance Release 5 (v1.5):
- JSR91 - OSS Trouble Ticket, Maintenance Release 2 (v1.2): published in Aug 07
- JSR142 - OSS Inventory, Maintenance Release 2 (v1.2): published in Aug 07
- JSR263 - Fault Management, Final Release (v1.0): published in Sep 07
- JSR264 - Order Management, Final Release (v1.0): published in Sep 07
- JSR210 - Service Quality Management, Final Release (v1.0): target: Mar 08
- JSR251 - Pricing, Final Release (v1.0): target: Mar 08
- JSR254 - Discovery, Final Release (v1.0): target: Feb 08
Detailed API release steps and deadlines are described here.
Information on other APIs
- JSR89 - OSS Service Activation - Available: Final Release - V1.0: no maintenance releases planned. Replaced by JSR264 Order Management
- JSR90 - OSS Quality of Service - Available: Final Release - V1.0: no maintenance releases planned. Fault Management part replaced by JSR263 Fault Management. The Performance Management part will be replaced by JSR285 Performance Management
- For information about the current status of the other APIs, please check the OSS/J API download page.
-- AntonioPlutino - 07 Jan 2008
|