[TYPO3-core] Target Versions in TYPO3 CMS Issue Tracker

Philipp Gampe philipp.gampe at typo3.org
Sat May 18 02:17:25 CEST 2013

Hi Ernesto,

Ernesto Baschny wrote:

> d) Introduce a simple rule for issue updaters: *Noone* should ever set a
> Target Version other than the Release Team! Only exception might be
> Subprojects which could manager their own Roadmap (i.e. Extbase) but of
> course in coordination with the Release Team.
> What do you think about that?

IMHO this comes closest to what I think the target field is for.

full +1

While you are at it, I think we also need to work on the various 
categories/subproject trackers.
e.g. there is a category for scheduler and a subproject. This makes it very 
hard to keep track on what needs to be changed. Subprojects do not inherit 
the rights from the super project which makes it very hard to update issues 
Some sysext some own categories, but most have none. I would suggest to 
create a category for each sysext plus a few global ones (e.g. FAL).
Then we should get rid of all subprojects but those which have a real team 
(e.g. extbase, fluid). IMHO it does not make much sense to have a subproject 
for dbal, linkvalidator, scheduler, etc - even if they are currently inside 
a submodule (which will be resolved anyway).

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

More information about the TYPO3-team-core mailing list