[TYPO3-v4] Minutes of the 14th meeting of the 4.6 Release Team

[Xavier Perseguers]

Hi,

>> As such, we think that it could be wise to create a branch but not for
>> 4.6 but for "next TYPO3 version after master", leaving master being the
>> official branch for the upcoming 4.6 version. This will allow new
>> features to be committed while still concentrate on fixing bugs for 4.6.

> Sorry, that makes no sense. Branch 4.6 or branch it not, but master is
> always the head of development. Declaring it as not "the most recent
> version" would cause just confusion IMHO.

Then we should have a clear strategy with Gerrit. I don't want it to 
become the new bug tracker where patches are waiting there for ages.

What about some (manual) policy that a patch should be reviewed within a 
given timeframe? Otherwise it should go back to the bug tracker only. 
Thinking aloud here...

Cheers

-- 
Xavier Perseguers
Release Manager TYPO3 4.6

TYPO3 .... inspiring people to share!
Get involved: http://typo3.org