Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "WTP Planning Lead"
m |
(added a few things) |
||
Line 1: | Line 1: | ||
− | The Planning Lead is responsible for the week-week, milestone-milestone planning and coordination of WTP Releases | + | The Planning Lead is responsible for the week-to-week, milestone-to-milestone planning and coordination of WTP Releases, which includes: |
− | The Planning Lead is also WTP's appointed representative to the Eclipse Foundation's (EMO) Planning Council. | + | * Conduct a weekly (or regularly occurring) status call primarily for (sub-) project leads but anyone is welcome to join in. |
+ | |||
+ | * Coordinate activities required for the yearly release train. | ||
+ | |||
+ | * Define and assume responsibility for EPP packages that includes WTP components. | ||
+ | |||
+ | The Planning Lead is also, typically, WTP's appointed representative to the Eclipse Foundation's (EMO) Planning Council. | ||
[[Category:WTP Roles| ]] | [[Category:WTP Roles| ]] |
Revision as of 23:36, 28 January 2008
The Planning Lead is responsible for the week-to-week, milestone-to-milestone planning and coordination of WTP Releases, which includes:
- Conduct a weekly (or regularly occurring) status call primarily for (sub-) project leads but anyone is welcome to join in.
- Coordinate activities required for the yearly release train.
- Define and assume responsibility for EPP packages that includes WTP components.
The Planning Lead is also, typically, WTP's appointed representative to the Eclipse Foundation's (EMO) Planning Council.