# WikiData

PageData:
==Summary of Changes

[[TOC]]
== Internal Release Manager Tests
>* Converted to use jquery and a better alert box.
>* Added test of LXR Server
== Release Notes : Unit Test
Updated the text in the dialog for adding an Autobuild UTF.

The new text is similar to that provided within WIKI page referenced by the old implementation, but provides the information directly.

== Access to dpkg_archive server
The 'releasem' password has been changed.
Definition of the password has been centralized.

== Merge Manager invocation
When Merge Manager is invoked within a Release it will now start with the Release as both the source and destination of 
the merge/diff. This simplifies the process of removing packages from the Release.

== Package Notification
Added the ability to configure package notification within the Package-Version display. This allows package notification to be configured in multiple Releases.

The existing notification configuration mechanism still exists. It is aimed at configuring multiple packages in the one Release.

== Build Logs Display
Now supports more than 2**15 entries in the build log table.

== Manually Locking and Unlocking a Path
Restored the functionality where unlocking a Patch made it writable in dpkg_archive
Add functionality where locking a Patch made it read-only in dpkg_archive

== Merge Permission
Set up a consistent policy. Now:
>* A user can merge into an Open Release in in which they have project access rights
>* A user with MergeRelease rights can merge into a Restricted Release in which they have project access rights
>* A user with MergeReleaseForCCB rights can merge into a CCB Release in which they have project access rights

== Build Status
Extended the filter to allow 'Package has no build environment' errors to be filtered out without also hiding other non-build errors.

== Package Software Licence Information
>* Creation of a New Package has a mandatory field to capture Software Licence
>* Display Software Licence information in the packages Release Notes
>* Log changes to a package's software licence
>* Add access control 
>>* to allow editing of Software Licences
>>* to all the creation of new Software Licences

PrevPageData:
@@@@@@@@@@@@@@@@17/12/2015 1:25:17 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release
== Internal Release Manager Tests
>* Converted to use jquery and a better alert box.
>* Added test of LXR Server
== Release Notes : Unit Test

Updated the text in the dialog for adding an Autobuild UTF.

The new text is similar to that provided within WIKI page referenced by the old implementation, but provides the information directly.

== Access to dpkg_archive server
The 'releasem' password has been changed.
Definition of the password has been centralized.

== Merge Manager invocation
When Merge Manager is invoked within a Release it will now start with the Release as both the source and destination of 
the merge/diff. This simplifies the process of removing packages from the Release.

== Package Notification
Added the ability to configure package notification within the Package-Version display. This allows package notification to be configured in multiple Releases.

The existing notification configuration mechanism still exists. It is aimed at configuring multiple packages in the one Release.

== Build Logs Display
Now supports more than 2**15 entries in the build log table.

== Manually Locking and Unlocking a Path
Restored the functionality where unlocking a Patch made it writable in dpkg_archive
Add functionality where locking a Patch made it read-only in dpkg_archive

== Merge Permission
Set up a consistent policy. Now:
>* A user can merge into an Open Release in in which they have project access rights
>* A user with MergeRelease rights can merge into a Restricted Release in which they have project access rights
>* A user with MergeReleaseForCCB rights can merge into a CCB Release in which they have project access rights

== Build Status
Extended the filter to allow 'Package has no build environment' errors to be filtered out without also hiding other non-build errors.

== Package Software Licence Information
>* Creation of a New Package has a mandatory field to capture Software Licence
>* Display Software Licence information in the packages Release Notes
>* Log changes to a package's software licence
>* Add access control 
>>* to allow editing of Software Licences
>>* to all the creation of new Software Licences

== FavIcon support
Add FavIcon support. With configuration via global.asa. Allows Production/Test and Dev web sites to have different Icons

== Page Footer and About Page
Made page footer and the About the same as the rest of the Manager Suite. Removed the 'year' indication from the copyright notice. Removed the 'contact us' from the footer.

== New Package Version
>* Fixed HTML formatting of the "New Package Version" line
>* Added Tool Tip to describe the 'Existing Versions" list.

== Jira Credentials
Moved the Jira and Package Archive credentials out of the source code and into the IIS controlled global.asa file.
Other credentials are already store in the global.asa file.

== Release Manager Front Page : Work In Progress display
>* Added a database index to greatly speed up the search
>* Corrected the exclusion of packages that are in Releases that are not open
>* Limited the patch-list to the release in which the patch is being implemented. Previously it list all Releases that used the package that contained the patch parent.  

== Release Manager Front Page : Package Metrics
>* Fixed the date-time format displayed. Spell out the month and be consistent.
>* Removed case. It was marked to be removed. It was in place to force metrics creation when code metrics was introduced.

== Release Notes - Package Metrics
Support the ability to show package metrics under all conditions. Previously it would not display package metrics unless the page was being displayed within a Release.

== Operations in Open and Closed Releases
Corrected a few checks for the state of a Release. Several operations had not been corrected to allow the current set of Release States.

== Deleting Recently Created Releases
The Release Deletion process has been modified to allow a user to Destroy a Release that they have created within the last 10 days.

This allows a user to create a temporary Release for experimentation. The 10 day limit prevents long term Releases from being accidently deleted.

== Creating a New Package Version
Fix issues with transferring Unit Test Information to the new version
>* Test Results are not transferred
>* Test Type and Summary are transferred - Remaining fields are set to defaults
>* Displays the 'Release Notes' tab of the new package version

== Release Notes. Previous Significant Version
The calculation of the Previous Significant Version has been corrected and sped up.

== Admin Test Page
Display Database Server date-time and Web Server date-time


@@@@@@@@@@@@@@@@17/12/2015 1:23:11 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release
== Internal Release Manager Tests
>* Converted to use jquery and a better alert box.
>* Added test of LXR Server
== Release Notes : Unit Test

Updated the text in the dialog for adding an Autobuild UTF.

The new text is similar to that provided within WIKI page referenced by the old implementation, but provides the information directly.

== Access to dpkg_archive server
The 'releasem' password has been changed.
Definition of the password has been centralized.

== Merge Manager invocation
When Merge Manager is invoked within a Release it will now start with the Release as both the source and destination of 
the merge/diff. This simplifies the process of removing packages from the Release.

== Package Notification
Added the ability to configure package notification within the Package-Version display. This allows package notification to be configured in multiple Releases.

The existing notification configuration mechanism still exists. It is aimed at configuring multiple packages in the one Release.

== Build Logs Display
Now supports more than 2**15 entries in the build log table.

== Manually Locking and Unlocking a Path
Restored the functionality where unlocking a Patch made it writable in dpkg_archive
Add functionality where locking a Patch made it read-only in dpkg_archive

== Merge Permission
Set up a consistent policy. Now:
>* A user can merge into an Open Release in in which they have project access rights
>* A user with MergeRelease rights can merge into a Restricted Release in which they have project access rights
>* A user with MergeReleaseForCCB rights can merge into a CCB Release in which they have project access rights

== Build Status
Extended the filter to allow 'Package has no build environment' errors to be filtered out without also hiding other non-build errors.

== Package Software Licence Information
>* Creation of a New Package has a mandatory field to capture Software Licence
>* Display Software Licence information in the packages Release Notes
>* Log changes to a package's software licence
>* Add access control 
>>* to allow editing of Software Licences
>>* to all the creation of new Software Licences

== FavIcon support
Add FavIcon support. With configuration via global.asa. Allows Production/Test and Dev web sites to have different Icons

== Page Footer and About Page
Made page footer and the About the same as the rest of the Manager Suite. Removed the 'year' indication from the copyright notice. Removed the 'contact us' from the footer.

== New Package Version
>* Fixed HTML formatting of the "New Package Version" line
>* Added Tool Tip to describe the 'Existing Versions" list.

== Jira Credentials
Moved the Jira and Package Archive credentials out of the source code and into the IIS controlled global.asa file.
Other credentials are already store in the global.asa file.

== Release Manager Front Page : Work In Progress display
>* Added a database index to greatly speed up the search
>* Corrected the exclusion of packages that are in Releases that are not open
>* Limited the patch-list to the release in which the patch is being implemented. Previously it list all Releases that used the package that contained the patch parent.  

== Release Manager Front Page : Package Metrics
>* Fixed the date-time format displayed. Spell out the month and be consistent.
>* Removed case. It was marked to be removed. It was in place to force metrics creation when code metrics was introduced.

== Release Notes - Package Metrics
Support the ability to show package metrics under all conditions. Previously it would not display package metrics unless the page was being displayed within a Release.

== Operations in Open and Closed Releases
Corrected a few checks for the state of a Release. Several operations had not been corrected to allow the current set of Release States.

== Deleting Recently Created Releases
The Release Deletion process has been modified to allow a user to Destroy a Release that they have created within the last 10 days.

This allows a user to create a temporary Release for experimentation. The 10 day limit prevents long term Releases from being accidently deleted.

== Creating a New Package Version
Fix issues with transferring Unit Test Information to the new version
>* Test Results are not transferred
>* Test Type and Summary are transferred - Remaining fields are set to defaults
>* Displays the 'Release Notes' tab of the new package version

== Release Notes. Previous Significant Version
The calculation of the Previous Significant Version has been corrected.

