[TYPO3-core] Review system woes
Alexander Opitz
alexander.opitz at netresearch.de
Thu Feb 7 16:47:51 CET 2013
Hi,
in short I can say: "Me too".
Reported http://forge.typo3.org/issues/16472 on 15.08.2006, but nobody
seems to do anything. The Bug is unfixed since years.
On the other side http://forge.typo3.org/issues/33165, patched more or
less in one day, no chance to response to the patch, no response
afterwards to my hints. A follow up bug to this
http://forge.typo3.org/issues/38781 didn't get any response.
http://forge.typo3.org/issues/38838, Accepted but no response.
And there are much more. As nobody changes the Target Version, they all
fall out of the roadmap overview page. (Beside of that, bugs in multiple
releases should get multiple target versions.) So nobody sees, what will
realy be done in a release.
On the other side, bugs having a target versions aren't respected at
release date. http://forge.typo3.org/issues/43244
Doesn't get ready for 6.0.0 and then forgotten for 6.0.1.
Another problem since gerrit seems the handling of patches. There are
comments in gerrit which aren't seen in the bug report and vice versa,
so informations and hints got lost. Beside of this, I don't know why I
should write a test scenario inside a commit message when all should be
described in the bug report, how to reproduce.
Greetings Alex//
--
Viele Grüße
Alexander Opitz
Developer
T: +49 341 47842 15
++++++++++++++
Netresearch - Passion for eCommerce
++++++++++++++
Netresearch GmbH & Co. KG
Nonnenstraße 11d - 04229 Leipzig
http://www.netresearch.de
Registergericht: AG Leipzig HRA 15614
Komplementär: Netresearch Beteiligungs GmbH, AG Leipzig HRB 17018
Geschäftsführer: Michael Ablass
More information about the TYPO3-team-core
mailing list