[TYPO3-team-core-v5] Sprint Review

Christopher Hlubek hlubek at networkteam.com
Tue May 18 15:05:49 CEST 2010


Hi Robert,

Robert Lemke schrieb:
> The second thing is that contributions like for example the Page-Not-Found handling was implemented at a wrong place. I'd consider this a technical debt and therefore it wasn't done done  - so the question is what implications that has on the sprint.
>   
I'd like to say that I couldn't find a better way to implement that for 
now without changing FLOW3 internals (maybe I've missed something) and I 
think it's better to have it in place than having the previous error. I 
agree that this is not the final solution (is anything in FLOW3 or 
Phoenix final?) but the exception handling is not working for that right 
now (it doesn't seem possible to use a exception handler from another 
package and there's no flexible handling of exceptions inside of 
controllers yet). I think this is a problem that would have been 
discussed in a daily scrum with some more time, but as you said, the 
time management is difficult and it just occured that I had the most 
time in the last day(s) of the sprint.

I generally think we have to create another task / story to enable a 
better solution for some code in another sprint but I think it shouldn't 
stop us from getting stuff done. Otherwise we would always move 
something around / open new issues to get a (sometimes subjective) best 
solution without even getting something "real".

Greetings,

Christopher


More information about the TYPO3-team-core-v5 mailing list