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.

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

Move ConfigRevision from extras to core #13648

Closed
jeremystretch opened this issue Aug 31, 2023 · 1 comment
Closed

Move ConfigRevision from extras to core #13648

jeremystretch opened this issue Aug 31, 2023 · 1 comment
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user

Comments

@jeremystretch
Copy link
Member

Proposed Changes

Move the ConfigRevision model from extras to core.

Justification

The active configuration and its revisions are considered core components of the application, as opposed to optional extensions.

@jeremystretch jeremystretch added status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user labels Aug 31, 2023
@jeremystretch jeremystretch added this to the v4.0 milestone Aug 31, 2023
@jeremystretch
Copy link
Member Author

I duplicated this under #14312 for v3.7. 🙄

@jeremystretch jeremystretch removed this from the v4.0 milestone Dec 7, 2023
@jeremystretch jeremystretch closed this as not planned Won't fix, can't repro, duplicate, stale Dec 7, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: housekeeping Changes to the application which do not directly impact the end user
Projects
None yet
Development

No branches or pull requests

1 participant