After a long period of work behind the scenes (localization, translation, speed, workspaces, content rendering, FLOW3 1.0 and so on), the TYPO3 Phoenix team today kickstarted a new sprint. The goal is a release which is suitable for truly managing the FLOW3 and conference websites through the user interface and being easy to set up by everybody interested.
Since it's been a while since the last Phoenix sprint with user-visible results, we have taken a closer a look what went well and which problems we faced the last time. One common complaint was the lack of overview during the planning and work phase of the sprint. During T3BOARD12 I set up a <link http: www.atlassian.com software>Jira / Greenhopper instance which we'll use during the next two sprints for a test run. The licenses, usually worth thousands of Euros, have been sponsored by Atlassian as part of their Open Source program. After these two sprints, we'll evaluate our experiences made and discuss the next steps with the TYPO3 teams.
But all tools aside, what really counts are the stories we are going to implement. This morning most of the Phoenix team <link https: skitch.com robertlemke t3px-team-hangout-hangouts-with-extras>gathered in a Google Hangout to go through the stories I've prepared. We found several more during the planning and discussed various details. This afternoon we'll scrub them some more and start with the actual sprint next monday. If all team members stay healthy and don't get consumed by some big customer project, we should be able to deliver the release shortly before or at the TYPO3 Developer Days.
You can follow our progress at <link http: jira.phoenix.typo3.org:8080 secure taskboard.jspa>the Task Board - just make sure to choose version "1.0 alpha 8" in the version selector …