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"
(added a few things) |
(added updates according to 1/29 PMC meeting) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 2: | Line 2: | ||
* Conduct a weekly (or regularly occurring) status call primarily for (sub-) project leads but anyone is welcome to join in. | * 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. | * Coordinate activities required for the yearly release train. | ||
| − | + | ** make sure projects understand "must do" items and have some means of compliance checking. | |
| + | ** monitor and coordinate cross-project mailing list | ||
| + | ** monitor and coordinate cross-project bugzilla component | ||
* Define and assume responsibility for EPP packages that includes WTP components. | * 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. | ||
| + | * Lead and ensure release reviews are ready. | ||
| + | ** Ensure IP Log is maintained and accurate. | ||
| + | ** Make sure Functions, specs, standards, etc., are properly documented | ||
| + | * Monitor dependencies and decide/recommend when to move to new versions. | ||
| − | |||
[[Category:WTP Roles| ]] | [[Category:WTP Roles| ]] | ||
Latest revision as of 00:40, 5 February 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.
- make sure projects understand "must do" items and have some means of compliance checking.
- monitor and coordinate cross-project mailing list
- monitor and coordinate cross-project bugzilla component
- 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.
- Lead and ensure release reviews are ready.
- Ensure IP Log is maintained and accurate.
- Make sure Functions, specs, standards, etc., are properly documented
- Monitor dependencies and decide/recommend when to move to new versions.