-
Notifications
You must be signed in to change notification settings - Fork 0
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
Write a policy about the use of CHaP #13
Comments
michaelpj
added a commit
that referenced
this issue
Oct 7, 2022
This reflects the policy that we have to follow now that the node is [using CHaP](IntersectMBO/cardano-node#4411). It also lays out a draft of a policy for when it can be appropriate to release to Hackage, and when it is appropriate to use `source-repository-package`s. Fixes #13.
michaelpj
added a commit
that referenced
this issue
Oct 7, 2022
This reflects the policy that we have to follow now that the node is [using CHaP](IntersectMBO/cardano-node#4411). It also lays out a draft of a policy for when it can be appropriate to release to Hackage, and when it is appropriate to use `source-repository-package`s. Fixes #13.
michaelpj
added a commit
that referenced
this issue
Oct 7, 2022
This reflects the policy that packages have to follow now that the node is [using CHaP](IntersectMBO/cardano-node#4411). It also lays out a draft of a policy for when it can be appropriate to release to Hackage, and when it is appropriate to use `source-repository-package`s. Fixes #13.
michaelpj
added a commit
that referenced
this issue
Oct 7, 2022
This reflects the policy that packages have to follow now that the node is [using CHaP](IntersectMBO/cardano-node#4411). It also lays out a draft of a policy for when it can be appropriate to release to Hackage, and when it is appropriate to use `source-repository-package`s. Fixes #13.
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
... once we agree we're going to use it fully.
The text was updated successfully, but these errors were encountered: