-
Notifications
You must be signed in to change notification settings - Fork 87
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
Align with official release strategy and adjust constraints #847
Labels
Comments
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 5, 2024
7 tasks
aj-stein-gsa
added a commit
to aj-stein-gsa/automate.fedramp.gov
that referenced
this issue
Nov 5, 2024
The content is generally correct, but the tags are not actually SemVer. They are halfway between the "soon-to-be-deprecated" approach from the ADR permalinked below. A new ADR is forthcoming. https://github.com/GSA/fedramp-automation/blob/fcdd25e3177d4bf31178041648fdc74d610146e9/documents/adr/0002-git-release-version-strategy.md
2 tasks
aj-stein-gsa
added a commit
to aj-stein-gsa/automate.fedramp.gov
that referenced
this issue
Nov 5, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 5, 2024
7 tasks
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 5, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 5, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 5, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 6, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 6, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 6, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/fedramp-automation
that referenced
this issue
Nov 6, 2024
aj-stein-gsa
added a commit
to aj-stein-gsa/automate.fedramp.gov
that referenced
this issue
Nov 6, 2024
aj-stein-gsa
added a commit
that referenced
this issue
Nov 12, 2024
Closed
aj-stein-gsa
added a commit
that referenced
this issue
Nov 14, 2024
…rsioning Use (#866) * [skip ci] Deprecate ADR2, backport "new" #847 ADR * [skip ci] Context and decision in #847 ADR * [skip ci] Add two options to #847 ADR * [skip ci] Add option 3, finalize #847 ADR * Apply very valid feedback during review from @Rene2mt Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> * [skip ci] Clarify ADR 10 explanation of past work per @Rene2mt review of #866 Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> * [skip ci] Add missing info to ADR 10 per @Rene2mt's #866 review Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov> --------- Co-authored-by: Rene Tshiteya <rene-claude.tshiteya@gsa.gov>
aj-stein-gsa
added a commit
to GSA/automate.fedramp.gov
that referenced
this issue
Nov 14, 2024
* Fix tags in release page to be SemVer for GSA/fedramp-automation#847 The content is generally correct, but the tags are not actually SemVer. They are halfway between the "soon-to-be-deprecated" approach from the ADR permalinked below. A new ADR is forthcoming. https://github.com/GSA/fedramp-automation/blob/fcdd25e3177d4bf31178041648fdc74d610146e9/documents/adr/0002-git-release-version-strategy.md * Add callouts deprecating Spock versions for GSA/fedramp-automation#847 * Add placeholder ADR 10 link to wrap up GSA/fedramp-automation#847 * Remove redundant phrase per @brian-ruf's review * Update with links to finalized ADR 10 from #866 as part of #847, prep for review
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This relates to ...
What happened?
During pairing on constraint develop around checking
fedramp-version
andoscal-version
, colleagues reported that the ADR#2 in repo version of our release strategy is not the same as our canonical updated version on the website (at this time from87a0d60
). The latter was after much feedback from the community that the former had significant drawback. This was decided but not aligned, so we now need to align it.What needs FedRAMP developer review?
Relevant log output
No response
How do we replicate this issue?
Where, exactly?
In multiple locations, see below.
Other relevant details
Expected fixes:
fedramp-3.0.0
per example. Correct and update align release guidance automate.fedramp.gov#104The text was updated successfully, but these errors were encountered: