Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.Hi, I've included a CHANGELOG.txt file for each branch (as result of a short conv in IRC with webchick) that should be updated from now on. I've included previous CVS operations (removing small issues) in the files.
Just as a reminder: Commit messages - providing history and credit, includes changelog recommendations.
Does not worth create the issue for the 6.x-1.x branch.
Comments
Comment #1
dave reidIs a changelog really necessary for this project? We have CVS commit messages and cvs.drupal.org to look at history. I'm just wondering what we gain in this project by adhering to the formality.
Comment #2
rfayIMO a changelog that just shows new examples being added is probably useful. Sometimes, especially with a module like this, you might check in on it every year or two and have no idea what's new.
Comment #3
dave reidOk, having only major changes and additions sounds good. I tend to break my commits into small and manageable sizes, and I don't like to put every. single. one. of. them. into CHANGELOG.txt files. Especially if it's things like fixing coding standards or small trivial changes. :)
Comment #4
ilo commentedI have populated CHANGELOG with current cvs commit messages according to each branch, but we can remove some of them if you want. I agree that being so instructive about any minor change as sun does may render changelog difficult to read, specially if module is being under constant changes and reviews as examples module is being now, but this is a something that will finish soon, once the module finds a more stable situation.
Comment #5
rfayIMO this isn't terribly important.
However, my practice is to add the commit message to the CHANGELOG.txt within each module as I do it. I helps to keep that history.