Closed astrofrog closed 9 years ago
We should also create a CHANGES.md
file to keep track of changes between tags, so that people not using git to merge in changes know which files have changed.
Now that the package-template has been updated to v0.4.1, I have tagged v0.4
of the package-template. No tar file release or anything, but it will help affiliated package template maintainers keep track of changes.
I've created a v0.4 milestone and assigned a few issues to it. Once those are done, I can tag v0.4 which just means that this is the recommended version to work with astropy v0.4 and the astropy-helpers. We don't have to actually make release tar files, but having tags will at least help affiliated package maintainers be able to refer to a version of the template. As for the helpers, it makes sense to pick a version that will roughly follow astropy so that it's easy to see the correspondence.