<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
  "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<link rel="home" title="HomePage" href="HomePage.html" />
<link rel="help" title="HowToUseWiki" href="HowToUseWiki.html" />
<link rel="copyright" title="GNU General Public License" href="http://www.gnu.org/copyleft/gpl.html#SEC1" />
<link rel="author" title="The PhpWiki Programming Team" href="http://phpwiki.org/ThePhpWikiProgrammingTeam" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta http-equiv="Content-Language" content="en" />
<meta name="robots" content="noindex,nofollow" />
<meta name="language" content="en" />
<meta name="document-type" content="Public" />
<meta name="document-rating" content="General" />
<meta name="generator" content="PhpWiki" />
<meta name="PHPWIKI_VERSION" content="1.3.14" />

<link rel="stylesheet" type="text/css" charset="iso-8859-1" href="phpwiki-printer.css" />
<title>PhpWiki - Update Identify</title>
</head>
<body>

<div id="header">
  
<!-- Page title -->
<h1>Update Identify</h1>
</div>
<div id="content">



<div class="wikitext"><p class="tightenable top">The <b>Update Identify</b> stage is where a package starts the maintenance process.</p>
<p class="tightenable">When the maintenace team have identified that a package has a potential update the following will occur:</p>
<ul><li class="tightenable">A sanity check will be made to make sure that the candidate update package does not immediately break the server.</li>
<li class="tightenable">A bug report is raised in the contribs.org <a href="http://bugs.contribs.org/" target="" class="namedurl"><span style="white-space: nowrap"><img src="images/http.png" alt="" class="linkicon" border="0" />Bug</span> Tracker</a> by the maintenance team.</li>
<li class="tightenable">The bug report will use the Category of <b>Updates</b> and the status is set to <b>New</b>.</li>
<li class="tightenable">The bug report must have a link to (or attached) the SRPM and RPM.</li>
<li class="tightenable">The next stage is <a href="QA%20Publish.html" class="wiki">QA Publish</a></li>
</ul>
<h4>Notes:</h4>
<ul><li class="tightenable top">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.</li>
<li class="tightenable">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.</li>
<li class="tightenable">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.</li>
</ul>
<h4>How To Participate</h4>
<p class="tightenable">The community can bring to the attention of the maintenance team packages that require an update.</p>
<p class="tightenable bottom">There are currently no guidelines on how to do this, but these will be created soon.</p>
</div>

<div id="footer">  <hr class="printer" noshade="noshade" />
<p class="editdate">Owner: &quot;wellsi&quot;  Last edited on July 27, 2005  5:45 pm by &quot;wellsi&quot;</p>
</div>

</div>
<!-- Add your Disclaimer here -->
</body>
</html>
