No changelog/release #86
Labels
Comments
|
Absolutely true. One of the problem being that I'm currently a "maintainer by default", as I'm not using the package in any of my projects, so I'm doing what I consider the minimum maintenance. |
adamchainz
pushed a commit
to adamchainz/django-contrib-comments
that referenced
this issue
May 8, 2016
Fixes django#86. * Added HISTORY.rst to the repo and backfilled it for all the releases down to 1.6.0 * Updated setup.py to copy the `long_description` strategy [from cookiecutter-pypackage](https://github.com/audreyr/cookiecutter-pypackage/blob/master/%7B%7Bcookiecutter.project_slug%7D%7D/setup.py), which pushes the changelog to PyPI so it's easy to find
claudep
pushed a commit
that referenced
this issue
May 10, 2016
Fixes #86. * Added HISTORY.rst to the repo and backfilled it for all the releases down to 1.6.0 * Updated setup.py to copy the `long_description` strategy [from cookiecutter-pypackage](https://github.com/audreyr/cookiecutter-pypackage/blob/master/%7B%7Bcookiecutter.project_slug%7D%7D/setup.py), which pushes the changelog to PyPI so it's easy to find
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrading
django-contrib-commentsis hard because there is no changelog, I have to read the git log and guess if anything affects the projectThe text was updated successfully, but these errors were encountered: