-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update stage object descriptions, release tags and planning process description #1415
Update stage object descriptions, release tags and planning process description #1415
Conversation
87d9a34
to
ed37c4e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just one suggestion. @yolile, feel free to merge if the suggestion is applied.
Regarding:
I think the use of "must" here is okay (typically, new "must" statements are not possible in a minor release), because a planning process is identified by the release tag or the tender.status (both of which are expected to align), such that the use of the 'tender' code would imply that the planning process is actually a contracting process – meaning that this new rule can't really be broken. That said, it's still useful to express as a rule, to avoid the blurring of the types of processes. |
Co-authored-by: James McKinney <[email protected]>
I meant @yolile, so that a reviewer merges, rather than the author :) But I can merge now. |
Closes #1385
Closes #866