TYPO3 Core

Hi Robert,

for this a SOAP method to retrieve the (cumulated) changelog entries for an extension would be needed in TER. Just assign this big to me if you implemented that. :)

Karsten

I have a different suggestion: Please should use the Changelog file instead of entering information while uploading the extension. If I may decide, I just drop support of entering upload comments and only display the last few lines from the Changelog file.

What about that?

Huh, even better. I tend to look into the ChangeLog file, and more often than not it's the default generated by the kickstarter...

I always have found the upload comments a hassle, and like idea of displaying the extension's ChangeLog file. Yet, I see three possible issues and would like some opinions on those:

1. Currently, in the manual template, there also is a changelog section. We should have one "official place" for the changelog: either the file ChangeLog (which I'd prefer) or the changelog in the manual

2. The changelog is one big file. How do we make sure that we only display the changes for the current version?

3. Actually, some kind of release notes that only list the most important changes, possible issues and things that should be considered while updating would be of more use when an administrator wants to update an extension and would like to know if the update is safe and which configuration schanges the update will bring.

When you upload, there is a field "changelog for update".
The content of this field is displayed in TER when downloading an extension manually and in TYPO3 when doing an update using the EM.

So I'd call this fixed.

The submodule "check for extension updates" shows this info