Adding or Removing a CSC from the XML Interface#

The following document lays out the procedure for adding or removing a CSC from the XML interface. There are also instructions on the workflow to update an version of OpenSplice.

Add/Rename a CSC#

  1. A subsystem representative must announce the intention to add a new or rename an existing CSC at the weekly CAP meeting.

  2. A new CAP Jira ticket must be created. Using established CAP tickets is not permitted

  3. The Summary for the ticket must start with the following text: (ADD) if adding or (RENAME) if renaming.

  4. The ticket must contain the following label: add_csc if adding or rename_csc if renaming

  5. The ticket must be tied to the XML version where the new or renamed CSC will be added.

  6. Work on the new CSC proceeds as normal

Remove a CSC#

  1. A subsystem representative must announce the intention to remove an existing CSC at the weekly CAP meeting.

  2. A new CAP Jira ticket must be created. Using established CAP tickets is not permitted.

  3. The Summary for the ticket must start with the following text: (REMOVE)

  4. The ticket must contain the following label: remove_csc

  5. The ticket must be tied to the XML version where the CSC will be removed.

  6. Work on removing the CSC proceeds as normal

Changing the OpenSplice Version#

  1. A subsystem representative must announce the intention to update the openSplice version at the weekly CAP meeting.

  2. A new CAP Jira ticket must be created. Using established CAP tickets is not permitted.

  3. The Summary for the ticket must start with the following text (UPDATE OPENSPLICE)

  4. The ticket must be tied to opensplice version that we are updating to.

  5. Work on updating openSplice proceeds as normal.

Before Release Procedure#

Before it is time to perform the XML release, the XML Work Coordinator and Build/Release Coordinator must meet to review the release tickets. This will ensure that added or removed CSCs will be properly addressed heading into the build process.