Release Manager™ V2 is a huge upgrade from the initial
Release Manager™. Here are the few major differences.
New User Interface
This time the approach was to split the screen in sections related to
a release or single package (e.g. browse version trees, see history
of releases, etc.), and sections independent of release (e.g. "My
Details", "Downloads", "Help", "Admin").
Click here to see
new User Interface.
No More Linking External Releases
All packages from all building teams will now be working on the same
release, avoiding the linking of the external releases. In the previous
version, this was a problem as the external releases may be updated,
but the changes will not take the effect until the external release
was re-linked.
Views
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 interested
in. Also, you can set up public views allowing your team to view the
same packages. Views are releases independent, and can be considered
as a filter. Using this filter, you limit what you see in a release.
Full Dependency Tree Search
With a release of approximately 90 - 100 packages, the dependency tree
becomes very large. Sometimes in order of 15 - 20 layers. No matter
how big your dependency tree or number of packages in a single release,
new Release Manager™ V2 will browse through it quickly giving you the
status of each package in a release in an instance. This means that
altering the package at the bottom of the tree, will result in an instant
status change of all packages up the dependency tree.
7 Different States of a Package
Old Release Manager™ could only tell you if package is not found, broken
or not. This time there are seven different states each package can
be in. This will give the user a detailed information of each package
allowing more clearer decision making during the building process. Release
Manager can distinguish between the package minor and major version
change, whether the package is in building process or released, which
package is ready to be built, etc.
Making Single Package Official
Release can now be done on the package level, not just on the whole
release. Making a single package official, you are indicating other
users that your package is ready for use, creating a better communication
between the builders.
Access Control
Browsing the releases for information still does not require login.
It is only until the user tries to alter the information, that the login
is required. This means that tasks like dependency updates, release
or package creation, etc. are all recorded. Again, this improves the
communication between the builders as the person making the change can
easily be contacted vie email link.
New Release Tools
Two new release tools are available. "Import" tool will allow
you to quickly import the contents from any release to your release.
"Diff" tool is used for comparing the releases, highlighting
any difference between them.
New Package Tools
"Contents" tab tool will give you ability to browse, view
and 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 now
available. It will give you the exact steps in building a particular
package, telling you the state of each dependency.
LinkPkgArchive and Java Support
Build file used for dependency input and export now supports LinkPkgArchive
for windows JATS builders. Also it supports Java builders using ANT
build file.
Multiple Package Manipulation
Old Release Manager™ was lacking the option of multiple package manipulation
like, adding multiple package to a release and removing multiple packages
from a release.
Quick Release Notes
Comments can now be added to an individual package and to the whole
release. Every building team member can do this, contributing to quick
Release Notes generated on-the-fly.
|