== Admin Test Page
Display Database Server date-time and Web Server date-time


@@@@@@@@@@@@@@@@16/12/2015 3:18:03 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release
== Internal Release Manager Tests
>* Converted to use jquery and a better alert box.
>* Added test of LXR Server
== Release Notes : Unit Test

Updated the text in the dialog for adding an Autobuild UTF.

The new text is similar to that provided within WIKI page referenced by the old implementation, but provides the information directly.

== Access to dpkg_archive server
The 'releasem' password has been changed.
Definition of the password has been centralized.

== Merge Manager invocation
When Merge Manager is invoked within a Release it will now start with the Release as both the source and destination of 
the merge/diff. This simplifies the process of removing packages from the Release.

== Package Notification
Added the ability to configure package notification within the Package-Version display. This allows package notification to be configured in multiple Releases.

The existing notification configuration mechanism still exists. It is aimed at configuring multiple packages in the one Release.

== Build Logs Display
Now supports more than 2**15 entries in the build log table.

== Manually Locking and Unlocking a Path
Restored the functionality where unlocking a Patch made it writable in dpkg_archive
Add functionality where locking a Patch made it read-only in dpkg_archive

== Merge Permission
Set up a consistent policy. Now:
>* A user can merge into an Open Release in in which they have project access rights
>* A user with MergeRelease rights can merge into a Restricted Release in which they have project access rights
>* A user with MergeReleaseForCCB rights can merge into a CCB Release in which they have project access rights

== Build Status
Extended the filter to allow 'Package has no build environment' errors to be filtered out without also hiding other non-build errors.

== Package Software Licence Information
>* Creation of a New Package has a mandatory field to capture Software Licence
>* Display Software Licence information in the packages Release Notes
>* Log changes to a package's software licence
>* Add access control 
>>* to allow editing of Software Licences
>>* to all the creation of new Software Licences

== FavIcon support
Add FavIcon support. With configuration via global.asa. Allows Production/Test and Dev web sites to have different Icons

== Page Footer and About Page
Made page footer and the About the same as the rest of the Manager Suite. Removed the 'year' indication from the copyright notice. Removed the 'contact us' from the footer.

== New Package Version
>* Fixed HTML formatting of the "New Package Version" line
>* Added Tool Tip to describe the 'Existing Versions" list.

== Jira Credentials
Moved the Jira and Package Archive credentials out of the source code and into the IIS controlled global.asa file.
Other credentials are already store in the global.asa file.

== Release Manager Front Page : Work In Progress display
>* Added a database index to greatly speed up the search
>* Corrected the exclusion of packages that are in Releases that are not open
>* Limited the patch-list to the release in which the patch is being implemented. Previously it list all Releases that used the package that contained the patch parent.  

== Release Manager Front Page : Package Metrics
>* Fixed the date-time format displayed. Spell out the month and be consistent.
>* Removed case. It was marked to be removed. It was in place to force metrics creation when code metrics was introduced.

== Release Notes - Package Metrics
Support the ability to show package metrics under all conditions. Previously it would not display package metrics unless the page was being displayed within a Release.

== Operations in Open and Closed Releases
Corrected a few checks for the state of a Release. Several operations had not been corrected to allow the current set of Release States.

== Deleting Recently Created Releases
The Release Deletion process has been modified to allow a user to Destroy a Release that they have created within the last 10 days.

This allows a user to create a temporary Release for experimentation. The 10 day limit prevents long term Releases from being accidently deleted.

== Creating a New Package Version
Fix issues with transferring Unit Test Information to the new version
>* Test Results are not transferred
>* Test Type and Summary are transferred - Remaining fields are set to defaults
>* Displays the 'Release Notes' tab of the new package version

== Release Notes. Previous Significant Version
The calculation of the Previous Significant Version has been corrected.


@@@@@@@@@@@@@@@@12/03/2015 9:03:25 AM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release
== Internal Release Manager Tests
>* Convert


PageData:
==Summary of Changes

[[TOC]]
Changes introduced since the last release
== Internal Release Manager Tests
>* Converted to use jquery and a better alert box.
>* Added test of LXR Server
== Release Notes : Unit Test

Updated the text in the dialog for adding an Autobuild UTF.

The new text is similar to that provided within WIKI page referenced by the old implementation, but provides the information directly.

== Access to dpkg_archive server
The 'releasem' password has been changed.
Definition of the password has been centralized.

== Merge Manager invocation
When Merge Manager is invoked within a Release it will now start with the Release as both the source and destination of 
the merge/diff. This simplifies the process of removing packages from the Release.

== Package Notification
Added the ability to configure package notification within the Package-Version display. This allows package notification to be configured in multiple Releases.

The existing notification configuration mechanism still exists. It is aimed at configuring multiple packages in the one Release.

== Build Logs Display
Now supports more than 2**15 entries in the build log table.

== Manually Locking and Unlocking a Path
Restored the functionality where unlocking a Patch made it writable in dpkg_archive
Add functionality where locking a Patch made it read-only in dpkg_archive

== Merge Permission
Set up a consistent policy. Now:
>* A user can merge into an Open Release in in which they have project access rights
>* A user with MergeRelease rights can merge into a Restricted Release in which they have project access rights
>* A user with MergeReleaseForCCB rights can merge into a CCB Release in which they have project access rights

== Build Status
Extended the filter to allow 'Package has no build environment' errors to be filtered out without also hiding other non-build errors.

== Package Software Licence Information
>* Creation of a New Package has a mandatory field to capture Software Licence
>* Display Software Licence information in the packages Release Notes
>* Log changes to a package's software licence
>* Add access control 
>>* to allow editing of Software Licences
>>* to all the creation of new Software Licences

== FavIcon support
Add FavIcon support. With configuration via global.asa. Allows Production/Test and Dev web sites to have different Icons

== Page Footer and About Page
Made page footer and the About the same as the rest of the Manager Suite. Removed the 'year' indication from the copyright notice. Removed the 'contact us' from the footer.

== New Package Version
>* Fixed HTML formatting of the "New Package Version" line
>* Added Tool Tip to describe the 'Existing Versions" list.

== Jira Credentials
Moved the Jira and Package Archive credentials out of the source code and into the IIS controlled global.asa file.
Other credentials are already store in the global.asa file.

== Release Manager Front Page : Work In Progress display
>* Added a database index to greatly speed up the search
>* Corrected the exclusion of packages that are in Releases that are not open
>* Limited the patch-list to the release in which the patch is being implemented. Previously it list all Releases that used the package that contained the patch parent.  

== Release Manager Front Page : Package Metrics
>* Fixed the date-time format displayed. Spell out the month and be consistent.
>* Removed case. It was marked to be removed. It was in place to force metrics creation when code metrics was introduced.

== Release Notes - Package Metrics
Support the ability to show package metrics under all conditions. Previously it would not display package metrics unless the page was being displayed within a Release.

== Operations in Open and Closed Releases
Corrected a few checks for the state of a Release. Several operations had not been corrected to allow the current set of Release States.

== Deleting Recently Created Releases
The Release Deletion process has been modified to allow a user to Destroy a Release that they have created within the last 10 days.

This allows a user to create a temporary Release for experimentation. The 10 day limit prevents long term Releases from being accidently deleted.

== Creating a New Package Version
Fix issues with transferring Unit Test Information to the new version
>* Test Results are not transferred
>* Test Type and Summary are transferred - Remaining fields are set to defaults
>* Displays the 'Release Notes' tab of the new package version

== Release Notes. Previous Significant Version
The calculation of the Previous Significant Version has been corrected and sped up.

== Admin Test Page
Display Database Server date-time and Web Server date-time


PageData:
==Summary of Changes
[[TOC]]
Changes introduced since the last release


== Package Version Dependency Page
Changes to the Package Dependency Changes section
 * Added widget to export the Dependency Changes as CSV
 * Added selector to simplify comparison with the version from another Release.
These two changes can be used to generate a simple diff report between a package between two releases.

== Package Version Details
>* Enhanced 'Copy to Clipboard' menu to support
>>* PVID
>>* RTAG_ID
>>* URL to the latest version of the package in the release. This is intended to allow a bookmark to the latest version of the package in the current release.

== Closing, Preserving and Archive a Release
Improved the treatment of WIP and Pending packages when Closing, Preserving and Archive a Release.

 * Error handling has been improved to remove an oracle error under some instances
 * If a package has been 'locked' then it will not be deleted, but simply removed from the Pending Area
When performs from the 'Release List' display, Added an 'Are you sure' dialog to prevent inadvertent closure of a release.

== Daemon Instructions and Test Builds
Fixed up the dialog.
 * Time changes are not forgotten
 * Dialog has less noise
 * No defaults for Projects, Releases and Packages, when creating a new instruction.

== Package Licences in a Release
 * Added facility to sort by licence.
 * Added hyperlinks to show all versions of the package as well as the package-version in the current release.
 * Improved page rendering.
 * Added help tips.

== Release Notes
 * Enable editing of Ripple Properties if the user is allowed to Peg a package
== Release Stats
 * Extended the save options to allow the data to be: downloaded, shown in a new window or copied to the clipboard.
== Rejecting a package that has failed to build
This will now increment the, internal, release sequence number so as to force the build daemons to re-plan the release.

If the package is a WIP then the process of rejecting the package will cause the previous version to become the effective version and packages that prevented from building because of the failed WIP may be considered for building if they have other dependencies that have also changed.
== View By Version Page
 * Added the package license
 * Improved sort by package version

== Files and Folders display
 * Fixed issue when comparing the files and folders of two versions. Forced file separator to be and '/'

== Package Replication Display and Configuration
Support has been added to allow the Configuration and Display of Projects and Releases that are being replicated to remote development sites.

The underling BLAT transfer needs to be configured on the package archive server, but the Projects and Releases to be transferred can be configured via Release Manager.

Release Manager allows:
 * Addition and Removal of Replica servers
 * Editing some properties of the Replica server
 * Adding and Removing Projects to a specific replica
 * Adding and Removing Releases to a specific replica
 * Display of the replication configuration
Servers can be configured to:
 * Transfer the entire contents of the master server
 * Transfer all packages being created
 * To be disabled
There are three menu items to support these operations:
 * Admin | Package Replication
 * Build | Package Replication
 * Release | Release Replication
The Project Summary Page also has a 'Replication' button to allow configuration of Project replication.

== Package Version Use Information
 * Improved the speed of display of the "Used By" information by removing a database query that was being run for every row rendered.

== Internal Changes
 * Greater use of CCS over images to display many of the tables throughout
 * Change the 'tab' display to 100% CSS

== Merge Manager
 * Added 'Bulk Operations' to simplify large merges

== Newer Version Report
The Newer Versions Report is available on the 'Release' submenu. The report details package-versions in the Release where a newer version has been created elsewhere.

The intent of the report is to allow developers to determine if a newer version of a package exists and if it should be included into the Release.
The page:
>* Shows newer versions of packages in the current Release
>* By default, the latest version will be shown, but a control allow other versions to be displayed
>* The display can be filtered by age of the new version.
>* The user can
>>* Inspect the history of a package version
>>* Examine the use of a package-version in other Projects and Releases
>>* Merge a package version into the Release. It will be added to the 'Pending' tab. The merge will need to be completed later.
>>* Remove a package that is marked to be merged
>>* Sort the display on some columns. The sort attempts to keeps packages together where possible.

== New Version Warning
The user is given a warning message when creating a 'new version' of a package for which a newer version exists.

== Scheduled builds
Support has been added to allow an approved package to be built at a future time. This feature is intended to allow a developer to 
release a package that will have major build effects at a time when the build system is not in use.

The user can specify the build time upto 3 days into the future.

== User Personal Views
Fixed a very old bug that prevents users from adding/removing Base Views to there personal collection.
Now a user can create a set of Person Views that consist of:
>* Private Views - A view created and maintained by a user. Visible to only that user
>* Public views - A view created and maintained by a user. Visible to all users
>* Base Views - A base Package View. Global views that are always available
>* SDK Views - A view for an SDK. A global view that is always available

== Restricted and CCB mode
Allow a New Version of a Package to be created when a Release is in Restricted or CCB mode so that developers can still progress code development.

== Page Header
The Page Header has been modified to
>* Display a warning if the build daemons have been disabled
>* Indicate if the user has been logged out
>* The time the page was last updated - in Perth (AWST) time
The information is dynamic and will be updated every 30 seconds.

== Build Plan
>* Fixed the calculation of the estimated Build Completion Time
>* Added support to show a second, follow-on, build plan.

Added control over the build plan
>* Drop the current plan. The current 'plan' will be dropped and the system will include all WIPS and Ripple requests into a new plan.
>* Disable advanced planning. The system will revert to the original plan algorithm and always include all WIPS, Ripples and Ripple Requests.
>* Cautious planning. The system will build the current set of ripples, unless adding in all the WIPs and Ripple Requests will not extend then build time by more than 20%, in which case it will build the complete plan.
>* Aggressive planning. The system will build the current set of ripples, unless adding in all the WIPs and Ripple Requests will not extend then build time by more than 100%, in which case it will build the complete plan.

== Build Package
The Build Package request has been changed to:
>* Display the expected build duration of the package
>* Display the expected build duration of the ripple caused by building the package
>>* The duration attempts to factor in presence of packages marked as 'Pegged', 'Advisory Ripple' and those imported from an SDK.
>* Display a warning, and set the default mode to 'schedule' if the expected ripple duration is greater that 2 hours.

== Files and Folders Tab
Added the ability to hide and show files that are 'unchanged', 'added', 'removed' or 'modified'

== Access to Build Logs
The 'Unit Test' tab and the 'Build Logs' pages have been enhanced with an icon that will link to a popup that will provided access to the Build Logs for each build.

The icon will be disabled if the logs are known to be unavailable, but the presence of the icon does not ensure that logs are available.

== Configuring build filters
Many changes have occurred. This include:
>* New admin page to define 'Build Platforms'
>* Extension to 'Build Machine' configuration to allow configuration of the 'Build Platforms' supported on each 'Build Machine'
>* Extension to the 'Release Build Configuration' to show the 'Build Platforms' available on the selected Build Machine.
>>* The Multi Column selector of the Build Machine has been rewritten to remove the need for a pre-formatted font
>>* Interaction between the 'Build Machine', 'Build Filter' and 'Available Platforms' to highlight the platforms that are available.
>>* Automatic handling of the 'None' pseudo platform

== Improved handling of pop-up windows when the user has been logged out.
Previously the pop-up would contain a 'log on' prompt and the operation may not proceed correctly.
The change will detect that the user has been logged and provide a message explaining that the operation cannot be performed.

== Improved 'Progress' indications
Replaced 'In Progress ...' text with a spinning Vix icon. In the process a number of mismatched 'progress' controls' were fixed.

== Improved file search
Improved two file search mechanisms:
>* The global file search.
>* The search for files within a Release.
The hard limit of 100 files displayed has been replaced with a scrolling table that can show all matches.
The table has been enhanced to allow additional searching on the returned fields.

== Extended the period of time that a user can delete their own Release
Extended from 10 days to 20 days.

== Support for future CI/CD - S3 Bucket Sync (Version1 since removed)
Added support for some parts of packages to be synced into an AWS S3 Bucket.
The components involved in the support are:
>* A Release Property to enable S3 Sync
>>* The sync target is a fix, and well known, bucket with the Releases rtag_id as a prefix within the bucket
>>* When a Release is cloned the S3 Sync property is disabled
>* Each package in a Release can be marked to enable S3 Sync
>>* The package must be correctly formatted. Only the 'pkg/S3TRANSFER' section of a package will be processed.
>>* This property is a function of the Release and not of the package version
>>* It can only be set on a Released package
>>* New versions of the package, in a Release, will inherit the property.
The Release Summary page will show the Releases that have S3Sync support enabled

Within a Release the menu will show that 'S3 Sync' is available.

A Menu option is available to view and alter the the S3Sync flag on all packages in a Release.
Through this page a user can:
>* Display all packages in a Release with an indication of:
>>* Packages that have the S3Sync flag enabled
>>* Packages that appear to have S3TRANSFER data present
>* Alter the S3Sync flag on a package
>* Apply various filters:
>>* Filter packages by name/version/project suffix
>>* Display only those package that have S3Sync enabled
>>* Display  only those package that appear to have S3TRANSFER data available

== Support for future CI/CD - S3 Manifest Generation
Added support for a Manifest to be generated into an S3 bucket.
The components involved in the support are:
>* A Release Property to Manifest Generation
>>* The sync target is a fix, and well known, bucket with the Releases rtag_id as a prefix within the bucket
>>* When a Release is cloned the Manifest Generation property is disabled
>* Each package in a Release can be marked to be in the Manifest
>>* This property is a function of the Release and not of the package version
>>* It can only be set on a Released package
>>* New versions of the package, in a Release, will inherit the property.
The Release Summary page will show the Releases that have S3 Manifest Generation support enabled

Within a Release the menu will show that 'S3 Manifest' is available.

A Menu option is available to view and alter the the 'In Manifest' flag on all packages in a Release.
Through this page a user can:
>* Display all packages in a Release with an indication of packages that have the InManifest flag enabled
>* Alter the InManifest flag on a package
>* Apply various filters:
>>* Filter packages by name/version/project suffix
>>* Display only those package that have InManifest enabled

When 'S3 Manifest Generation' generation for a Release is enabled the build system will automatically create a snapshot of the release when all packages
that can be built have been built without error.

== Added GIT Support
>* User can select GIT as the version control system for the package-version
>>* Source path is validated as:
>>>* SYMNAME/path/Repo, where SYNMAME is a symbolic name of Repo known to the build system
>>* Tag is validated. Allowed forma are:
>>>* A 40 character SHA1
>>>* A tag ending in WIP. The tag must consist of A-Z,a-z, 0-9,_,- and . - no comma
>>>* A tag starting with a lowercase 'v' - USe by the build system ti indicate a version number. Same rules as WIP.
>* When a package is made pending or released a sanity test will be performed to ensure that a package that has been migrated to GIT is not being released or rippled under either ClearCase or Subversion.

== Release Snapshots - initial support
A new class of Release has been created called a 'snapshot'. These have the following properties:
>* They cannot be re-opened, although a clone can be taken
>* That can have the same name as an existing 'snapshot', but not a Release
At the moment a snapshot can only be manually created via the 'Releases || Snapshot Releases'

There is a 'Releases || Release Snapshots' menu item. This will display a list of the Releases Snapshots. It is possible to:

>* Delete the Snapshot
>* Compare it against another snapshot
>* Compare/Merge with the parent release
>* Edit the snapshot properties
>* Open the snapshot

== External Package Reference
A field has been added to the Release Notes package to contain a reference to 3rd party and licenced packages. The data in the field may be used by external tools to detect new versions in these packages.

The field will only be shown if the package is a COTS or a TOOLS package or if the package has a specified licence.

PrevPageData:
@@@@@@@@@@@@@@@@1/07/2020 3:59:26 PM : 10.240.2.68@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release


== Package Version Dependency Page
Changes to the Package Dependency Changes section
 * Added widget to export the Dependency Changes as CSV
 * Added selector to simplify comparison with the version from another Release.
These two changes can be used to generate a simple diff report between a package between two releases.

== Package Version Details
>* Enhanced 'Copy to Clipboard' menu to support
>>* PVID
>>* RTAG_ID
>>* URL to the latest version of the package in the release. This is intended to allow a bookmark to the latest version of the package in the current release.

== Closing, Preserving and Archive a Release
Improved the treatment of WIP and Pending packages when Closing, Preserving and Archive a Release.

 * Error handling has been improved to remove an oracle error under some instances
 * If a package has been 'locked' then it will not be deleted, but simply removed from the Pending Area
When performs from the 'Release List' display, Added an 'Are you sure' dialog to prevent inadvertent closure of a release.

== Daemon Instructions and Test Builds
Fixed up the dialog.
 * Time changes are not forgotten
 * Dialog has less noise
 * No defaults for Projects, Releases and Packages, when creating a new instruction.

== Package Licences in a Release
 * Added facility to sort by licence.
 * Added hyperlinks to show all versions of the package as well as the package-version in the current release.
 * Improved page rendering.
 * Added help tips.

== Release Notes
 * Enable editing of Ripple Properties if the user is allowed to Peg a package
== Release Stats
 * Extended the save options to allow the data to be: downloaded, shown in a new window or copied to the clipboard.
== Rejecting a package that has failed to build
This will now increment the, internal, release sequence number so as to force the build daemons to re-plan the release.

If the package is a WIP then the process of rejecting the package will cause the previous version to become the effective version and packages that prevented from building because of the failed WIP may be considered for building if they have other dependencies that have also changed.
== View By Version Page
 * Added the package license
 * Improved sort by package version

== Files and Folders display
 * Fixed issue when comparing the files and folders of two versions. Forced file separator to be and '/'

== Package Replication Display and Configuration
Support has been added to allow the Configuration and Display of Projects and Releases that are being replicated to remote development sites.

The underling BLAT transfer needs to be configured on the package archive server, but the Projects and Releases to be transferred can be configured via Release Manager.

Release Manager allows:
 * Addition and Removal of Replica servers
 * Editing some properties of the Replica server
 * Adding and Removing Projects to a specific replica
 * Adding and Removing Releases to a specific replica
 * Display of the replication configuration
Servers can be configured to:
 * Transfer the entire contents of the master server
 * Transfer all packages being created
 * To be disabled
There are three menu items to support these operations:
 * Admin | Package Replication
 * Build | Package Replication
 * Release | Release Replication
The Project Summary Page also has a 'Replication' button to allow configuration of Project replication.

== Package Version Use Information
 * Improved the speed of display of the "Used By" information by removing a database query that was being run for every row rendered.

== Internal Changes
 * Greater use of CCS over images to display many of the tables throughout
 * Change the 'tab' display to 100% CSS

== Merge Manager
 * Added 'Bulk Operations' to simplify large merges

== Newer Version Report
The Newer Versions Report is available on the 'Release' submenu. The report details package-versions in the Release where a newer version has been created elsewhere.

The intent of the report is to allow developers to determine if a newer version of a package exists and if it should be included into the Release.
The page:
>* Shows newer versions of packages in the current Release
>* By default, the latest version will be shown, but a control allow other versions to be displayed
>* The display can be filtered by age of the new version.
>* The user can
>>* Inspect the history of a package version
>>* Examine the use of a package-version in other Projects and Releases
>>* Merge a package version into the Release. It will be added to the 'Pending' tab. The merge will need to be completed later.
>>* Remove a package that is marked to be merged
>>* Sort the display on some columns. The sort attempts to keeps packages together where possible.

== New Version Warning
The user is given a warning message when creating a 'new version' of a package for which a newer version exists.

== Scheduled builds
Support has been added to allow an approved package to be built at a future time. This feature is intended to allow a developer to 
release a package that will have major build effects at a time when the build system is not in use.

The user can specify the build time upto 3 days into the future.

== User Personal Views
Fixed a very old bug that prevents users from adding/removing Base Views to there personal collection.
Now a user can create a set of Person Views that consist of:
>* Private Views - A view created and maintained by a user. Visible to only that user
>* Public views - A view created and maintained by a user. Visible to all users
>* Base Views - A base Package View. Global views that are always available
>* SDK Views - A view for an SDK. A global view that is always available

== Restricted and CCB mode
Allow a New Version of a Package to be created when a Release is in Restricted or CCB mode so that developers can still progress code development.

== Page Header
The Page Header has been modified to
>* Display a warning if the build daemons have been disabled
>* Indicate if the user has been logged out
>* The time the page was last updated - in Perth (AWST) time
The information is dynamic and will be updated every 30 seconds.

== Build Plan
>* Fixed the calculation of the estimated Build Completion Time
>* Added support to show a second, follow-on, build plan.

Added control over the build plan
>* Drop the current plan. The current 'plan' will be dropped and the system will include all WIPS and Ripple requests into a new plan.
>* Disable advanced planning. The system will revert to the original plan algorithm and always include all WIPS, Ripples and Ripple Requests.
>* Cautious planning. The system will build the current set of ripples, unless adding in all the WIPs and Ripple Requests will not extend then build time by more than 20%, in which case it will build the complete plan.
>* Aggressive planning. The system will build the current set of ripples, unless adding in all the WIPs and Ripple Requests will not extend then build time by more than 100%, in which case it will build the complete plan.

== Build Package
The Build Package request has been changed to:
>* Display the expected build duration of the package
>* Display the expected build duration of the ripple caused by building the package
>>* The duration attempts to factor in presence of packages marked as 'Pegged', 'Advisory Ripple' and those imported from an SDK.
>* Display a warning, and set the default mode to 'schedule' if the expected ripple duration is greater that 2 hours.

== Files and Folders Tab
Added the ability to hide and show files that are 'unchanged', 'added', 'removed' or 'modified'

== Access to Build Logs
The 'Unit Test' tab and the 'Build Logs' pages have been enhanced with an icon that will link to a popup that will provided access to the Build Logs for each build.

The icon will be disabled if the logs are known to be unavailable, but the presence of the icon does not ensure that logs are available.

== Configuring build filters
Many changes have occurred. This include:
>* New admin page to define 'Build Platforms'
>* Extension to 'Build Machine' configuration to allow configuration of the 'Build Platforms' supported on each 'Build Machine'
>* Extension to the 'Release Build Configuration' to show the 'Build Platforms' available on the selected Build Machine.
>>* The Multi Column selector of the Build Machine has been rewritten to remove the need for a pre-formatted font
>>* Interaction between the 'Build Machine', 'Build Filter' and 'Available Platforms' to highlight the platforms that are available.
>>* Automatic handling of the 'None' pseudo platform

== Improved handling of pop-up windows when the user has been logged out.
Previously the pop-up would contain a 'log on' prompt and the operation may not proceed correctly.
The change will detect that the user has been logged and provide a message explaining that the operation cannot be performed.

== Improved 'Progress' indications
Replaced 'In Progress ...' text with a spinning Vix icon. In the process a number of mismatched 'progress' controls' were fixed.

== Improved file search
Improved two file search mechanisms:
>* The global file search.
>* The search for files within a Release.
The hard limit of 100 files displayed has been replaced with a scrolling table that can show all matches.
The table has been enhanced to allow additional searching on the returned fields.

== Extended the period of time that a user can delete their own Release
Extended from 10 days to 20 days.

== Support for future CI/CD - S3 Bucket Sync (Version1 since removed)
Added support for some parts of packages to be synced into an AWS S3 Bucket.
The components involved in the support are:
>* A Release Property to enable S3 Sync
>>* The sync target is a fix, and well known, bucket with the Releases rtag_id as a prefix within the bucket
>>* When a Release is cloned the S3 Sync property is disabled
>* Each package in a Release can be marked to enable S3 Sync
>>* The package must be correctly formatted. Only the 'pkg/S3TRANSFER' section of a package will be processed.
>>* This property is a function of the Release and not of the package version
>>* It can only be set on a Released package
>>* New versions of the package, in a Release, will inherit the property.
The Release Summary page will show the Releases that have S3Sync support enabled

Within a Release the menu will show that 'S3 Sync' is available.

A Menu option is available to view and alter the the S3Sync flag on all packages in a Release.
Through this page a user can:
>* Display all packages in a Release with an indication of:
>>* Packages that have the S3Sync flag enabled
>>* Packages that appear to have S3TRANSFER data present
>* Alter the S3Sync flag on a package
>* Apply various filters:
>>* Filter packages by name/version/project suffix
>>* Display only those package that have S3Sync enabled
>>* Display  only those package that appear to have S3TRANSFER data available

== Support for future CI/CD - S3 Manifest Generation
Added support for a Manifest to be generated into an S3 bucket.
The components involved in the support are:
>* A Release Property to Manifest Generation
>>* The sync target is a fix, and well known, bucket with the Releases rtag_id as a prefix within the bucket
>>* When a Release is cloned the Manifest Generation property is disabled
>* Each package in a Release can be marked to be in the Manifest
>>* This property is a function of the Release and not of the package version
>>* It can only be set on a Released package
>>* New versions of the package, in a Release, will inherit the property.
The Release Summary page will show the Releases that have S3 Manifest Generation support enabled

Within a Release the menu will show that 'S3 Manifest' is available.

A Menu option is available to view and alter the the 'In Manifest' flag on all packages in a Release.
Through this page a user can:
>* Display all packages in a Release with an indication of packages that have the InManifest flag enabled
>* Alter the InManifest flag on a package
>* Apply various filters:
>>* Filter packages by name/version/project suffix
>>* Display only those package that have InManifest enabled

When 'S3 Manifest Generation' generation for a Release is enabled the build system will automatically create a snapshot of the release when all packages
that can be built have been built without error.

== Added GIT Support
>* User can select GIT as the version control system for the package-version
>>* Source path is validated as:
>>>* SYMNAME/path/Repo, where SYNMAME is a symbolic name of Repo known to the build system
>>* Tag is validated. Allowed forma are:
>>>* A 40 character SHA1
>>>* A tag ending in WIP. The tag must consist of A-Z,a-z, 0-9,_,- and . - no comma
>>>* A tag starting with a lowercase 'v' - USe by the build system ti indicate a version number. Same rules as WIP.
>* When a package is made pending or released a sanity test will be performed to ensure that a package that has been migrated to GIT is not being released or rippled under either ClearCase or Subversion.

== Release Snapshots - initial support
A new class of Release has been created called a 'snapshot'. These have the following properties:
>* They cannot be re-opened, although a clone can be taken
>* That can have the same name as an existing 'snapshot', but not a Release
At the moment a snapshot can only be manually created via the 'Releases || Snapshot Releases'

== External Package Reference
A field has been added to the Release Notes package to contain a reference to 3rd party and licenced packages. The data in the field may be used by external tools to detect new versions in these packages.

The field will only be shown if the package is a COTS or a TOOLS package or if the package has a specified licence.



@@@@@@@@@@@@@@@@16/12/2019 3:07:49 PM : 10.240.2.68@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release


== Package Version Dependency Page
Changes to the Package Dependency Changes section
 * Added widget to export the Dependency Changes as CSV
 * Added selector to simplify comparison with the version from another Release.
These two changes can be used to generate a simple diff report between a package between two releases.

== Package Version Details
>* Enhanced 'Copy to Clipboard' menu to support
>>* PVID
>>* RTAG_ID
>>* URL to the latest version of the package in the release. This is intende


PageData:
==Summary of Changes
[[TOC]]

== Cloning a Release
Options have been added to allow the new Release to be created in either the:

>* Open State (Default)
>* Closed State
>* Archived State - suitable for creating a snapshot of a Release

== Package Release Notes
>* Added links to the 'Previous Version' and 'Previous Significant Version' fields to allow navigation to the previous versions. {br}The versions are shown in the context of the currently displayed release. {br}A package icon will be displayed t show that displayed version is not a member of the current Release.

>* Package Metrics will not be displayed if there are no metrics. {br}Packages that have not been built will not have package metrics.

>* The Deployable field in Release Notes matches the same field in the Editor [JATS-359]. The display in the Release Notes was incorrect.

== Locating Unused Packages within a Release
A new menu item in the 'Release' menu will show all packages within the Release that are not being used.

This feature has been available as an 'Advanced Report'. Now it is readily available within the Release Display.

imagecenter:$image$/UnusedPackages.png

== Removed JANTS support
It is no longer possible to import or export package dependencies in JANTS style. It has not been in use for many years.

== Display Package Versions - Handle deleted users
The underlying SQL to the Display by Package Version page has been corrected to allow for users that cannot be found in the data base.

== Calculation of Previous Significant Version
Corrected for the edge case of there being only one significant version.

== Build Daemon Configuration
The configuration dialog has been enhanced to prevent multiple instances of a build machine being configured in a single Release. [JATS-52].

The drop-down list of machines will display those machines that are currently in use as 'disabled'. This will prevent the user from selecting them.

== Advanced Package Search
Addressed [JATS-7] Advanced package search does not find packages

Improved the SQL such that packages will be found.

== Removed many Pop-Up Windows
Altered many of the button operations to use a modal-dialog rather than a popup window.

Popup Windows are considered to be a bad practice and confusing to the user. The modal dialogs appear in the center of the Release Manager window and not on a different screen or under another window. 

== Move Package to a different view
The button is only provided to the user if the package has been released, otherwise the change will not be applicable.

== Action Buttons
Enabled hover text on disabled buttons.

== Editing Package Information
The editing process has been modified such that partial information can be entered [JATS-24].

It will not be possible to release the package before all the information has been entered, but the information required does not need to be entered at the same time.

== New Member and Lost Password information
This has been updated to provide useful information.

PrevPageData:
@@@@@@@@@@@@@@@@3/03/2016 3:30:58 PM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release

== Cloning a Release
Options have been added to allow the new Release to be created in either the:

>* Open State (Default)
>* Closed State
>* Archived State - suitable for creating a snapshot of a Release

== Package Release Notes
>* Added links to the 'Previous Version' and 'Previous Significant Version' fields to allow navigation to the previous versions. {br}The versions are shown in the context of the currently displayed release. {br}A package icon will be displayed t show that displayed version is not a member of the current Release.

>* Package Metrics will not be displayed if there are no metrics. {br}Packages that have not been built will not have package metrics.

>* The Deployable field in Release Notes matches the same field in the Editor [JATS-359]. The display in the Release Notes was incorrect.

== Locating Unused Packages within a Release
A new menu item in the 'Release' menu will show all packages within the Release that are not being used.

This feature has been available as an 'Advanced Report'. Now it is readily available within the Release Display.

imagecenter:$image$/UnusedPackages.png

== Removed JANTS support
It is no longer possible to import or export package dependencies in JANTS style. It has not been in use for many years.

== Display Package Versions - Handle deleted users
The underlying SQL to the Display by Package Version page has been corrected to allow for users that cannot be found in the data base.

== Calculation of Previous Significant Version
Corrected for the edge case of there being only one significant version.

== Build Daemon Configuration
The configuration dialog has been enhanced to prevent multiple instances of a build machine being configured in a single Release. [JATS-52].

The drop-down list of machines will display those machines that are currently in use as 'disabled'. This will prevent the user from selecting them.

== Advanced Package Search
Addressed [JATS-7] Advanced package search does not find packages

Improved the SQL such that packages will be found.

== Removed many Pop-Up Windows
Altered many of the button operations to use a modal-dialog rather than a popup window.

Popup Windows are considered to be a bad practice and confusing to the user. The modal dialogs appear in the center of the Release Manager window and not on a different screen or under another window. 

== Move Package to a different view
The button is only provided to the user if the package has been released, otherwise the change will not be applicable.

== Action Buttons
Enabled hover text on disabled buttons.

== Editing Package Information
The editing process has been modified such that partial information can be entered [JATS-24].

It will not be possible to release the package before all the information has been entered, but the information required does not need to be entered at the same time.

== New Member and Lost Password information
This has been updated to provide useful information.


PageData:
==Summary of Changes
[[TOC]]
Changes introduced since the last release

== Build Status Page
>* Handle 'Preserved' Releases correctly

== Editing Package information
>* Extended the allowed size of the SVN tag.

== Build Plan [Experimental]
The Daemon Build Plan can be selected via the 'Build' menu available when a Release is being displayed. 
imagecenter:images/1-BuildPlan.png

The page shows the current build information and a list of packages that it plans to build, in the proposed order.

The build plan is recalculated before each build. It is not a queue of packages to be built, rather an ordered list of packages that would be built now. The list includes 'Test Builds' and directly released builds together with packages that will be rippled as a part of the build process.

== Build Time
The build daemons are now capturing and storing the duration of each build. This is now stored with the Release Manager database as a single time per package-version. Only the time of a successful build it retained. 

The build time includes the time to:
 * Extract the package from version control
 * Build the package
 * Run unit tests
 * Transfer the build artifacts to dpkg_archive
 * Insert data into the Release Manager database
This value may be used in the future to:
 * Enhance the build-plan with an estimated of build times
 * Provide a basis for limiting the time to build a package - to capture rouge builds and unit tests.
The Build Time can be seen in the 'Package Metrics' of a package. It will only be displayed if it exists.

== Display of Dates
Almost all instances where a date is displayed have been changed to make the date unambiguous ( ie: What is 2/3/16).

The form adopted is: Day DD-Mon-YYYY ( ie: Wed 2-Mar-2016)

== Unify the date-time pickers used within Release Manager
This affects:
 * Add / Edit Memo
 * Add / Edit Scheduled Task
 * Add / Edit Daemon Instruction
 * Add / Edit Scheduled Build outages
 * Report Selection

== Removed some application code from the database [JATS-48]
Removed use of ripple_field_states

== Adding an SDK to a Release
The process of adding an SDK to a Release is:

image:images/1-SdkManagement.png

1) The SDK Management button will toggle the display of the SDK Management Window

2) The SDK Management Window. This will show SDKs currently in use by the Release and all that addition and deletion of SDKs to the Release

3) The 'Add' button will pop up a dialog to add an SDK to the Release

The 'Add SDK' dialog:

image:images/2-SdkManagement.png

1) Select the SDK Family

2) Select the Version of the SDK required

3) Select the mode. The default mode will not remove package-versions from the Release. Conflicting packages will be displayed and the SDK will not be added. The 'Replace Packages' mode will automatically replace conflicting packages with those from the SDK.

4) Add the selected SDK to the Release.

== SDK Details Display
 * Highlight package version differences
 * Highlight package selection differences
 * Added checkbox to limit the display to diffs
 * Added buttons to allow all packages to be selected and deselected
 * Added a button to allow the exported packages from the reference release to be set 

== Release Merge / Diff
 * Highlight the reason that a Merge is not possible.
 * Restored the 'Undo' button.

== New Advanced Report
Find Files within a Package - Search and display partial file name within a given package.

== Login Process
 * Changed text to prompt for a Login
 * When a user is logged in, allow the user to log in again without logging out first.

== Tooltips
Modified the tooltip mechanism so that it will create any required page elements, rather than assume that  they are present.

== Deleting Package Versions
The 'History' and 'View by Version' pages have been enhanced to allow a user to delete (destroy) a package version under the following conditions:
 * They created OR own the package version
 * AND the version is not locked or pending. ie: It has not yet been released
 * AND the version is not in use by a Release. It may be a WIP or PENDING
This should allow developers to delete unneeded WIPS.

The Pending tab has been modified so that the package cannot be directly deleted. The user must 'Reject' the package before deleting it.

== COTS packages
When creating a new COTS, or COTS-like, package:
 * Ensure that the user has appended a patch-build number, for manually versioned packages
 * Display a message telling the user the expected format of a COTS package version

== Build Daemon Status Display
Moved the display options to a side panel. This frees up more screen real estate for displaying the Build Daemon Status.

Show the daemon control buttons, even when all the daemons have been stopped due to an Indefinite Pause. The user can still control the 
daemons, but they will not have any effect until the build system is operational.

== Package Not in Release
When viewing a version of a package within the context of a Release, if the displayed version is no longer a member of the 
Release then clicking on the 'Not in Release' icon will update the display with the version of the package that is in 
the Release.

== Project Log
Added a 'Project Log' page to the 'Admin' menu.

This page will display the content of the Release Manager 'Project Action Log. The log is not complete.

== Search for packages that contain specified Jira Issue [JATS-393]
The advanced search facility available under the 'Reports | Advanced Search | Find Jira / ClearQuest Bugs / Issues Location' menu has been
extended to allow searching for Jira issues. 

== Importing Package Dependencies from JATS/ANT [JATS-358]
Prevent users from accidently creating new packages and package versions. Add a step to Package Dependencies Import process. 

The new step will only allow the user to proceed if the package names are already defined and the package versions are already defined. The step allows package versions to be edited.

== UnBuildable Packages
There are a small number of packages that are spontaneously created via Deployment Manager. These packages are not a part of the build system 
and cannot be built by the build system. Release Manager has been enhanced to handle unBuildable Packages. They cannot be:
 * Released
 * Approved for build
 * Merged into a Release

== Dangling Package Versions
The main display page of Release Manager has been extended to show a user's Dangling Package Versions. These are package versions that have not been released, but are not associated with a Release.

Users are encouraged to review and Destroy such packages.

== Version History Browser
Improved the page layout to ensure that most of the controls are always visible.


== Package 'Used By' page
This page has been improved by:
>* The 'Used by Project' section is now displayed only on demand. This results in much faster loading of the base page. The extra detail is available, but only if the user wants it.
>* Added new sections. There are now nine sections showing the Projects, Packages and SDKs that use the displayed version. These are:
>>* Display all project that use any version of this package and project suffix
>>* Display all projects that use the current package and version
>>* Display all projects that use the current package - any version and suffix
>>* Display all packages that use any version of the current package and project suffix
>>* Display all packages that used the current package and version
>>* Display all packages that used the current package - any version and suffix
>>* Display all SDKs that use any version of the current package and project suffix
>>* Display all SDKs that used the current package and version
>>* Display all SDKs that used the current package - any version and suffix
>* Refactored the code so that is can be used with the 'History' browser. Now both displays show the same information.

== Package Version Browser
Corrected the operation of the Destroy and Revision buttons when the page is displayed outside of a Release. Under some conditions the user will be allowed to Destroy or Reversion the package. 

== Destroying a Version of a Package
This operation has been enhanced. New features include:
 * Operation occurs in a popup dialog
 * A sanity check is performs and the user will be given a list of reasons that the package should not be destroys. Some of these are simply advisory, some will prevent the version from being destroyed as it will impact other Releases,Packages, SDKs or SBOMs.

The user is forced to Destroy or Move a WIP from a Release. The option to 'Delete a WIP' is being incorrectly used resulting in WIPS that are not being used and confuse other users.

== Fixed Oracle Session Handle Leak [JATS-397]
Release Manager was leaking Oracle session handles. When binding variables to a database session, all the binding must be removed before the page processing completes otherwise the Oracle driver holds a session handle open.

In practice: All 'OraDatabase.Parameters.Add' statements need a matching OraDatabase.Parameters.Remove.

== Edit Software Licencing
Added editing facility to the 'Release Notes' page to allow the Software Licence to be updated on the displayed package version.

Improved the Admin | Licences page to allow the text of the licences to be changed.

== Admin Pages
The pages available via the 'Admin' tab have been modified:
 * They are now available, for display, to all users
 * Edit controls are enabled to users that have sufficient access to change the configuration.

== Navigation in 'Reports' and 'Members' pages
The standard Release Manager menu bar has been added to all the 'Reports' and 'Members' pages. The 'Exit' link has been removed from these pages as it serves no purpose.

== Manually Built Packages
Note: There is support for some legacy packages that are not built within the build system.

Disable the 'Test Build' button for manually built package.

PrevPageData:
@@@@@@@@@@@@@@@@6/11/2018 4:12:43 PM : 10.240.1.125@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release

== Build Status Page
>* Handle 'Preserved' Releases correctly
>* Added the 'Estimated Build Time' - fro the Master build machine.

== Editing Package information
>* Extended the allowed size of the SVN tag.

== Build Plan [Experimental]
The Daemon Build Plan can be selected via the 'Build' menu available when a Release is being displayed. 
imagecenter:images/1-BuildPlan.png

The page shows the current build information and a list of packages that it plans to build, in the proposed order.

The build plan is recalculated before each build. It is not a queue of packages to be built, rather an ordered list of packages that would be built now. The list includes 'Test Builds' and directly released builds together with packages that will be rippled as a part of the build process.

== Build Time
The build daemons are now capturing and storing the duration of each build. This is now stored with the Release Manager database as a single time per package-version. Only the time of a successful build it retained. 

The build time includes the time to:
 * Extract the package from version control
 * Build the package
 * Run unit tests
 * Transfer the build artifacts to dpkg_archive
 * Insert data into the Release Manager database
This value may be used in the future to:
 * Enhance the build-plan with an estimated of build times
 * Provide a basis for limiting the time to build a package - to capture rouge builds and unit tests.
The Build Time can be seen in the 'Package Metrics' of a package. It will only be displayed if it exists.

== Display of Dates
Almost all instances where a date is displayed have been changed to make the date unambiguous ( ie: What is 2/3/16).

The form adopted is: Day DD-Mon-YYYY ( ie: Wed 2-Mar-2016)

== Unify the date-time pickers used within Release Manager
This affects:
 * Add / Edit Memo
 * Add / Edit Scheduled Task
 * Add / Edit Daemon Instruction
 * Add / Edit Scheduled Build outages
 * Report Selection

== Removed some application code from the database [JATS-48]
Removed use of ripple_field_states

== Adding an SDK to a Release
The process of adding an SDK to a Release is:

image:images/1-SdkManagement.png

1) The SDK Management button will toggle the display of the SDK Management Window

2) The SDK Management Window. This will show SDKs currently in use by the Release and all that addition and deletion of SDKs to the Release

3) The 'Add' button will pop up a dialog to add an SDK to the Release

The 'Add SDK' dialog:

image:images/2-SdkManagement.png

1) Select the SDK Family

2) Select the Version of the SDK required

3) Select the mode. The default mode will not remove package-versions from the Release. Conflicting packages will be displayed and the SDK will not be added. The 'Replace Packages' mode will automatically replace conflicting packages with those from the SDK.

4) Add the selected SDK to the Release.

