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

Document support tiers in Nixpkgs manual #244686

Closed
asymmetric opened this issue Jul 21, 2023 · 3 comments
Closed

Document support tiers in Nixpkgs manual #244686

asymmetric opened this issue Jul 21, 2023 · 3 comments
Assignees
Labels
6.topic: documentation Meta-discussion about documentation and its workflow

Comments

@asymmetric
Copy link
Contributor

asymmetric commented Jul 21, 2023

After RFC046 got merged, no documentation was added to the nixpkgs manual regarding support tiers.

This is the last state of the conversation.

cc @7c6f434c

@asymmetric asymmetric converted this from a draft issue Jul 21, 2023
@asymmetric asymmetric added the 6.topic: documentation Meta-discussion about documentation and its workflow label Jul 21, 2023
@asymmetric asymmetric moved this to ⚖ To Discuss in Nix documentation Jul 21, 2023
@asymmetric asymmetric self-assigned this Jul 24, 2023
@infinisil
Copy link
Member

Related: #143732 (discussed in the docs team meeting today)

@nixos-discourse
Copy link

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/2023-07-24-documentation-team-meeting-notes-66/30885/1

@asymmetric asymmetric moved this from ⚖ To Discuss to 🏁 Assigned in Nix documentation Jul 25, 2023
@fricklerhandwerk
Copy link
Contributor

Closed by #254741

@github-project-automation github-project-automation bot moved this from 🏁 Assigned to ✅ Done in Nix documentation Oct 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
6.topic: documentation Meta-discussion about documentation and its workflow
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants