Discontinuing the CMS Changelog.txt in Favor of...

[Nick Savov]

The Production Leadership Team (PLT) has decided to discontinue the CMS changelog.txt file, because we have a much better changelog available now through Git. Therefore, we will be using GitHub’s built-in tools instead of the manually created changelog.txt file.

You can view the new changelogs at:

Joomla 3:

https://github.com/joomla/joomla-cms/commits/master

Joomla 2.5:

https://github.com/joomla/joomla-cms/commits/2.5.x

Please let us know if you have any questions and we'll be glad to answer. Thanks!

Cheers,

Nick

[brian teeman]

Will there still be a changelog file included in the download zip

[Donald Gilbert]

Good question Brian. I think we overlooked that when discussing.

No worries though, if it is decided that it's still needed, it's relatively simple to create a changelog from github commit history. In fact, Andrew has created a tool to automate this process as well, so I don't think it's that big of a deal.

The PLT will get an official answer for you though, hopefully soon.

[brian teeman]

Thanks 

I asked because a lot of us old time open source geeks are used to checking the changelog of everything we download

[Andrew Eddie]

Github gives us a lot of different ways to provide a changelog. A new one is releases and we can likely automate the change notes with those. Here's an example for the Framework:

https://github.com/joomla/joomla-framework/releases/tag/1.0-beta3

We could include the file as a part of the build process (scrape the pull requests for a tag) but removing it will chop a few seconds off processing each pull request (time the user can spend on writing docs, hehe).

Regards,

Andrew Eddie

[Dmitry Rekun]

Looks awesome +1

Dmitry

[Hassan Amouhzi]

Hello,

Github use this https://github.com/eddieajau/tagaliser to generate Changelog.