The CHANGELOG.txt included with the module refers to 6.x.

Comments

xiukun.zhou’s picture

Status: Active » Fixed

Thanks klonos.

It's more time this got committed and I went ahead and had this rolled at:

7.x-2.x: d591e43.

7.x-2.x: 984138d.

7.x-2.x: 898ecab.

Marking this as fixed.

Please let me know if you would have any other questions, comments, issues or concerns on any of these changes, I would be glad to provide more information.
Thanks again to everyne for the help and great work on this issue.

Cheers!

klonos’s picture

Status: Fixed » Needs work

...just a minor thing: it is accustomed to have latest versions added to the top of the file (that's how the 6.x version of the CHANGELOG.txt was). So I guess you'll have to reorder the versions mentioned in the log in descending order.

xiukun.zhou’s picture

Hi klonos,
I do not think is right. you see ctools 6.x and 7.x of CHANGELOG.txt.

klonos’s picture

Yes. I guess then it's a matter of personal taste of the maintainer. But I had core's CHANGELOG.txt in mind that lists changes with newest at the top.

Also, the way I see it, having the latest changes at the top of the file has benefits for both the people reading the file as well as for people keeping it up to date. Those reading it don't have to scroll all the way down to see what has changed compared to the previous version and those that need to update the file need only open it and start typing - no scrolling for them either. These benefits get more value as the file grows larger and larger.

Anyways, I'm sure that if you want it with oldest at the top, you have your reasons so I won't insist any further. That main goal of this issue was about updating the file to include the 7.x branch's changes. That was done, so thank you :)

xiukun.zhou’s picture

Status: Needs work » Fixed

Status: Fixed » Closed (fixed)

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