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

There are a couple of known issues with UCM4SVN v1.0, but neither of these should prevent normal usage, they are listed here for your information.

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.

2. 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.