Skip to content

"When the project has made a release" is confusing #422

@ericcornelissen

Description

@ericcornelissen

Does it mean "if there has ever been a release do X" or "for every release do X"? For some controls the former makes sense (e.g. OSPS-SA-03.02) while for other controls the latter makes sense (e.g. OSPS-QA-02.02) to me.

If it's the former, what's the point? Why would I follow this checklist for a project that will never be released? If the release hasn't happened yet, of course I won't do release-related tasks until there is a release.

This problem is very similar to #398

Metadata

Metadata

Assignees

Labels

bugSomething isn't workingcriteria

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions