Phoenix Release Management

Added by Maik Hagenbruch almost 7 years ago

Phoenix Release Management - Karsten Dambekalns

This project aims to enable reliable and continuous release management for “Phoenix” and FLOW3. This includes overall coordination of work, code reviews, making actual releases, release communication and related supporting tasks (infrastructure maintenance, coordination with other teams, …).
The workload estimation is based on the time logs of the first 8 months of 2012, during which (at least) 6 days a week were spent on code reviews, release preparation and communication.
We plan to have at least four stable releases of each Phoenix and FLOW3 throughout 2013 (one each quarter), possibly more, depending on the amount of changes that would justify additional releases.


Replies (3)

RE: Phoenix Release Management - Added by Volker Graubaum almost 7 years ago

The Phoenix budget included CodeReview, why here again? FLOW3 and Phoenix have the same estimation. Why?
Another question: you plan for each release 27 days. Is there also developing included or only "meta" work?
could someone else take the communication part (eg. Marketing/PR) ?

RE: Phoenix Release Management - Added by Karsten Dambekalns almost 7 years ago

Hi.

Volker Graubaum wrote:

The Phoenix budget included CodeReview, why here again?

The development budget contains a rather small amount and is targeted at the "during development reviews" done by everyone. This budget contains the "QA only reviews".

FLOW3 and Phoenix have the same estimation. Why?

Because it is hard to split it any more precise. In the end it influences each other and during the year the needed attention will shift back and forth between the projects.

Another question: you plan for each release 27 days. Is there also developing included or only "meta" work?

The code reviews include a lot of development by itself (tweaking changes, finished bits here and there, …).

could someone else take the communication part (eg. Marketing/PR) ?

That would be awesome.

Regards,
Karsten

RE: Phoenix Release Management - Added by Karsten Dambekalns over 6 years ago

I updated the description for the budget application as follows, based on feedback received:

This project aims to enable reliable and continuous release management for “Phoenix” and FLOW3. This includes overall coordination of work, code reviews, making actual releases, release communication and related supporting tasks (infrastructure maintenance, coordination with other teams, …).
We plan to have at least four stable releases of each Phoenix and FLOW3 throughout 2013 (one each quarter), possibly more, depending on the amount of changes that would justify additional releases.
The workload estimation is based on the time logs of the first 8 months of 2012, during which (at least) 6 days a week were spent on code reviews, release preparation and communication.
Keep in mind that the code review includes a fair bit of development, in the sense that a review often is followed by tweaks to the change at hand or other code adjustments related to it. But “real” development is planned in the related “Phoenix Development” budget.
The equal split between Phoenix and FLOW3 in this budget application is due to the fact that it is hard to estimate the split more precise. Reviews on Phoenix should be more than on FLOW3 next year, but the projects influence each other and during the year the needed attention will shift back and forth between the two.
The application lists two members, but during the year it might happen that release tasks are taken over by other members of the project team – so the current names list is something imposed by the application template and process.

The updated budget application will be sent to the TYPO3 Association as well.

Phoenix_Release_Management_Budget_Application_2013_v2.odt - v2 with updated description (28.9 KB)

    (1-3/3)