Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clarifies the "Handling deprecated services" section

...

Handling deprecated services

We tag code deprecated deprecated services as a part of a release and  these code branch using the "<deprecated" element. Deprecated services will be removed from next release package.

Lets say we set a service as deprecated for Release 17.XX as deprecated for a service, this service  . This service will be part of Release17.XX and will be removed in next Release 18.XX
Imagine we are the 30 december 2019 and .

For instance, imagine we decide to create a new releasenext to be released R19 branch.
We have on trunk :

  • addCatalogMember deprecated since="next releaseUpcoming Branch"
  • deleteWorkEffortAssignment deprecated since="18.12"

We prepare the release branch, we have on trunk :

  • addCatalogMember deprecated since="19.12"
  • deleteWorkEffortAssignment deprecated since="18.12"

We create the stable branchenew R19 branch, and after clean the trunk. Now on trunk we have :

...