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

Split charms.txt into charms.txt and release-charms.txt to signal the difference between maintained charms and released charms #135

Open

ajkavanagh opened this issue Feb 10, 2021 · 0 comments

Contributor

ajkavanagh commented Feb 10, 2021

Essentially, this distinction is:

charms.txt - all the charms that need to have their requirements.txt, tox.ini, etc. maintained (along with to-be-announced upper-constraints.txt) that we want to keep in sync across all the charms.
release-charms.txt - the charms that get pushed to the charm store as stable releases.

i.e. charms.txt is ALL the charms. release-charms.txt is a subset of the released/SLA charms.

The tooling will need to be adjusted so that they use the correct charms.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment