| Rev |
Age |
Author |
Path |
Log message |
Diff |
| 208 |
6299 d 16 h |
mhunt |
/ManagerSuite/Release_Manager/branches/Release_Manager_3.30.0000.cr_for_3.30.1000.cr/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Support for the implementation of DEVI-49829 in the buildtool. |
|
| 207 |
6299 d 16 h |
mhunt |
/ManagerSuite/Release_Manager/branches/Release_Manager_3.30.0000.cr_for_3.30.1000.cr/ |
Copied by Jats Svnlabel |
|
| 204 |
6307 d 20 h |
mhunt |
/ManagerSuite/Release_Manager/tags/Release_Manager_3.30.0000.cr/ |
DevTools/ManagerSuite/Release_Manager: Tagged by Jats Svn Import |
|
| 203 |
6307 d 20 h |
mhunt |
/ManagerSuite/Release_Manager/branches/Release_Manager_3.29.0000.cr_for_3.30.0000.cr/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Introduce new licences and package version licencing management capabilities.
NOTE: Requires backwardly compatible database patch. |
|
| 202 |
6307 d 20 h |
mhunt |
/ManagerSuite/Release_Manager/branches/Release_Manager_3.29.0000.cr_for_3.30.0000.cr/ |
Copied by Jats Svnlabel |
|
| 124 |
6339 d 23 h |
ghuddy |
/ManagerSuite/Release_Manager/tags/Release_Manager_3.29.0000.cr/ |
DevTools/ManagerSuite/Release_Manager: Tagged by Jats Svn Import |
|
| 123 |
6339 d 23 h |
ghuddy |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
1) Implement Bulk Release button operations
2) Improve Release Differencing Display to show merge candidates in destination release
3) Fix "Find a File" functionality
4) Fix "Use This Version" functionality |
|
| 121 |
6350 d 1 h |
hknight |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Work on package version extension handling, plus other assorted fixes. |
|
| 119 |
6396 d 2 h |
ghuddy |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
devi-45066 - show ccdiff and ccbc2 commands in release notes
devi-45275 - merge manager now merges into pending table, not released table
devi-48158 - daemon pause button now works under IE6
devi-48653 - fixed "used by" tab problem
devi-48681 - updated about page version and version history data |
|
| 117 |
6410 d 17 h |
vnguyen |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
DEVI-033954 Metric Collection
DEVI-046293 Release Manager restrictions on pasting Code Review URLs are too restrictive
DEVI-045770 Package Version Locking/Unlocking
Various Urgent Bug fixes |
|
| 115 |
6424 d 1 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Synchronize Release Manager production codes to version control system.
* Modified the find files section so that it can search within patches.
* Added hints on the home page so that the user can use wildcards to find files.
* Modified the build status page to enable excluded packages to be re-included.
* Fixed a bug that caused runtime errors to occur when attempting to re-version a package.
* Changed date in copyright notice.
* Fixed a bug that caused unit test results not to be uploaded when using Firefox. |
|
| 113 |
6683 d 0 h |
jtweddle |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
- Extended the Code Review section to include fields for URLs linking to external code review tools.
- Fixed a bug that caused "Fixed Issues For Last Non-Ripple Build" not to be shown in the "Reason for last non-ripple build" section. |
|
| 111 |
6718 d 0 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
* Added SBOM Priority functionality
* Added Project Issues Report
* Added support for COMING SOON build daemons
* Added support for Java 1.6
* Added ReleaseInfo Functionality
* Destroying Personal WIPs.
* Notification to the SBOM Management Team
* Sanity Check
* Release Difference - Union With Archive Manager
* Added GBE_BUILDFILTER to the Release Configuration |
|
| 109 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>Functionality Feature Between Release Manager and Deployment Manager</b>
There has been a change in the application Release Manager to make the process between Release and Deployment Manager more formal.
This would not affect Projects/Releases that are not interested in using this functionality.
Currently it has been switched on for SITS LEGACY AND SITS RELEASE 1 AND 2.
Users with the role to configure/edit a release should be able to toggle on/off for their releases.
If it's switched on, it would affect the availability of products in Deployment Manager that could be incorporated into an SBOM.
<b>Release Date:</b> 31-January-2007 |
|
| 107 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>Release Autobuildable Report Released</b>
This would help in getting the correct statistical results for DEVI-033954 (Dashboard Functionality).
<b>Archived History Faeture Added (DEVI-033926)</b>
I am concerned that Archiving a release in Release Manager means that historical information concerning packages will be lost.
That is, the archive process will remove all versions of a package that are no longer referenced by a non-archived release.
This means that the history of packages are lost - we will only be able to view the release notes of a few spot releases.
We will then not be able to see the release notes of other releases that may have contained the major changes and
are therefore losing valuable information.
From Martin Hunt 30/11/2006: Rupesh suggested viewing package history as per normal,
and viewing archived packaged history if required. MM is happy with this approach. It should keep us all happy.
I understand the intent here is that there are two History buttons on the pacakge page, "History" and "Archived History".
Once a RM release is moved to Archive Mode, the archive process will move the RM release and all packages no longer
referenced by a non-Archived release into the Archive RM database.
RM will then show all non-archived packages from the "History" button and all archived packages from the "Archived History" button.
No release notes will be deleted by this process and all will be accessible using either button.
However, all artifiacts associated with the archived packages will be archived from dpkg_archive and will no longer be accessible except from tape.
<b>Bug Fix - Detected by Steve Kinsman</b>
Importing of Package Dependencies in a Release.
<b>Bug Fix - Detected by Steve Kinsman</b>
Used By Feature
<b>Release Date:</b> 21-December-2006 |
|
| 105 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
Moving forward with the autobuild and having daemon builds, a number of GUI changes have been put in place for different levels of access for users:
Developers:
The Build Environment section under the Package Information section would have the Build Machines:
Solaris, Win32, Linux, Generic. Cannot set Generic with other options, but can set Solaris and Win32 and Linux.
NB:
Solaris could map to any number of Solaris machines, depending on the project eg Solaris 8 sparc, Solaris 10 sparc, Solaris 10 x64, Solaris 11 (coming soon)
Win32 could map to any number of Win32 machines, depending on the project eg XP Server 2003, XP Pro x64 Edition, Vista (coming soon)
ditto Linux
Generic maps to all machines, depending on the project
In addition to that, there would be a section for defining ERG's Build Standards: JATS, ANT or none (only a Leader can check none on a new package, default is JATS on a new package)
Depending on the selection of the Build Standard, the Addendums available would be:
JATS Addendum: Debug, Production, Debug and Production
ANT Addendum: Java 1.4, Java 1.5
Project Administrators
Administrators would be able to configure the build daemons and machtypes per release.
For example, we can associate release ABC with the GBE_MACHTYPES: solaris10_x86, solaris10_sparc, win32 etc.
Each of these GBE_MACHTYPE would be associated with a hostname to identify the build machine delivering that GBE_MACHTYPE.
These daemons would then be associated with a host either in MASTER or SLAVE mode. Only onde daemon can be the master.
<b>Release Date:</b> 07-December-2006 |
|
| 103 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>Creating From Other Release Completed - Pending Work Completed</b>
Users can now create a new release from a release existing in a different project.
<b>Check Release Before Closing Release - Simon Morley Request</b>
This functionality would enable the user to make sure there does not reside any package versions
in the Work In Progress or Pending before closing a release. He has the option to either move all or delete all.
<b>Select All Patches In Bulk Release - Mel Luy Request</b>
This functionality has now been added so that patches can be released in batch mode.
<b>Display Text when switching Between the Tabs - Lee Rewell Request</b>
The text to find in a given tab will now not disappear when the user switches between the tabs.
<b>Access to Access Manager from Admin Menu </b>
This has been added so that users of Access Manager can gain access into the application.
<b>Added the Escrow Report</b>
<b>Added the functionality to Ignore Dependencies from the Used By Tab - Morgan Dell Request</b>
<b>Release Date:</b> 13-October-2006 |
|
| 101 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>Obsoleting Patches</b>
You should now be able to select a patch that would make a patch obsolete
<b>Make Bulk Patch Releases</b>
This would enable you to release several patches in one go instead of having to do it one patch at a time.
The following example displays the patches that can be selected and released when "Make Release Bulk Patches" is clicked under the patches tab in Release Manager:
<b>Reports -> Advanced Search -> Find ClearQuest Bugs/Issues Location</b>
Use this section under the reports to display the package names and versions that have been associated with a given issue.
<b>Depreacation State</b>
Deprecated and deprecated dependency packages would now be the lowest priority compared to the other states that a package can exist in.
<b>Patches Automation Process</b>
An automative feature in Release Manager hsa been added for the patches section even though the existing manual process will still exist for users. I have tested with patches for Sydney but maybe other projects may be interested as well. The automative feature will do the following:
- User selects the auto checkboxes for dependency patches that he/she wants to include and clicks on the AutoFill button (the magic stuff button!!!).
- This would then invoke the script to do the following:
- Create new versions of the patches with the patch versions set to be the ones displayed in bold grey (selected versions only).
- It will then go into dpkg_archive and look under the dependency package name and version scripts folder and read the shell script that is associated with it.
- The reason for this version under the release notes will then be populated with the value set to be "Schema Patch - (PATCH_ENV1)". (PATCH_ENV1 would be the value that is assigned in the shell script).
- The package overview will be updated with the short description text.
- Build environment will not be applicable as patches do not need them. (Please do let me know if I am wrong!!!)
- The default package label will then be applied.
- There are no unit tests done on patches therefore it would mean that section would by default be "Unit Test is not done".
The automation process will therefore be saving a lot of time which currently the users spend on to make and release patches. (The manual process will still use the same old principal and click on Submit(DO NOT USE AutoFill for manual process).)
<b>Interactive Unit Tests</b>
These tests would now be carried over when a new version of a package is created but the only the "Summary" section would be cloned from the previous version. The rest of the test information needs to be filled up by the developers.
<b>Release Date:</b> 19-July-2006 |
|
| 99 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
There are changes in Release Manager and Deployment Manager so that the generation of node spec files is automated
and the business processes involved made efficient and less time-consuming. This involves the introduction of a mechanism
that would enable users to add/import processes to package versions in Release Manager and to the platforms in a given node
in a BOM (Bills Of Materials) in Deployment Manager. In general, the mechanism can be described in the following steps:
1. Insert processes/instances of processes in a given package version in Release Manager.
2. Import the processes/instances of processes to the platforms in a given node in Deployment Manager.
3. Generate the NodeSpecFiles from Deployment Manager to be used.
<b>Release Date:</b> 19-May-2006 |
|
| 97 |
6719 d 2 h |
rsolanki |
/ManagerSuite/Release_Manager/trunk/ |
DevTools/ManagerSuite/Release_Manager: Checkin by Svn Import
<b>Adding Package Interest in a given Project</b>
This functionality has now been added under the member's notifications section. Users would select the project and the package that they have interest in so that they can be notified when a new version of the package is officially released/ready for autobuild in the selected project.
<b>Editing Release Notes For a Package in Pending State</b>
Administrators, Leaders and Managers will now have the power to edit the release notes when a package has been officially released into the pending state.
<b>Clearquest Issues Filtering enabled for VTSUP and TDSE databases</b>
<b>JIRA Issues</b>
All states of Jira Issues can now be imported into JIRA table under the Release Notes section.
<b>Release Date:</b> 12-May-2006 |
|