Simultaneous Release Roles
Simultaneous Release Roles
Many tasks and activities must take place to produce our yearly simultaneous releases, and the Planning Council is responsible for many of those tasks and activities.
This document is to list some of those tasks and activities and group them according to "roles" that various people play. Of course, the same person may fill more than one role and sometimes a role can be shared by more than one person. The important thing about this listing of roles is to make sure that all areas are covered (i.e., assigned to someone), and if someone is no longer able to perform a role, then someone else must be found that can pickup their "job" with a clear understanding of what's expected.
This document will (likely) be be updated frequently, as we learn or think of things we have to do but that have never been written down. Also it will be updated as conditions change both within a release and across releases.
Also, please note, at this point in time, this is the first draft of this document so it may contain many errors and omissions. Greatest appreciation to you who find them. The goal of this document is not to invent something new, of what we would wish to have, but just to document what tasks we do or have done before.
- Creates a schedule for the yearly releases and maintenance releases. Projects of course can have additional releases ... but all participants are expected to deliver and test the the main yearly release, and two subsequent service releases.
- Establish, by consensual agreement, the criteria required to be part of the yearly release. For example, see Requirements For Participation.
- Determine the code name of the yearly release.
- In addition to participating in meetings, the Planning Council must also find people (from the PMCs or Strategic members they represent) to carry out the tasks of the Simultaneous Release.
- Also see Planning_Council.
Planning Council Chair
- Schedule and Lead meetings as required.
- Make sure the council operates fairly, according dev. process, and at the same time making sure that the yearly releases stay relevant to users, and adopters, and are of the expected quality, etc.
- Make sure the schedule stays on track, and if not take corrective action.
- Finds people to solve specific problems, or to fill required roles.
- Leads the planning council to consensus on the release criteria, name, etc.
- Historically there's always been an innovator in Eclipse who produces a "build system" that Projects can input to, and when run produces an update site, basically, that allows a common place for all Eclipse Users to find the functionality they are looking for, instead of having to search all over eclipse and find all the bits and pieces that they require.
- The Build Producer creates and maintains that system, not only for the yearly release but also for the subsequent simultaneous releases. So this is a fairly long term commitment.
- The Build Producer must also document the system, both in terms of what projects need to do (and not do) but also document well enough that someone could "reproduce" the build on their own hardware, especially for testing purposes.
- Helps people "get in to" the build, if there are questions or issues.
- Helps diagnosis problems if people have trouble ... at least, be the first point of contact.
- Keeps the builds running smoothly day to day.
- Makes sure that if someone breaks the build, that they attend to it relatively quickly, or else communicates with them directly.
- Runs scripts to "move" the build from one location to another, such as form build machine to staging area, and then later from staging to releases area.
- Runs scripts to do any "final" preparation work that's required, such perhaps to run pack200 on all the jars. (This is specific, pack200 task is no longer required, since current builder mirrors the pack.gz files directly, but will leave the line item for the general case).
- Creates scripts to run on a build to be sure various criteria are met, for example, that all jars are signed (and if not, open bugs against those who have not signed their jars).
- And many more tests that can be automated (e.g. check if execution environment specified, check if different versions of third party bundles used, etc).
- Run scripts to collect interesting statistics on the release ... how many bites, how many projects, how many downloads.
- Webmasters help by telling how and when to update and how to cause least impact to Eclipse mirroring system.
There are some related activities which, while related, are independent of the roles of the Planning Council and the Simultaneous Release.
This page describes EMO's role in the Simultaneous Release.
EPP produces packages of all-in-one downloads to make it easier for users in the community to get started.
While EPP of course uses the contents of the Simultaneous release, their processes, criteria, and packages are their own.
Eclipse Foundation Download pages
The Eclipse Foundation can provide download pages meant to feature the contents of the simultaneous release, sometimes even, perhaps providing web page wizards, etc, to make it easier for users to get started. Again, while this uses the content of the Simultaneous Release, their process, efforts, goals, etc., are their own and not strictly related to the Planning Council or Simultaneous Release.