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

[Bastian Waidelich]

TYPO3 Phoenix Scrum Meeting Notes - 02.07.2012


ⓘ 1.1. RC 1 on June 26th
	http://forge.typo3.org/projects/flow3-distribution-base/issues?query_id=192
ⓘ  https://notes.typo3.org/p/PhoenixSprintRelease
ⓘ we should schedule a real-world sprint between 3.-7. September or 
17.-21. September
   ➜ http://www.doodle.com/kug2gsdbi624qt3n
ⓘ New scrumming time? 
http://lists.typo3.org/pipermail/typo3-team-core-v5/2012-June/001080.html
ⓘ Sprint planning next friday?

[SEBASTIAN]

♫ we have a new sprint release in Phoenix
✔ Sprint Planning https://notes.typo3.org/p/PhoenixSprintJuly
✔ use surf for packaging a phoenix release 
https://review.typo3.org/#/q/topic:38500,n,z
➜ continue deployment, work on setup

[KARSTEN]

✔ sent mail to EAB regarding sprint 9 planning
➜ work on Reflection service bug

[RENS]

✔ Sprint 8 release
➜ Javascript unit / functional testing in jenkins
➜ Fix Relase Notes url on http://phoenix.typo3.org/download.html
➜ Standalone showcase of VIE with Emberjs

[BASTIAN]

☠ Functional routing tests fail for karsten, please confirm: 
https://review.typo3.org/#/c/12379/
✔ found issue with https requests and pushed fix: 
https://review.typo3.org/#/c/12515/
➜ discuss next steps for TYPO3.Setup after scrum

[CHRISTIAN]

➜ Implement content types

[RYAN]

➜ continue to check manual for errors / improvements
➜ build another example application a little more complex than the blog, 
showing more advanced FLOW3 features

[JACOB]

✔/➜ proofread and improve i18n chapter of reference
➜ think about linking to the api in the docs (need more than just 
TYPO3.FLOW3)
✔/➜ Dealing with em dashes
ⓘ TYPO3 Documentation Team Martin Bless working on ReST stuff, and 
Fabien Udriot working on api.typo3.org

[GENERAL]

➜ implement references to extbase issues
➜ evaluate “issue conference” handling for FLOW3/Phoenix


~~~

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