[TYPO3-team-core-v5] TYPO3 Phoenix Scrum Meeting Notes - 23.04.2012
Christopher Hlubek
hlubek at networkteam.com
Mon Apr 23 12:05:24 CEST 2012
Hi Phoenix Team,
sorry, I couldn't attend the daily scrum last friday, next try this week.
[CHRISTOPHER]
✔ Fixed some TYPO3.Eel bugs (nested operations and variables / methods) and implemented conditions (ternary operator)
☠ Was quite shocked about our review queue
➜ Will help doing reviews instead of pushing new code
Am 23.04.2012 um 11:48 schrieb Bastian Waidelich:
> TYPO3 Phoenix Scrum Meeting Notes - 23.04.2012
>
> [RENS]
>
> ✔ Did quite some reviews
> ✔ Reviewing TYPO3.Setup stuff and add all to the Phoenix demo package
> ➜ Finish review and push it
> ➜ Add redirect to Setup if no site / admin found in Development context
>
> [CHRISTIAN]
>
> ✔ reviews
> ➜ backend plugin exception debug
> ➜ T3CON12 Stuttgart
>
> [BASTIAN]
>
> ✔ Refactored FrontendNodeRoutePartHandler to use a Service class
> ➜ push (as WIP?) to make Phoenix Setup stories easier
> ➜ Global fallback for routing (no exceptions)
> ➜ Check out CodeSniffer rulesets
> ➜ Create DB-only TYPO3.Query implementation
>
> [MARKUS]
>
> ☠ was ill last week
> ☠ not much time for phoenix this week, because of project
> ➜ http://jira.phoenix.typo3.org:8080/browse/PHX-82 Inspector
> ➜ try to do some reviews
>
> [GENERAL]
>
> ➜ urgently do documentation
> ➜ implement references to extbase issues
> ➜ evaluate “issue conference” handling for FLOW3/Phoenix
> ➜ Karsten will be the first friendly ghost (March/April) and prepares guidelines along the way. Doodle on your availability here:
> http://www.doodle.com/h7mshvnwwehf24w3
>
> ~~~
>
> Legend:
> ✔ done
> ➜ next steps
> ☠ impediment
> ⓘ background info
> ♫ celebrated
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.typo3.org
> http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-team-core-v5
More information about the TYPO3-team-core-v5
mailing list