[TYPO3-mvc] [RFC] Keeping FLOW3 Compatibility

Claus Due claus at wildside.dk
Mon Feb 13 13:19:17 CET 2012

Hi Sebastian,

On Feb 13, 2012, at 6:30 AM, Sebastian Kurfürst wrote:

> We extend the commit guidelines for both projects, Extbase and FLOW3, a
> little, in a way that we include a "Extbase Issue:" or "FLOW3 Issue:"
> line inside the commit message, pointing to the corresponding Extbase or
> FLOW3 issue... An example for Extbase:


> This, IMHO, provides the following benefits:
>  * the issue tracker serves as ToDo list for both FLOW3 and Extbase
>    project members
>  * Each project member in FLOW3 and in Extbase team has to *consciously
>    think about the sister-project* when creating a patch.
>  * ... and every reviewer thinks about it, too.
>  * If we disagree if a certain feature should be back/forwardported,
>    this is just part of our regular review process.
>  * However, it does not block innovation in either Extbase or FLOW3, as
>    it could certainly be that an issue is not fixed in FLOW3 yet while
>    it is fixed in Extbase (or the other way round).
> In a nutshell, I propose:
>  * changing the commit message policy a little, creating tracking
>    issues for the other sister-project
>  * read the scrum protocols of FLOW3 Devs
>  * try to set up something similar like the Scrum protocols for Extbase
>    (though I have no idea yet how this could practically work)
> What do you think about these ideas?

My reaction:

Yes, yes, yes, YES! and yes.

Then yes, yes and finally "SCRUM? When do we start?"



More information about the TYPO3-project-typo3v4mvc mailing list