[TYPO3-v4] What has been fixed in which release?

[Ernesto Baschny [cron IT]]

Hi,

small follow-up on this one:

	http://www.typo3-anbieter.de/typo3-merges/

Instead of a table of "dates" you can now see in which release exactly
which fix was included (i.e. 4.5.5 or 4.6.0beta2). The mouse-over still
shows the date. And showing the now obsolete "4.2" was dropped.

I had send this script some months ago to Stucki to make this available
on some official typo3.org server, but we haven't got a chance to chat
more deeply or to really get it "done". So meanwhile still on my
servers, but none the less somehow useful.

Cheers,
Ernesto

Ernesto Baschny [cron IT] schrieb am 28.06.2011 18:09:

> starting with Git/Gerrit it got a bit more difficult to really see what
> Bugfix was ported to which release of TYPO3v4. Well, it was also
> difficult before that (tedious comparison of ChangeLogs).
> 
> Since we have so many cool ways of querying information from Git, I
> build a small script that presents an overview of merges that happened
> on the releases we are still maintaining.
> 
> 	http://www.typo3-anbieter.de/typo3-merges/
> 
> This allows us to see:
> 
> 1) what bugfix we might still want to backport from master to older
> branches.
> 
> 2) (more important): in some cases these backports were explicitly
> desired by the original author (including a "Releases:" tag in the
> commit message for master). If those are still pending, they are listed
> as "TODO" in the table.
> 
> 3) (most important!) what bugfixes we have commited to 4.5 or earlier
> which are *not yet* applied to 4.6.
> 
> The table is updated three times a day, maybe someone (besides the
> release management...) might find it useful.
> 
> Note: only commits with unique (and correct) "Fixes:" or "Resolves:"
> lines in the commit message can be displayed here, because the issue# is
> the only thing that "links" the merges together.
> 
> Cheers,
> Ernesto