Ucm4Svn ReleaseNotes

UCM4SVN Release 2.4 - Orchestra Build

• Bug fixes:
  • This build was a re-pack of the existing build to remove the search buttons from the template as a bug was located, there have been no code changes what so ever.

UCM4SVN Release 2.4

UCM4SVN 2.4 is the latest feature release providing exciting new features including a JIRA plugin that allows Developers to work with UCM4SVN entirely through the JIRA user interface, as well as an Eclipse plugin for Eclipse-based developers.

New Features

• JIRA plugin, which allows you to drive UCM4SVN developer actions from JIRA.
• Eclipse plugin, providing to-do list and basic developer actions.
• Java Checkout GUI improvements:-
  • Open Folder after checkout
  • Allow user to save Subversion password in encrypted format.
• You can now clone activities for another project. This makes it easier to create an activity with the same title and description in another project.
• Improved display for activities with long titles.
• You can now see all activities awaiting integration from all projects on the Integrate tab.
• Baseline names can now contain a wider set of special characters including '.', '+' and '-'.

Bug Fixes

• For Subversion repositories with UCM4SVN-managed authz-based access control, allow developers to resolve merge conflicts on the project integration branch whilst the activity is being merged.
• The UCM4SVN server port number was missing from some email notifications. This has been corrected.
• Edit user page no longer reverts the displayed settings to previous settings after an update to a user profile.
• Intermittent error with ReviewBoard settings not being shown on the Edit Project page.
• Fixed issue with disabling ReviewBoard integration for projects with existing reviews.
• Addressed issue with Edit Activity changing the state of the activity under certain conditions.
• Improved display of login page for Internet Explorer 7 users.
• Addressed issue with Loading page refreshing rapidly.

UCM4SVN Release 2.3

UCM4SVN 2.3 is a feature release providing new functionality and some bug fixes.

Existing customer upgrading from earlier releases must upgrade their database after the installation of UCM4SVN 2.3.

Please make sure you back up your database before upgrading to UCM4SVN 2.3. Once the database has been upgraded, it will be incompatible with previous releases, and you will not be able to go back.

New Features

Shared Components

Shared components allow you to share changes on some components between projects. This can be useful for shared code such as class libraries or third-party deliveries, for which you would like to use the same version across all of your products.

Activities performed on shared components are visible in all projects that share the component, and they are integrated into the same shared integration branch. As a result, activities performed on shared components appear in the baselines of all projects sharing the component.

To use a component in shared mode, click the Shared tick box for the component when you create a new project.

Password Encryption in Configuration Files

In previous releases of UCM4SVN, passwords for Subversion, email and other external systems such as Trac and JIRA had to be provided in configuration files in plain text, making it possible for anyone with read access to a configuration file to see the passwords contained in it.

It is now possible to encrypt passwords using the ucm4svn_passwd utility. Please see Admin Guide for details.

UCM4SVN Information in Subversion Logs

UCM4SVN now logs activity-related information in Subversion log messages as actions such as Accept, Close, Deliver or Integrate are performed. This makes it easier to identify UCM4SVN activities in the Subversion repository and allows you to track who performed actions and why on the Subversion side.

Confirm Merge After Conflict

If merge conflicts occur during the integration or delivery of an activity, you can now resolve the conflicts outside of UCM4SVN and mark the activity as integrated. This will ensure that the manually integrated activity correctly appears in the list of activities for the next baseline.

A new button is shown at the bottom of the Merge Conflict page which allows you to mark the activity as merged.

Other Changes

• ENH-2223: Emails notifications will now only be sent to members of the project that the email notification relates to. In particular, this affects notifications to integrators regarding new activities ready for integration.
• ENH-2204: UCM4SVN now provides direct links to JIRA, if JIRA activities cannot be transitioned to their next state. A direct link to the transition being performed can also be included. Please see the Admin Guide for details on the new jira_show_transition_links option.
• ENH-2170: UCM4SVN now records additional information including stack traces, if internal errors occur.

Bug Fixes

• ENH-2171: Resolved issue with reassigning activities from the Edit Activity tab.
• UCM-128: Resolved issue with the pull-down select list on the Assign Activity tab for Google Chrome users.
• UCM-143: Fixed problem with the Edit Project page not always displaying review settings correctly.
• UCM-144: Made it possible to have users who are only Reviewers and do not have any other roles. Previously, reviewers without any additional roles were unable to log in.

UCM4SVN Release 2.2

UCM4SVN 2.2 is a feature release providing new functionality and some bug fixes.

Please make sure you back up your database before upgrading to UCM4SVN 2.2. Once the database has been upgraded, it will be incompatible with previous releases, and you will not be able to go back.

New Features

ReviewBoard Integration

The 2.2 release provides a new integration with the Open-Source ReviewBoard code-review management system. This allows you to automatically post reviews to a Review Board server and track progress of reviews within UCM4SVN. UCM4SVN will also automatically create fix activities for any activities that have failed a review.

Please see http://www.reviewboard.org for more information on ReviewBoard.

Trac Integration

A new integration with the Trac change management system has been implemented, adding to the existing integrations with Jira and ClearQuest.

Selective Checkout

UCM4SVN can now generate checkouts scripts that cover only parts of a project, baseline or activity. This is particularly useful for developers working on a small part of a product and not needing the complete project to be checked out.

Improved Merge-conflict Handling

If there are any conflicts during the merge of an activity or a rebase, UCM4SVN will provide checkouts scripts (for Linux, Windows and Java), which will set up a workspace for you showing the merge conflict and allowing you to resolve the issue and commit the changes to Subversion.

Automatic Subversion Access Control for Activity and Project Branches

UCM4SVN can now manage access to the Subversion repository based on Subversion authz rules. This allows you to limit access to project and integration branches

Other Changes

• Improved configuration file checking will alert you of serious issues in your configuration file.
• API Changes
  • New API functions to get and close activities.
  • An XML schema is now provided for the UCM4SVN API responses.
  • UCM4SVN will now return id of newly created element on all creation functions.

Bug Fixes

• For some users, merging large activities could cause timeout messages in the browser. All pages with lengthy operations are now routed through an intermediate "Loading" page such that timeouts will no longer occur.
• UCM4SVN now provides support for Subversion access through svnserve.

UCM4SVN Release 2.1

UCM4SVN 2.1 is a minor enhancement and bug-fix release, which is compatible with the UCM4SVN 2.0 database format.

New Features

• New API functions to
  • Create components
  • Create projects
  • Create activities

Bug Fixes

• If both ClearQuest and JIRA integrations were disabled but allow_multiple_activity_sources was set to 1 in the config file, projects created with these settings would not allow you to create new activities.

UCM4SVN Release 2.0

UCM4SVN 2.0 is a major release, which refines many of the concepts of previous UCM4SVN releases. Projects have attained a more important role as they are now the central focus point for UCM4SVN operations. In particular, activities now stretch across projects rather than components and changes are integrated back onto project integration branches rather than the trunk of individual components.

New Features

• Projects now have their own project integration branch.
• It is now possible to baseline projects, which creates Subversion tags and baseline information in UCM4SVN for all components in the project. New projects can be started from another project's baselines, making it possible to create follow-on projects based on previous projects. For each component in the new project, you can choose a project baseline to use for the creation of the new project.
• Activities now stretch across projects. When an activity is started, all components of a project become part of the activity.
• New mechanisms for checking out data have been introduced. Where previously the only option was to cut-and-paste 'svn checkout' commands into a shell window, you now additionally have the option to download activity-specific checkout scripts:-
  • Java checkout application with graphical user interface (requires Java to be installed client-side)
  • Windows checkout batch file
  • Linux shell script
• Read-only components in projects. A read-only component cannot be changed with activities. It is a reference component (e.g. an external component) that cannot be updated as part of a project.
• Baselines can be labelled with a status to indicate their status, e.g. in terms of quality (Good, Bad, Tested, ...)

Bug Fixes

• A number of forms have been fixed such that data entered by the user is retained on errors.
• When creating activities, you can now assign multiple users. Previously this was only possible through the Reassign Activity tab.

UCM4SVN Release 1.4

Features of release:

• UCM4SVN now supports JIRA behind a https:// protocol. Use exactly as before except add https://
• Fixed a bug which prevented delivery from working in some cases when subversion authentication was turned on.

UCM4SVN Hotfix Release 1.3

Release 1.3 is a hotfix release to fix some bugs introduced by the latest 1.2 Release.

Bug Fixes:

• Changing a NON JIRA user's username and/or password failed.
• Editing an activities description with a non-project manager account resulted in an error
• The server port number was missing from the email notifications

UCM4SVN Release 1.2

Release 1.2 is a major release providing support for the integration between UCM4SVN and JIRA.

Release Highlights:

• Import users directly from JIRA
• Use your JIRA user name and password to log into UCM4SVN
• Create UCM4SVN activities directly from JIRA
• Change the state of an issue in JIRA in parallel to its stage of development in UCM4SVN
• Receive e-mail updates whenever you are assigned a new activity or an activity is available for integration
• Edit your user profile

Please note that UCM4SVN 1.2 is incompatible with previous releases. Existing users of UCM4SVN 1.0, please contact sales@clearvision-cm.com for upgrade information.

UCM4SVN Release 1.0

Release 1.0 is the initial release of UCM4SVN. CentOS 5.2 is the first supported platform for the server (others will be supported in the future). UCM4SVN is delivered as a web service, so clients can usue any platform that supports a web browser.

Known Issues

1. When creating an Activity, if the "do nothing" option is selected (ie the "---" separator), a message box is displayed with the error "Problem retrieving components for this project: INTERNAL SERVER ERROR (500)". To rectify this issue, click on the 'OK' button of the message box, and then select a valid project. This error doesn't cause any issues with your database and will be fixed in the next release of UCM4SVN.

1. When Integrating, it's possible to not select any activities to be merged, and try to merge. In this case, it will appear that a merge has happened, but in reality, nothing happens in Subversion.