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

Add a policy on Haskell package distribution #23

Merged
merged 1 commit into from
Oct 18, 2022

Conversation

michaelpj
Copy link
Collaborator

This reflects the policy that we have to follow now that the node is using CHaP.

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-packages.

This policy should not be merged until most of the Cardano Haskell packages are in compliance (i.e. are using CHaP).

Fixes #13.

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.

A package which is released to Hackage that was previously released to CHaP MUST be released to Hackage with a higher version number than any version number under which it appears in CHaP.

The Hackage user [iogospo](https://hackage.haskell.org/user/iogospo) MUST be included as a maintainer of the package on Hackage.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What iogospo stands for? IOG Open-Source Package O...?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea, it was on an existing page 🤷

@abailly-iohk abailly-iohk merged commit 85ad582 into main Oct 18, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write a policy about the use of CHaP
4 participants