[TYPO3-team-core-v5] TYPO3 Phoenix Scrum Meeting Notes - 12.09.2012

[Karsten Dambekalns]

TYPO3 Phoenix Scrum Meeting Notes - 12.09.2012


[ROBERT]

✔ continued discussions with Marketing Team regarding TYPO3 naming scheme
✔ Reviewed change I11c34dec: [!!!][FEATURE] Custom Error Renderers
✔ Tried current state of FLOW3 Composer integration
✔ Reviewed Change I91a1f7af: [TASK] Handle errors in subprocesses properly
✔ Reviewed Change I15ed77e5: [BUGFIX] Use NotFoundView for missing actions
✔ Reviewed Change I704d806c: [FEATURE] Improve frontend routing error handling
✔ Reviewed Change Ic6e14864: [WIP][FEATURE] Improve Plugin integration
✔ Went through open reviews / questions regarding Phoenix features
✔ Checked submission requirements for packagist.org
✔ Communication regarding Phoenix UI design (login screen)
✔ Looked at impact of having merged https://review.typo3.org/#/c/14439/
➜ reviews, mostly focussing on plugin support and TypoScript
➜ preparations for Phoenix release

[KARSTEN]

✔ a bunch of FLOW3 reviews
✔ looked into cache behavior with Apc, Redis, Memcache, not køøl it seems
✔ Updated Doctrine packages to 2.2.3 (for FLOW3-1.1) and 2.3.0 (unpushed, preparation for composer)
✔ made it work with Doctrine 2.3 (unpushed, preparation for composer)
➜ get rid of our own changes to stock Doctrine (preparation for composer)
♫ did not discuss branding

[SEBASTIAN]

✔ fixed Deletion of nodes
✔ tested / fixed image handling
➜ fix in-page reloads
➜ help Marc to fix a property mapping error in TYPO3.Admin
ⓘ will be offline on Friday
ⓘ new demo site editing doesn’t seem to work very nicely, we’ll need to check this before merging

[ASKE]

✔ Reviewed the new demo package design implementation
➜ Review the user settings/user management changes
➜ Review image content element
➜ Go through review queue

[MARKUS]

☠ merging issues page tree NodeController
➜ find fix
➜ pagetree moving nodes
➜ pagetree renaming js actions
➜ reviews
♫ Phoenix Day each Friday until T3CON

[JULLE]

✔ Rebased Composer-fork to HEAD
✔ Fixed minor YAML issue
✔/➜ Handle stock packages
➜ Clean up and prepare composer code for review
ⓘ http://www.youtube.com/watch?v=vCadcBR95oU 

~~~

Legend:
✔   done
➜   next steps
☠   impediment
ⓘ   background info
♫   celebrated

Regards,
Karsten
-- 
Karsten Dambekalns
TYPO3 Core Developer, FLOW3 / Phoenix Team

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