Skip to content

Please, document a workflow on the support of new GHCs #2545

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

Open
Anton-Latukha opened this issue Dec 27, 2021 · 2 comments · May be fixed by #2548
Open

Please, document a workflow on the support of new GHCs #2545

Anton-Latukha opened this issue Dec 27, 2021 · 2 comments · May be fixed by #2548
Labels
type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc.. type: enhancement New feature or request

Comments

@Anton-Latukha
Copy link
Collaborator

Support of new versions is a constant periodic task.

Denoting main steps/phases would allow for reports as #2541 & for maintainers & users to be more context-aware of the process. So the tracking reports created would have a more stable form & the process would be easier to track.

@Anton-Latukha
Copy link
Collaborator Author

Anton-Latukha commented Dec 27, 2021

@Anton-Latukha
Copy link
Collaborator Author

Since I need to #2525 anyway - I would go into some doc PR mode. Would do a bunch of doc pattern work. Like, open a minimal PR adding 9.0.2 information & ghcup dependency-aware description of GHC support process information from #2541.

@fendor fendor added type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc.. and removed old_type: documentation labels Jul 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't right: doesn't work as intended, documentation is missing/outdated, etc.. type: enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants