The Update Identify stage is where a package starts the maintenance process.
When the maintenace team have identified that a package has a potential update the following will occur:
- A sanity check will be made to make sure that the candidate update package does not immediately break the server.
- A bug report is raised in the contribs.org
Bug Tracker by the maintenance team. - The bug report will use the Category of Updates and the status is set to New.
- The bug report must have a link to (or attached) the SRPM and RPM.
- The next stage is QA Publish
Notes:
- An update may be identified due to a new package from Fedora Legacy, Mitel, the Core Dev Team, or a bug-fix in the trackers.
- All Fedora Legacy updates will be taken unless they clash with e-smith customisations this is in line with the goal of trying to track the base release as closely as possible. Updates that clash will be assessed on a case-by-case basis.
- All newly created RPMs will be signed and the Fedora Legacy RPMs are signed, however RPMs from some repositories may not be signed and will be as-is.
How To Participate
The community can bring to the attention of the maintenance team packages that require an update.
There are currently no guidelines on how to do this, but these will be created soon.