Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Automate Version / Release labeling for Document Notes #284

Closed
ToddCooper opened this issue Apr 5, 2024 · 0 comments · Fixed by #290
Closed

Automate Version / Release labeling for Document Notes #284

ToddCooper opened this issue Apr 5, 2024 · 0 comments · Fixed by #290
Assignees
@d-gregorczyk
Labels
Comment General Comment received outside of a normal review "period" Comment Review Comment of some sort from somewhere sometime Fix Spec Incremental issue with the published specification (version x.y.z with z being incremental)
Milestone
SDPi 1.4 Review

Comments

@ToddCooper
Copy link
Collaborator

Section Number

Entire document wherever release numbers are included

Priority

  • Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

Issue

Release version labels are used throughout the document to address specific release-specific observations, but many of these are automatically "pushed" to the next release (e.g., 1.2 becomes 1.3 becomes 1.4) when they remain unresolved. This results in often unnecessary work and a more automated approach should be implemented.

Proposed Change

A "current version" label should be created; however, this will not address all occurrences, since we sometimes mention the "current - 1" or "current + 1" version. Maybe we would need those 3 labels? (currentVersion, previousVersion, nextVersion).
@ToddCooper ToddCooper added Comment Review Comment of some sort from somewhere sometime Comment NEW A submitted comment waiting to be reviewed and dispositioned labels Apr 5, 2024
@ToddCooper ToddCooper added Comment General Comment received outside of a normal review "period" Fix Spec Incremental issue with the published specification (version x.y.z with z being incremental) and removed Comment NEW A submitted comment waiting to be reviewed and dispositioned labels Apr 5, 2024
@ToddCooper ToddCooper added this to the SDPi 1.4 review milestone Apr 12, 2024
d-gregorczyk added a commit that referenced this issue May 2, 2024
@d-gregorczyk
#284 Add variables for SDPi version string (short version number). Re…
8430ead 
…place version in text with variable.
@d-gregorczyk d-gregorczyk linked a pull request May 2, 2024 that will close this issue
#284 Add variables for SDPi version string (short version number) #290
Merged
2 tasks
d-gregorczyk added a commit that referenced this issue May 3, 2024
@d-gregorczyk
#284 Remove mentioning of specific subsequent SDPi version to avoid i…
1f0572a 
…nconsistencies after a release cycle.
d-gregorczyk added a commit that referenced this issue May 3, 2024
@d-gregorczyk
#284 Add CHANGELOG.md item
a4e4042
JavierEspina pushed a commit that referenced this issue May 3, 2024
@d-gregorczyk
#284 Add variables for SDPi version string (short version number) (#290)
37ce271 
* #284 Add variables for SDPi version string (short version number). Replace version in text with variable.

* #284 Remove mentioning of specific subsequent SDPi version to avoid inconsistencies after a release cycle.

* #284 Add CHANGELOG.md item
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@d-gregorczyk d-gregorczyk

Labels
Comment General Comment received outside of a normal review "period" Comment Review Comment of some sort from somewhere sometime Fix Spec Incremental issue with the published specification (version x.y.z with z being incremental)
Projects
Gemini SDPi Releases
Archived in project
Milestone
SDPi 1.4 Review
Development

Successfully merging a pull request may close this issue.

#284 Add variables for SDPi version string (short version number) IHE/DEV.SDPi
2 participants
@ToddCooper @d-gregorczyk