[TYPO3-core] Review system woes

[Philipp Gampe]

Hi Thorsten Kahler,

Thorsten Kahler wrote:

>>
>> IMHO the issue tracker is for discussing the problem, make it
>> reproducible and find out under which condition a bug triggers.
>>
>> For me that is something completely different then the code change and
>> the comments related to the change. The change review system is for
>> discussing the best strategies to code the specific feature or bugfix.
> 
> IMHO "strategies" belong to the bug tracker because
> 
> - there should be an agreement on how to solve issues before somebody
> starts to implement a solution
> - Forge has better support for markup, links etc. so it's much easier to
> follow discussions, add examples and so on

+1

>> It allows to
>> comment on code smells and anti-patterns, as well as unwanted side
>> effects. It is the technical part.
> 
> Yep, that's the domain of a review system.

Best regards
-- 
Philipp Gampe – PGP-Key 0AD96065 – TYPO3 UG Bonn/Köln
Documentation – linkvalidator
TYPO3 .... inspiring people to share!