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

document support policy #466

Closed
1 task
goern opened this issue Oct 17, 2022 · 2 comments · Fixed by #476
Closed
1 task

document support policy #466

goern opened this issue Oct 17, 2022 · 2 comments · Fixed by #476
Assignees
@goern
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@goern
Copy link
Member

goern commented Oct 17, 2022

Problem statement

As a developer, I want to know which versions of python and environments are supported by thoth

Additional context

the policy should answer questions like thoth-station/solver#5191

Acceptance Criteria

  • support policy published

/kind documentation
/priority critical-urgent
/assign @goern
@goern goern added the kind/feature Categorizes issue or PR as related to a new feature. label Oct 17, 2022
@sesheta sesheta added kind/documentation Categorizes issue or PR as related to documentation. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Oct 17, 2022
@sesheta
Copy link
Member

sesheta commented Oct 17, 2022

@goern: This issue is currently awaiting triage.
If a refinement session determines this is a relevant issue, it will accept the issue by applying the
triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@sesheta sesheta added needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. needs-sig labels Oct 17, 2022
@goern goern moved this to 🆕 New in Planning Board Oct 17, 2022
@goern goern added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Oct 17, 2022
@goern goern moved this from 🆕 New to 🏗 In progress in Planning Board Oct 17, 2022
@goern
Copy link
Member Author

goern commented Oct 17, 2022

/sig user-experience

@sesheta sesheta added sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. and removed needs-sig labels Oct 17, 2022
@goern goern mentioned this issue Dec 15, 2022
Merged
@codificat codificat mentioned this issue Dec 23, 2022
Open
Repository owner moved this from 🏗 In progress to ✅ Done in Planning Board Dec 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@goern goern

Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/feature Categorizes issue or PR as related to a new feature. lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. needs-triage Indicates an issue or PR lacks a `triage/...` label and requires one. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Planning Board
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add support policy document
2 participants
@goern @sesheta