Products reach the end of their life cycle for a number of reasons. These reasons may be due to market demands, technology innovation and development driving changes in the product, or the products simply mature over time and are replaced by functionally richer technology. While this is an established part of the overall product life cycle, CollabNet recognizes that end-of-life milestones often prompt companies to review the way in which such end-of-support and end-of-life milestones impact the CollabNet products or its supported platforms. With that in mind, we have set out below CollabNet’s end-of-life policy to help customers better manage their end-of-life transition and to understand the role that CollabNet can play in helping to migrate to alternative CollabNet products, platforms and technologies. The general policy guidelines are:
- As a general rule, CollabNet will provide six months’ notice and we would send out regular notifications to all our customers through our CollabNet blog, product notifications and/or support newsletter.
- We would End-Of-Life support for our products, platforms and software with our new version of our product release.
- We would continue to provide support to our products, platforms and software for our earlier supported product version.
- You will need to ensure that you have a current and fully paid support contract with CollabNet to receive notifications on end of life. Please contact your Account Manager regarding fees payable during the end-of-life period so that we can support you right through the end-of-life transition period.
- See the list of Currently Supported Products for more information.
|Products, Platforms and Software||Description||When?||Replacement Options|
||No support for
|CVS||No support for CVS||CVS supported in TeamForge 20.1 and earlier | CVS not supported from TeamForge 20.2 and later||Use other SCM tools like Git.|
|EventQ||No support for EventQ||EventQ supported in TeamForge 19.3 and earlier | EventQ not supported from TeamForge 20.0 and later||Use the Webhooks-based Event Broker in place of EventQ.
Some of the EventQ related features such as the Activity Stream, EventQ based reports, and the Include Traceability check box (on the add/edit project tool page) have already been disabled in TeamForge 19.0 and later by default, however, with an option to enable them again if required.
TeamForge's native Webhooks-based Event Broker replaces EventQ as the default event broker to support integrations with tools such as Jenkins, Jira and TestLink and hence EventQ is no longer supported in TeamForge 20.0 and later.
|Nexus 2||No support for Nexus 2||Nexus 2 supported in TeamForge 19.1 and earlier | Nexus 2 not supported from TeamForge 19.2 and later||Upgrade to Nexus 3.|
|Chinese Korean and Japanese (CJK) locales||No support for CJK locales with TeamForge 17.1 and later||CJK supported in TeamForge 16.10 and earlier | CJK not supported from TeamForge 17.1 and later||NA|
|Crucible Plug-in||No support for Crucible plug-in||Supported in TeamForge 18.1 and earlier | Not supported from TeamForge 18.2 and later||NA|
|Artifactory versions later than v4.7||No support for Artifactory versions later than v4.7||Supported in TeamForge 18.1 and earlier | Not supported from TeamForge 18.2 and later||NA|
|TeamCity||No support for TeamCity||Supported in TeamForge 18.1 and earlier | Not supported from TeamForge 18.2 and later||NA|
|Activity Stream||No support for EventQ Activity Stream||Supported in TeamForge 18.2 and earlier | Not supported from TeamForge 18.3 and later||NA|
|DLM 1.x||No support for DLM 1.x||Supported in TeamForge 17.4 and 17.8 | Not supported from TeamForge 18.1 and later||NA|
|Old site-options.conf syntax||No support for older syntax for defining your HOST token (HOST_xxx)||Supported in TeamForge 17.11 and earlier | Not supported from TeamForge 18.1 and later||To ensure backward compatibility, TeamForge supported both old and new syntaxes for defining your HOST token. However, this backward compatibility will be available only with TeamForge 17.11 and earlier versions. It is recommended to adjust your site-options.conf in line with the new syntax (xxx:SERVICES) as support for older syntax would be dropped in TeamForge 18.1 release.|
|Unmanaged CVS servers||No support for unmanaged CVS integration servers||Supported in TeamForge 17.11 and earlier | Not supported from TeamForge 18.1 and later||During an upgrade, unmanaged CVS integration servers are "disabled" (converted to use the "generic adapter"). This is similar to how Perforce integration servers were disabled.|
|Running two PostgreSQL clusters on the same server||The ability to run two PostgreSQL clusters on the same server is deprecated||Supported in TeamForge 17.8 and earlier | Not supported from TeamForge 17.11 and later||Use same cluster for database and datamart or move datamart to a separate server (virtual machine).|
|RHEL/CentOS 6.x||No support for Red Hat Enterprise Linux/CentOS 6.x platform||Supported in TeamForge 20.3 and earlier | Not supported from TeamForge 21.0 and later.||Update to RHEL/CentOS 7.x or later.|
|Microsoft Project Integration||No support for MS Project integration||Supported in TeamForge 5.2–6.1 | Not supported from TeamForge 6.2 and later||NA. Tasks component becomes obsolete from TeamForge 17.11.|
|Black Duck Code Sight||No support for Black Duck Code Sight||Supported in TeamForge 16.10 and earlier | Not supported from TeamForge 17.1 and later||Use TeamForge's native Code Search function powered by Elastic Search. Available in TeamForge 17.1 and later.|
|SSH tunneling||No support for SSH tunneling||Supported in TeamForge 16.7 and earlier | Not supported from TeamForge 16.10 and later||NA|
|VMware Player image||VMware Player appliance image is no longer available for TeamForge 16.7 and later||Available in TeamForge 16.3 and earlier | Not available from TeamForge 16.7 and later||TBD|
|Tasks component||No support for "Tasks" component||Supported in TeamForge 17.11 and earlier | Not supported from TeamForge 18.1 and later||Tasks component becomes obsolete from TeamForge 17.11 release. You may create a Tasks tracker, if required.|
|Berkeley DB backend for Subversion||No support for Berkeley DB||Supported in TeamForge 16.3 and earlier | Not supported from TeamForge 16.7 and later||All new Subversion repositories, by default, use the FSFS backend. Existing repositories must be converted.|
|TeamForge SOAP5.x||No support for SOAP5.x API support||Supported in TeamForge 16.7 and earlier | Not supported from TeamForge 16.10 and later||Use the latest TeamForge SOAP/REST APIs.|
|Project Tracker||No support for the Project Tracker component||Supported in TeamForge 16.7 and earlier | Not supported from TeamForge 16.10 and later||NA. Project Tracker becomes obsolete from TeamForge 16.10 release.|
|Advanced mode installation||No support for advanced mode installation||Supported in TeamForge 8.1 and earlier | Not supported from TeamForge 8.2 and later||NA. TeamForge 16.7 and later support dedicated installation only.|
|Perforce||No support for Perforce integration||Supported in TeamForge 8.1 and earlier | Not supported from TeamForge 8.2 and later||NA|
|TeamForge on SUSE||No support for SUSE||Supported in TeamForge 8.1 and earlier | Not supported from TeamForge 8.2 and later||Migrate to RHEL/CentOS platforms.|
|TeamForge SOAP4.x||No support for SOAP4.x API||Supported in TeamForge 7.2 and earlier | Not supported from TeamForge 8.0 and later||Customers can use the latest TeamForge SOAP/REST APIs.|
|TeamForge 32-bit||No support for 32-bit platform||Supported in TeamForge 7.2 and earlier | Not supported from TeamForge 8.0 and later||Move to 64-bit platform.|