Blame | Last modification | View Log | RSS feed
<html><head><title>Release Manager - HELP</title><meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"><!-- The xtree script file --><script src="../images/xtree.js"></script><script language="JavaScript"><!--function MM_reloadPage(init) { //reloads the window if Nav4 resizedif (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) {document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }}else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload();}MM_reloadPage(true);// --></script><link rel="stylesheet" href="../images/release_manager_style.css" type="text/css"><link type="text/css" rel="stylesheet" href="../images/xtree.css"></head><body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0"><table width="100%" border="0" cellspacing="0" cellpadding="0"><tr><td><img src="../images/b_release_manager_small.jpg" width="300" height="32"></td></tr><tr><td bgcolor="#000000"><img src="/images/h_trsp_dot.gif" width="1" height="1"></td></tr></table><div style="position: absolute; width: 200; top: 40; left: 0px; height: 470; padding: 5px; overflow: auto;"><!-- js file containing the tree content, edit this file to alter the menu,the menu will be inserted where this tag is located in the document --><script src="../images/tree.js"></script></div><div id="Layer1" style="position:absolute; left:200; top:33px; z-index:1; height:100%"><table width="600" border="0" cellspacing="0" cellpadding="0"><tr><td bgcolor="#000000" width="1"><img src="../images/h_trsp_dot.gif" width="1" height="1"></td><td width="1"><img src="../images/h_trsp_dot.gif" width="10" height="475"></td><td valign="top"> <br><table width="100%" border="0" cellspacing="0" cellpadding="4"><tr><td class="help_ttl" background="../images/bg_form_lightbluedark.gif">What's New in Version 2</td></tr></table><p class="help_txt" align="center"><img src="../images/b_road.jpg" width="505" height="88"></p><p class="help_txt">Release Manager™ V2 is a huge upgrade from the initialRelease Manager™. Here are the few major differences.</p><p class="help_txt"><b>New User Interface</b><br>This time the approach was to split the screen in sections related toa release or single package (e.g. browse version trees, see historyof releases, etc.), and sections independent of release (e.g. "MyDetails", "Downloads", "Help", "Admin").<a href="user_interface_O001.htm" class="help_link">Click here to seenew User Interface</a>.<br></p><p class="help_txt"><b>No More Linking External Releases</b><br>All packages from all building teams will now be working on the samerelease, avoiding the linking of the external releases. In the previousversion, this was a problem as the external releases may be updated,but the changes will not take the effect until the external releasewas re-linked.</p><p class="help_txt"> <b>Views</b><br>Apart from the old way of displaying all packages available in a release,now you can set up your Views to view only the packages you are interestedin. Also, you can set up public views allowing your team to view thesame packages. Views are releases independent, and can be consideredas a filter. Using this filter, you limit what you see in a release.</p><p class="help_txt"><b>Full Dependency Tree Search</b><br>With a release of approximately 90 - 100 packages, the dependency treebecomes very large. Sometimes in order of 15 - 20 layers. No matterhow big your dependency tree or number of packages in a single release,new Release Manager™ V2 will browse through it quickly giving you thestatus of each package in a release in an instance. This means thataltering the package at the bottom of the tree, will result in an instantstatus change of all packages up the dependency tree.</p><p class="help_txt"><b>7 Different States of a Package</b><br>Old Release Manager™ could only tell you if package is not found, brokenor not. This time there are seven different states each package canbe in. This will give the user a detailed information of each packageallowing more clearer decision making during the building process. ReleaseManager can distinguish between the package minor and major versionchange, whether the package is in building process or released, whichpackage is ready to be built, etc.</p><p class="help_txt"><b>Making Single Package Official</b><br>Release can now be done on the package level, not just on the wholerelease. Making a single package official, you are indicating otherusers that your package is ready for use, creating a better communicationbetween the builders.</p><p class="help_txt"><b>Access Control</b><br>Browsing the releases for information still does not require login.It is only until the user tries to alter the information, that the loginis required. This means that tasks like dependency updates, releaseor package creation, etc. are all recorded. Again, this improves thecommunication between the builders as the person making the change caneasily be contacted vie email link.</p><p class="help_txt"><b>New Release Tools</b><br>Two new release tools are available. "Import" tool will allowyou to quickly import the contents from any release to your release."Diff" tool is used for comparing the releases, highlightingany difference between them.</p><p class="help_txt"><b>New Package Tools</b><br>"Contents" tab tool will give you ability to browse, viewand download the contents of the package, located in release area (e.g.dpkg_archive) as soon as it is placed there. "Build Order"tab tool is indeed very useful and on demand of our users, it is nowavailable. It will give you the exact steps in building a particularpackage, telling you the state of each dependency.</p><p class="help_txt"><b>LinkPkgArchive and Java Support</b><br>Build file used for dependency input and export now supports LinkPkgArchivefor windows JATS builders. Also it supports Java builders using ANTbuild file.</p><p class="help_txt"><b>Multiple Package Manipulation</b><br>Old Release Manager™ was lacking the option of multiple package manipulationlike, adding multiple package to a release and removing multiple packagesfrom a release.</p><p class="help_txt"><b>Quick Release Notes</b><br>Comments can now be added to an individual package and to the wholerelease. Every building team member can do this, contributing to quickRelease Notes generated on-the-fly.</p><p class="help_txt"> </p></td></tr></table></div></body></html>