As a Developer I would like to automatically update the changelogs of all bricks and products with sections linking to new versions.
Rationale
As of now, a changelog with a section for a specific release can only be created when a single brick or product is selected by setting the version using a command line argument. When updating multiple (or all) changelogs together, the changes will only be put in the Unreleased section.
To allow better automation the update of many changelogs at the same time should automatically detect new releases and take them into account.
Technical Details
Describe technical details needed for the implementation of this story. MAY refer to an epic describing the details.
Product Details
Describe non technical details relevant for the product required by this story. I.e. legal requirements. MAY refer to an epic describing the details.
required if any
Acceptance Criteria
Describe the requirements that must be satisfied to be able to accept the story's implementation.
Related Issues
Add related issues. Can describe if an related issue is blocking the implementation of the story.
required if any
Stakeholder
The stakeholder affected by the Story / for whom this Story makes an impact.
Details
Preconditions
The (required) conditions before executing the Use Case
Basic Course of Events
A timely description of all events executing the Use Case normally
Alternative Paths
A timely description in respect to the former section to describe deviations from the usual path of events. E.g. in case of an error.
Postconditions
The (required) conditions after the execution of the Use Case. Must take into account all possible paths of execution.
As a Developer I would like to automatically update the changelogs of all bricks and products with sections linking to new versions.
Rationale
As of now, a changelog with a section for a specific release can only be created when a single brick or product is selected by setting the version using a command line argument. When updating multiple (or all) changelogs together, the changes will only be put in the Unreleased section.
To allow better automation the update of many changelogs at the same time should automatically detect new releases and take them into account.
Technical Details
Describe technical details needed for the implementation of this story. MAY refer to an epic describing the details.
Product Details
Describe non technical details relevant for the product required by this story. I.e. legal requirements. MAY refer to an epic describing the details.
required if any
Acceptance Criteria
Describe the requirements that must be satisfied to be able to accept the story's implementation.
Related Issues
Add related issues. Can describe if an related issue is blocking the implementation of the story.
required if any
Stakeholder
The stakeholder affected by the Story / for whom this Story makes an impact.
Details
Preconditions
The (required) conditions before executing the Use Case
Basic Course of Events
A timely description of all events executing the Use Case normally
Alternative Paths
A timely description in respect to the former section to describe deviations from the usual path of events. E.g. in case of an error.
Postconditions
The (required) conditions after the execution of the Use Case. Must take into account all possible paths of execution.