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

- Added CHANGES file (auto-generated). #2

Closed
wants to merge 1 commit into from

Conversation

manwar
Copy link

@manwar manwar commented Dec 14, 2015

HI Ari, please review the above change.

Many Thanks.
Best Regards,
Mohammad S Anwar

@ajolma
Copy link
Owner

ajolma commented Dec 15, 2015

How does one update the CHANGES file when making a release? (I guess it is a FAQ, but anyway).

@manwar
Copy link
Author

manwar commented Dec 15, 2015

You have two choices:

  1. Manually add the change details to the CHANGES file

or

  1. Use tool like Dist::Zilla, to automagically update CHANGES file every time you release.

If you opt for #2, I can submit PR with the proposed changes.

Best Regards,
Mohammad S Anwar

@ajolma
Copy link
Owner

ajolma commented Dec 15, 2015

There's "svn log >Changes" but that seems quite stupid since if one is really interested then they can simply come to github and see it themselves. And the commit messages are often quite cryptic.

I personally have found very little use for Changes files so I haven't thought so much about them.

But apparently some people use them. There's for example this blog http://blog.urth.org/2011/01/27/changes-file-how-and-how-not-to/

Hm. I'll try to improve this aspect of my modules.

@ajolma
Copy link
Owner

ajolma commented Dec 15, 2015

Added now a manual Changes file. Did the same for WFS and will do the same for WMTS.

@ajolma ajolma closed this Dec 15, 2015
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.

None yet

2 participants