[MCHANGES-412] Allow an action to carry an optional scope

• Type: New Feature
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: changes.xml
• Assignee: Unassigned
• Reporter: Gary D. Gregory
• Created: 29/Sep/22 14:02
• Updated: 05/Oct/24 18:08

Description

In changes.xml, I would like an action to carry an optional scope.

This would help users understand what changes affect which part of their projects.

For example:

<action issue="ABC-189" type="fix" scope="runtime">Fix some bug</action>
<action issue="ABC-190" type="update" scope="test">Bump dependency foo from 1 to 2</action>
<action issue="ABC-191" type="update" scope="build">Bump commons-parent foo from 1 to 2</action>
<action issue="ABC-191" type="update" scope="site">Documented this and that</action>

The use of the scope documents where the change applies, usually runtime, test, or build, but it could be string maybe.

This somewhat parallels the concept of a scope in a dependency so the value set could be the same as allowed for a dependency scope but that might be too restrictive.

Thoughts?