== SDK Details Display
 * Highlight package version differences
 * Highlight package selection differences
 * Added checkbox to limit the display to diffs
 * Added buttons to allow all packages to be selected and deselected
 * Added a button to allow the exported packages from the reference release to be set 

== Release Merge / Diff
 * Highlight the reason that a Merge is not possible.
 * Restored the 'Undo' button.

== New Advanced Report
Find Files within a Package - Search and display partial file name within a given package.

== Login Process
 * Changed text to prompt for a Login
 * When a user is logged in, allow the user to log in again without logging out first.

== Tooltips
Modified the tooltip mechanism so that it will create any required page elements, rather than assume that  they are present.

== Deleting Package Versions
The 'History' and 'View by Version' pages have been enhanced to allow a user to delete (destroy) a package version under the following conditions:
 * They created OR own the package version
 * AND the version is not locked or pending. ie: It has not yet been released
 * AND the version is not in use by a Release. It may be a WIP or PENDING
This should allow developers to delete unneeded WIPS.

The Pending tab has been modified so that the package cannot be directly deleted. The user must 'Reject' the package before deleting it.

== COTS packages
When creating a new COTS, or COTS-like, package:
 * Ensure that the user has appended a patch-build number, for manually versioned packages
 * Display a message telling the user the expected format of a COTS package version

== Build Daemon Status Display
Moved the display options to a side panel. This frees up more screen real estate for displaying the Build Daemon Status.

Show the daemon control buttons, even when all the daemons have been stopped due to an Indefinite Pause. The user can still control the 
daemons, but they will not have any effect until the build system is operational.

== Package Not in Release
When viewing a version of a package within the context of a Release, if the displayed version is no longer a member of the 
Release then clicking on the 'Not in Release' icon will update the display with the version of the package that is in 
the Release.

== Project Log
Added a 'Project Log' page to the 'Admin' menu.

This page will display the content of the Release Manager 'Project Action Log. The log is not complete.

== Search for packages that contain specified Jira Issue [JATS-393]
The advanced search facility available under the 'Reports | Advanced Search | Find Jira / ClearQuest Bugs / Issues Location' menu has been
extended to allow searching for Jira issues. 

== Importing Package Dependencies from JATS/ANT [JATS-358]
Prevent users from accidently creating new packages and package versions. Add a step to Package Dependencies Import process. 

The new step will only allow the user to proceed if the package names are already defined and the package versions are already defined. The step allows package versions to be edited.

== UnBuildable Packages
There are a small number of packages that are spontaneously created via Deployment Manager. These packages are not a part of the build system 
and cannot be built by the build system. Release Manager has been enhanced to handle unBuildable Packages. They cannot be:
 * Released
 * Approved for build
 * Merged into a Release

== Dangling Package Versions
The main display page of Release Manager has been extended to show a user's Dangling Package Versions. These are package versions that have not been released, but are not associated with a Release.

Users are encouraged to review and Destroy such packages.

== Version History Browser
Improved the page layout to ensure that most of the controls are always visible.


== Package 'Used By' page
This page has been improved by:
>* The 'Used by Project' section is now displayed only on demand. This results in much faster loading of the base page. The extra detail is available, but only if the user wants it.
>* Added new sections. There are now nine sections showing the Projects, Packages and SDKs that use the displayed version. These are:
>>* Display all project that use any version of this package and project suffix
>>* Display all projects that use the current package and version
>>* Display all projects that use the current package - any version and suffix
>>* Display all packages that use any version of the current package and project suffix
>>* Display all packages that used the current package and version
>>* Display all packages that used the current package - any version and suffix
>>* Display all SDKs that use any version of the current package and project suffix
>>* Display all SDKs that used the current package and version
>>* Display all SDKs that used the current package - any version and suffix
>* Refactored the code so that is can be used with the 'History' browser. Now both displays show the same information.

== Package Version Browser
Corrected the operation of the Destroy and Revision buttons when the page is displayed outside of a Release. Under some conditions the user will be allowed to Destroy or Reversion the package. 

== Destroying a Version of a Package
This operation has been enhanced. New features include:
 * Operation occurs in a popup dialog
 * A sanity check is performs and the user will be given a list of reasons that the package should not be destroys. Some of these are simply advisory, some will prevent the version from being destroyed as it will impact other Releases,Packages, SDKs or SBOMs.

The user is forced to Destroy or Move a WIP from a Release. The option to 'Delete a WIP' is being incorrectly used resulting in WIPS that are not being used and confuse other users.

== Fixed Oracle Session Handle Leak [JATS-397]
Release Manager was leaking Oracle session handles. When binding variables to a database session, all the binding must be removed before the page processing completes otherwise the Oracle driver holds a session handle open.

In practice: All 'OraDatabase.Parameters.Add' statements need a matching OraDatabase.Parameters.Remove.

== Edit Software Licencing
Added editing facility to the 'Release Notes' page to allow the Software Licence to be updated on the displayed package version.

Improved the Admin | Licences page to allow the text of the licences to be changed.

== Admin Pages
The pages available via the 'Admin' tab have been modified:
 * They are now available, for display, to all users
 * Edit controls are enabled to users that have sufficient access to change the configuration.

== Navigation in 'Reports' and 'Members' pages
The standard Release Manager menu bar has been added to all the 'Reports' and 'Members' pages. The 'Exit' link has been removed from these pages as it serves no purpose.

== Manually Built Packages
Note: There is support for some legacy packages that are not built within the build system.

Disable the 'Test Build' button for manually built package.


@@@@@@@@@@@@@@@@25/10/2016 11:12:53 AM : 10.240.2.161@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

==Summary of Changes
[[TOC]]
Changes introduced since the last release

== Build Status Page
>* Handle 'Preserved' Releases correctly

== Editing Package information
>* Extended the allowed size of the SVN tag.

== Build Plan [Experimental]
The Daemon Build Plan can be selected via the 'Build' menu available when a Release is being displayed. 
imagecenter:images/1-BuildPlan.png

The page shows the current build information and a list of packages that it plans to build, in the proposed order.

The build plan is recalculated before each build. It is not a queue of packages to be built, rather an ordered list of packages that would be built now. The list includes 'Test Builds' and directly released builds together with packages that will be rippled as a part of the build process.

== Build Time
The build daemons are now capturing and storing the duration of each build. This is now stored with the Release Manager database as a single time per package-version. Only the time of a successful build it retained. 

The build time includes the time to:
 * Extract the package from version control
 * Build the package
 * Run unit tests
 * Transfer the build artifacts to dpkg_archive
 * Insert data into the Release Manager database
This value may be used in the future to:
 * Enhance the build-plan with an estimated of build times
 * Provide a basis for limiting the time to build a package - to capture rouge builds and unit tests.
The Build Time can be seen in the 'Package Metrics' of a package. It will only be displayed if it exists.

== Display of Dates
Almost all instances where a date is displayed have been changed to make the date unambiguous ( ie: What is 2/3/16).

The form adopted is: Day DD-Mon-YYYY ( ie: Wed 2-Mar-2016)

== Unify the date-time pickers used within Release Manager
This affects:
 * Add / Edit Memo
 * Add / Edit Scheduled Task
 * Add / Edit Daemon Instruction
 * Add / Edit Scheduled Build outages
 * Report Selection

== Removed some application code from the database [JATS-48]
Removed use of ripple_field_states

== Adding an SDK to a Release
The process of adding an SDK to a Release is:

image:images/1-SdkManagement.png

1) The SDK Management button will toggle the display of the SDK Management Window

2) The SDK Management Window. This will show SDKs currently in use by the Release and all that addition and deletion of SDKs to the Release

3) The 'Add' button will pop up a dialog to add an SDK to the Release

The 'Add SDK' dialog:

image:images/2-SdkManagement.png

1) Select the SDK Family

2) Select the Version of the SDK required

3) Select the mode. The default mode will not remove package-versions from the Release. Conflicting packages will be displayed and the SDK will not be added. The 'Replace Packages' mode will automatically replace conflicting packages with those from the SDK.

4) Add the selected SDK to the Release.

== SDK Details Display
 * Highlight package version differences
 * Highlight package selection differences
 * Added checkbox to limit the display to diffs
 * Added buttons to allow all packages to be selected and deselected
 * Added a button to allow the exported packages from the reference release to be set 

== Release Merge / Diff
 * Highlight the reason that a Merge is not possible.
 * Restored the 'Undo' button.

== New Advanced Report
Find Files within a Package - Search and display partial file name within a given package.

== Login Process
 * Changed text to prompt for a Login
 * When a user is logged in, allow the user to log in again without logging out first.

== Tooltips
Modified the tooltip mechanism so that it will create any required page elements, rather than assume that  they are present.

== Deleting Package Versions
The 'History' and 'View by Version' pages have been enhanced to allow a user to delete (destroy) a package version under the following conditions:
 * They created OR own the package version
 * AND the version is not locked or pending. ie: It has not yet been released
 * AND the version is not in use by a Release. It may be a WIP or PENDING
This should allow developers to delete unneeded WIPS.

The Pending tab has been modified so that the package cannot be directly deleted. The user must 'Reject' the package before deleting it.

