| 119 |
ghuddy |
1 |
<html>
|
|
|
2 |
<head>
|
|
|
3 |
<title>Release Manager - HELP</title>
|
|
|
4 |
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
|
|
|
5 |
<!-- The xtree script file -->
|
|
|
6 |
<script src="../images/xtree.js"></script>
|
|
|
7 |
|
|
|
8 |
<script language="JavaScript">
|
|
|
9 |
<!--
|
|
|
10 |
function MM_reloadPage(init) { //reloads the window if Nav4 resized
|
|
|
11 |
if (init==true) with (navigator) {if ((appName=="Netscape")&&(parseInt(appVersion)==4)) {
|
|
|
12 |
document.MM_pgW=innerWidth; document.MM_pgH=innerHeight; onresize=MM_reloadPage; }}
|
|
|
13 |
else if (innerWidth!=document.MM_pgW || innerHeight!=document.MM_pgH) location.reload();
|
|
|
14 |
}
|
|
|
15 |
MM_reloadPage(true);
|
|
|
16 |
// -->
|
|
|
17 |
</script>
|
|
|
18 |
<link rel="stylesheet" href="../images/release_manager_style.css" type="text/css">
|
|
|
19 |
<link type="text/css" rel="stylesheet" href="../images/xtree.css">
|
|
|
20 |
</head>
|
|
|
21 |
|
|
|
22 |
<body bgcolor="#FFFFFF" text="#000000" leftmargin="0" topmargin="0">
|
|
|
23 |
<table width="100%" border="0" cellspacing="0" cellpadding="0">
|
|
|
24 |
<tr>
|
|
|
25 |
<td><img src="../images/b_release_manager_small.jpg" width="300" height="32"></td>
|
|
|
26 |
</tr>
|
|
|
27 |
<tr>
|
| 5339 |
dpurdie |
28 |
<td bgcolor="#000000"><img src="../images/h_trsp_dot.gif" width="1" height="1"></td>
|
| 119 |
ghuddy |
29 |
</tr>
|
|
|
30 |
</table>
|
|
|
31 |
<div style="position: absolute; width: 200; top: 40; left: 0px; height: 470; padding: 5px; overflow: auto;">
|
|
|
32 |
<!-- js file containing the tree content, edit this file to alter the menu,
|
|
|
33 |
the menu will be inserted where this tag is located in the document -->
|
|
|
34 |
<script src="../images/tree.js"></script>
|
|
|
35 |
</div>
|
|
|
36 |
<div id="Layer1" style="position:absolute; left:200; top:33px; z-index:1; height:100%">
|
|
|
37 |
<table width="600" border="0" cellspacing="0" cellpadding="0">
|
|
|
38 |
<tr>
|
|
|
39 |
<td bgcolor="#000000" width="1"><img src="../images/h_trsp_dot.gif" width="1" height="1"></td>
|
|
|
40 |
<td width="1"><img src="../images/h_trsp_dot.gif" width="10" height="475"></td>
|
|
|
41 |
<td valign="top"> <br>
|
|
|
42 |
<table width="100%" border="0" cellspacing="0" cellpadding="4">
|
|
|
43 |
<tr>
|
|
|
44 |
<td class="help_ttl" background="../images/bg_form_lightbluedark.gif">What's New in Version 2</td>
|
|
|
45 |
</tr>
|
|
|
46 |
</table>
|
|
|
47 |
<p class="help_txt" align="center"><img src="../images/b_road.jpg" width="505" height="88"></p>
|
|
|
48 |
<p class="help_txt">Release Manager™ V2 is a huge upgrade from the initial
|
|
|
49 |
Release Manager™. Here are the few major differences.</p>
|
|
|
50 |
<p class="help_txt"><b>New User Interface</b><br>
|
|
|
51 |
This time the approach was to split the screen in sections related to
|
|
|
52 |
a release or single package (e.g. browse version trees, see history
|
|
|
53 |
of releases, etc.), and sections independent of release (e.g. "My
|
|
|
54 |
Details", "Downloads", "Help", "Admin").
|
|
|
55 |
<a href="user_interface_O001.htm" class="help_link">Click here to see
|
|
|
56 |
new User Interface</a>.<br>
|
|
|
57 |
</p>
|
|
|
58 |
<p class="help_txt"><b>No More Linking External Releases</b><br>
|
|
|
59 |
All packages from all building teams will now be working on the same
|
|
|
60 |
release, avoiding the linking of the external releases. In the previous
|
|
|
61 |
version, this was a problem as the external releases may be updated,
|
|
|
62 |
but the changes will not take the effect until the external release
|
|
|
63 |
was re-linked.</p>
|
|
|
64 |
<p class="help_txt"> <b>Views</b><br>
|
|
|
65 |
Apart from the old way of displaying all packages available in a release,
|
|
|
66 |
now you can set up your Views to view only the packages you are interested
|
|
|
67 |
in. Also, you can set up public views allowing your team to view the
|
|
|
68 |
same packages. Views are releases independent, and can be considered
|
|
|
69 |
as a filter. Using this filter, you limit what you see in a release.</p>
|
|
|
70 |
<p class="help_txt"><b>Full Dependency Tree Search</b><br>
|
|
|
71 |
With a release of approximately 90 - 100 packages, the dependency tree
|
|
|
72 |
becomes very large. Sometimes in order of 15 - 20 layers. No matter
|
|
|
73 |
how big your dependency tree or number of packages in a single release,
|
|
|
74 |
new Release Manager™ V2 will browse through it quickly giving you the
|
|
|
75 |
status of each package in a release in an instance. This means that
|
|
|
76 |
altering the package at the bottom of the tree, will result in an instant
|
|
|
77 |
status change of all packages up the dependency tree.</p>
|
|
|
78 |
<p class="help_txt"><b>7 Different States of a Package</b><br>
|
|
|
79 |
Old Release Manager™ could only tell you if package is not found, broken
|
|
|
80 |
or not. This time there are seven different states each package can
|
|
|
81 |
be in. This will give the user a detailed information of each package
|
|
|
82 |
allowing more clearer decision making during the building process. Release
|
|
|
83 |
Manager can distinguish between the package minor and major version
|
|
|
84 |
change, whether the package is in building process or released, which
|
|
|
85 |
package is ready to be built, etc.</p>
|
|
|
86 |
<p class="help_txt"><b>Making Single Package Official</b><br>
|
|
|
87 |
Release can now be done on the package level, not just on the whole
|
|
|
88 |
release. Making a single package official, you are indicating other
|
|
|
89 |
users that your package is ready for use, creating a better communication
|
|
|
90 |
between the builders.</p>
|
|
|
91 |
<p class="help_txt"><b>Access Control</b><br>
|
|
|
92 |
Browsing the releases for information still does not require login.
|
|
|
93 |
It is only until the user tries to alter the information, that the login
|
|
|
94 |
is required. This means that tasks like dependency updates, release
|
|
|
95 |
or package creation, etc. are all recorded. Again, this improves the
|
|
|
96 |
communication between the builders as the person making the change can
|
|
|
97 |
easily be contacted vie email link.</p>
|
|
|
98 |
<p class="help_txt"><b>New Release Tools</b><br>
|
|
|
99 |
Two new release tools are available. "Import" tool will allow
|
|
|
100 |
you to quickly import the contents from any release to your release.
|
|
|
101 |
"Diff" tool is used for comparing the releases, highlighting
|
|
|
102 |
any difference between them.</p>
|
|
|
103 |
<p class="help_txt"><b>New Package Tools</b><br>
|
|
|
104 |
"Contents" tab tool will give you ability to browse, view
|
|
|
105 |
and download the contents of the package, located in release area (e.g.
|
|
|
106 |
dpkg_archive) as soon as it is placed there. "Build Order"
|
|
|
107 |
tab tool is indeed very useful and on demand of our users, it is now
|
|
|
108 |
available. It will give you the exact steps in building a particular
|
|
|
109 |
package, telling you the state of each dependency.</p>
|
|
|
110 |
<p class="help_txt"><b>LinkPkgArchive and Java Support</b><br>
|
|
|
111 |
Build file used for dependency input and export now supports LinkPkgArchive
|
|
|
112 |
for windows JATS builders. Also it supports Java builders using ANT
|
|
|
113 |
build file.</p>
|
|
|
114 |
<p class="help_txt"><b>Multiple Package Manipulation</b><br>
|
|
|
115 |
Old Release Manager™ was lacking the option of multiple package manipulation
|
|
|
116 |
like, adding multiple package to a release and removing multiple packages
|
|
|
117 |
from a release.</p>
|
|
|
118 |
<p class="help_txt"><b>Quick Release Notes</b><br>
|
|
|
119 |
Comments can now be added to an individual package and to the whole
|
|
|
120 |
release. Every building team member can do this, contributing to quick
|
|
|
121 |
Release Notes generated on-the-fly.</p>
|
|
|
122 |
<p class="help_txt"> </p>
|
|
|
123 |
</td>
|
|
|
124 |
</tr>
|
|
|
125 |
</table>
|
|
|
126 |
</div>
|
|
|
127 |
</body>
|
|
|
128 |
</html>
|