I think its cool to have some documentation in the module itself as far as changes, but it doesn't make much sense to create a text file for a specific release. We should do a CHANGELOG.txt which is what is pretty standard in all kinds of software.

I think it is more important to to make descriptive releases as we have been doing that we can highlight on the project page when necessary, as I don't think many people will read a CHANGELOG.txt, but its still nice to have.

Comments

tmcw’s picture

tmcw commented

Yeah, it's unstandard, and I'll consider changing it back. I'm just imagining that users upgrading from alpha3 to alpha4 will not expect things to break and won't know how to fix them, and hence bug reports / support requests.

zzolo’s picture

zzolo commented

I totally agree, but its more appropriate to have a CHANGELOG.txt and many other places to ensure people know about the change, like the project page, in the release notes, a note in the README, etc.

zzolo’s picture

zzolo commented

It may be good to put the CHANGELOG.txt into the root director for the module as to make it more obvious.

tmcw’s picture

tmcw commented
Status: Active » Fixed

Committed: http://drupal.org/cvs?commit=352080

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.