== COTS packages
When creating a new COTS, or COTS-like, package:
 * Ensure that the user has appended a patch-build number, for manually versioned packages
 * Display a message


PageData:
==Summary of Changes
[[TOC]]

== Access Control
Release Manager has been altered such that only a logged in user may display any information. 

This is in line with the other applications in the Manager Suite: Access Manager, Deployment Manager and Production Manager.

== Destroying a Release
A Release must be Close, Preserved or Archived in order to be destroyed. 

The restriction that the user needed to delete associated build daemons has been removed.

== Release Diff / Merge
Sped up loading and processing of this page through internal changes:
 * Removed many hidden fields and replaced them with attribute data. The very large numbers of form fields caused some password managers to perform badly.
 * Cleaned up the form POST data by removing unneeded input fields - by hiding them.

== Build Service Configuration
The Name of the LXR Server is now configurable.

== Licensing for packages in a Release.
This has been extended to include:
 * The packages "Short Description"
 * Licenses applicable (configured) on other versions of the package
 * Edit widget to allow the licenses to be updated
 * A "Show All" button to allow the licensing information for all packages in the release to be shown.

== Package Deprecation
Corrected the operation of this feature.

== Copy to Clipboard
Added several 'Copy to Clipboard' icons to the 'Release Notes' page.
Click on the icon or double click the field to copy the field text to the clipboard.

== Display and Edit 'Deployable State'
A new item has been added to the 'Release' Menu to allow the use to Display and Edit the 'Deployable State' for all packages in the Release.

If the release cannot be edited, then the Edit options are not available. The user can still view the state of the flags.

== Unused Package Display
This display has been extended to allow the selective exclusion of:
 * 3rd Party Packages
 * Products and Auto Products
 * Packages marked as deployable

== Projects Menu 
The projects shown in the Project menu is now limited to active projects.

== Used by SBOM
Extended the 'Used By' tab to show SBOMs that use the package.

== Build Machine configuration
Added some error checking to the Build Configuration page.
 * Detect if the build set has more than one Master
 * Detect if each Machine Type (GBE_MACHTYPE) does not have a TOOLSET builder configured.
The 'Build Status' and 'Build Plan' pages will indicate configuration errors and warnings, with a link to the
configuration page where details are available.

== Reject Packages approved for Building
The logic allowing a package, that has been approved for building, to be rejected has been enhanced. A package can be rejected if:
 * The user has required permissions AND
 * The release has no active (not Paused or Disabled ) daemons OR
 * The package build has failed

== Workflow for Manually Build Packages
The workflow for an Open release is now the same as all others. A WIP package goes to Pending and then the Released.
The user will be prevented from 'Releasing' a package unless it exists in dpkg_archive

== Package Display Action Buttons
Changes to the logic of disabling the Action Buttons has been simplified.
An attempt has been made to show all action that could be available, but to deactivate those actions that are not currently allowed.
Hover text on inactive buttons has been enabled.

== Release Menu
Some of the options have been disallowed if the release is not open.

New Options:
 * Clone Release
 * Destroy Release. The release must be closed.

== Adding daemon Instructions. Test Build and Ripple Build
Fixed the error handling such that errors are provided within the dialog that is adding the instructions.

== Ripple and Test Builds
Added buttons to allow the easy removal of a pending Test build and Ripple build
Changed the Package State icons for Test Builds and Ripple Builds

== Merge Manager - Release Difference display
Fixed several issues:
 * Show Pending changes - with all filter options 
 * Deletion of a pending delete
Several improvements
 * Fewer data base access - increase display speed
 * Result Filter moved to a side panel
 * Added checkbox to the result files to cycle the filters between, current, inverted, all, none and original.
 * The Result Filter 'refresh' button is only enabled if the current filter setting have been changed.
 * New Filter - filter out 'Pending' operations
 * New Filter - Filter out Updates that appear to be downgrades
 * New icon and color to highlight Updates that appear to be downgrades
 * Do not generate HTML report unless required
 * Generate URLS with the release information. This improves behaviour when the pages have not been fully loaded.

== Highlight deprecated build machines
Changes have been made to pages that show the status of the build machines to highlight the presence of a machine that
is no longer available for use.
This may arise when a 'closed' release is re-opened. The selected build machines may no longer be available.

== Better support for unused Package Names
 * Allow unused package named to be deleted
 * DO not allow a user to select an unused package name when selecting package-versions to add to a release

== Project Creation
Removed the ability to create a new project from the 'Administrators' role.

The issue is that an Administrator could create a new project, but then could not do anything with it as the process of creating a new project does not setup access to the new project.
At the moment setting up access can only be done in Access Manager - and it is not trivial.

Removing the ability to create a new project will force a SAF fo a new project. This can be done by someone with access/knowledge to create a new project AND set up the required access permissions.

== Edit Project Name
The 'Project Name' can be edited on the 'Admin | Project Info' Page, along with other Project specific information.

== Release Notes Page
 * Fixed toggling of the Package Metrics
 * Note editing will position page to the note section
 * All 'edit' controls moved into the fieldset surrounding the edit area. Improves screen real estate usage.
 * Extended the 'Build Inclusion' field of the 'Ripple Properties' section to include the reason for any exclusion.
 * Added 'Previous NonRipple Version'
 * Added JATS commands to assist in the creation of a new package
 * Clarified 'Owner' as 'Build Owner' and added help text

== Internal Wiki
Fixed the 'gHideWikiSource' config option.

== Package Rename
It is possible to rename a package if there is one and only one version of the package.

Once there is more than one version of a package the package will have been released and the name will 
be fixed in build files.

The rename operation is achieved via the 'Package Version Rename' dialog.

== Files and Folders display
>* Improved page generation via use of CSS instead of images for color
>* Removed Product Component stuff - its never been used
>* Improved version comparison
>>* Added button to goto either version in the comparison
>>* Added size and chksum for both versions in a comparison
>* Added Folder opener and closers to show/hide sub directories
>>* By default the 'utResults' and 'lcov' are not expanded

== Added Ripple Stop
Two properties that apply to a package-version per release.
When the build system needs to 'ripple' a package marked as 'Ripple Stop', then it will not build the package
nor any packages that depend on the package - until the user has removed the ripple stop marker.

This is intended to simplify the building of MOS 'MUG' packages that should not be built on every ripple as 
the version numbers are limited. These package only support a major and minor version number.

1. A package may be marked as a Persistent Ripple Stop
2. A package may be marked as Ripple Stop

When a package is flagged with a Persistent Ripple Stop, then each new version of the package will be marked as
having a Ripple Stop, otherwise the Ripple Stop marker is removed when the package is rippled.

== Notifications
Add a tab to the package details display to show the users who will be sent a notification when the package is modified.
Add a Page to show all notifications configured in a Project. 

Notifications are for new versions of a named package in any release within a project.

A 'ViewAdmin' can delete a user from the list.
The user can delete their own entries from the list. This can also be done in the 'Release Notes' tab.

== Build Status Page
Added the 'Estimated Build Time' - for the Master build machine.

== Build Logs
Optimised the Oracle Query to improve display speed for most operations. Sorting by Package-Version and Build Duration is very slow.
Added the 'Build Duration' to the display

== Search and Browse by Release
Add a 'Search by Release' mode to the front page and shortcut icons.

This allows a user to search or browse for a specific release.

== Release Properties
 * Prevent Names with leading and trailing white space from being used
 * Improve input validation
 * Fixed issues where fields were forgotten when processing errors

== Editing Base View
Added a edit widget on the 'Release Notes' page to allow the packages 'Base View' to be edited from the screen in which it is shown.

== Caching of page resources
Added a global version number to all instances where files that are normally cached by web browsers are included. This addresses the issue where a resource file,
such as a style sheet, is updated. Bumping the global version number will ensure that users will pick up the new resource.

== Release Statistics
Added a page to display 'Release Statistics'. Supports:
 * Removal of COTS and TOOL packages
 * Removal of packages provided by an SDK
 * Display of Unit Tests per package
 * Display of Build Time
 * Exporting of Unit tests information via CSV

Added page to allow the extraction of the statistics to be automated.
The page is: 'release_stats_rest.asp' With parameters it will display some help.


== Base View Administration
Added a page to allow base views to be managed. Base views can be
 * Renamed
 * Deleted if they are not in use
 * New ones created
The page shows the number of packages that are using each base view

== Public Views
Improved the display: 
 * Added package counts to Base View packages
 * Hide the 'Show' Icon on 'Base' and 'SDK' views

== Copy Package Name and other details to clipboard
Extended the 'Dependencies' tab with a menu item to allow the user to copy the Package Name and version to the clipboard in various formats.

== User name handling
Enhanced the display of user names:
 * Provide a menu to allow the user to copy the name, email address or to send an email
 * Always use full user names - not a mix a login and full names

== Release Metrics
Enhanced the 'index' page to provide better Release Metrics.
 * Improved the numbers provided
 * Corrected the number provided
 * Improved the HTML layout
 * Allow various tables to be exported as CSV

Enhanced the 'Package Version' page to display some of the metrics.

== Package Version History
Used a sortable tables widget to allow in-page sorting/searching of the columns

== Editing Package Ownership
 * Added a page to view/edit all the packages and package Owners in a Release


