Reporting Work for XML Release#
Current Release Tickets#
The individual XML releases are defined as release artifacts on the Releases page from the CAP project page.
Clicking on the boat icon takes you to the list of releases that are currently available. The filters (Released, Unreleased and Archived) can be used to look at specific categories of all releases.
Clicking on one of the version names will take you to the status page of that release. From here you can see progress and the number of tickets in the various lifecycle stages.
To see the list of tickets in the release, click on the “Issues in version” listing in the ticket status tabs. Now one can see the tickets that are assigned to this release.
Now one can determine if a CAP ticket is available to link work tickets into or one needs to be created before linking work tickets. If you see a potential CAP to use for linking, make sure you read the description and ask questions of the reporter if necessary to determine if it’s the right place for your work. Just sticking tickets in random locations is not acceptable. If there is no description on the ticket, please publicly shame the reporter on the #se-software-interact Slack channel to have one written. Make sure to reference the offending ticket.
Creating a CAP Ticket#
If you determine that no current CAP ticket suits your needs, please create one. You can make it generic so that others might be able to use it to link work, just make sure you have a description that describes your intention for the ticket. While the ticket creation is a standard process, the one thing to remember is to assign the release artifact during ticket creation. The “Fix Version/s” field is part of standard ticket types (not Epic) and has a dropdown that shows all releases, both unreleased and released. Please pick the appropriate unreleased version for the ticket.
In order for a release to proceed, all tickets associated with that release must be closed. While the policy for closing tickets varies depending on the ticket in question, the need has arisen for the case where a linked ticket (usually a DM ticket) must stay open beyond the XML work. If a ticket falls into this category, the label xmldone must be added to the ticket once the XML work is completed and merged. This will indicate to the release manager that the necessary work is complete for the release.