[TYPO3-team-core-v5] Scrum Meeting Notes - 05.04.2013

[Robert Lemke]

Scrum Meeting Notes - 05.04.2013

SPRINT PLANNING

(i) permanent Scrum Hangout: http://bit.ly/FlowHangout
(i) https://notes.typo3.org/p/renaming-technical-todo
(i) Code Sprint 2 date "fixed": http://doodle.com/gcaqkzyv9ze5szm3
PING Christian soon regarding special "cooking event" if you are taking 
part in the code sprint!

[ROBERT]

? spent yesterday's afternoon and the whole day today with reviews / 
testing: the review queue is way too long for both, proceeding with Neos 
and Flow development, so we're cleaning up. 
http://robertlemke.com/en/blog/preparing-flow-2-0-beta-2.html
? continue with reviews until we can release 2.0 beta 2

[BASTIAN]

? booked train ticket to "Inspiring Flow"
? Pushed rough prototype for "Request refactoring": 
https://review.typo3.org/#/c/19556/
(i) we should refine the CGL, e.g.: "inline comments", "(relative) 
namespaces", "fast exit"
? Discuss/implement simple(?) (security) update mechanism for Neos/Flow
     (i) idea: if enabled (by default?), send current package version(s) 
to typo3.org on neos login (not more than once per X days) show 
arbitrary message if the server returns a status with a certain severity
     Maybe integrate the same functionality in Flow as command?
     Question: can we somehow automate the server side (check packages 
for important updates, ...)

[CHRISTIAN]

? also doing reviews for Flow beta release
? continue with reviews until we can release 2.0 beta 2

~~~
Legend:

?   done
?   next steps
?   impediment
(i)  background info
?   celebrated
?   work
?  snow
?  life / work balance in danger