End of Product Life Cycle: Overview

This is 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.

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: The end-of-life milestones and CollabNet commitments are presented in the following table.
Products, Platforms and Software Description When? Replacement Options
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.
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 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.
Perforce No support for Perforce integration Supported in TeamForge 8.1 and earlier | Not supported from TeamForge 8.2 and later NA
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.
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.
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 Customers can use the latest TeamForge SOAP/REST APIs.
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 might have to be converted.
Tasks component No support for "Tasks" component Supported in TeamForge 17.8 and earlier | Not supported from TeamForge 17.11 and later Tasks component becomes obsolete from TeamForge 17.11 release. You may create a Tasks tracker, if required.
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
SSH tunneling No support for SSH tunneling Supported in TeamForge 16.7 and earlier | Not supported from TeamForge 16.10 and later NA
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.
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.

RHEL/CentOS 6.x No support for Red Hat Enterprise Linux/CentOS 6.x platform Support for RHEL/CentOS 6.x platform ends by Dec 2017 or once RHEL/CentOS 8 is released (whichever comes first). RHEL/CentOS 6.x is reaching end of “Production 2 Phase” (“limited support”) in May 2017.

Update to RHEL/CentOS 7.x or later.

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 databse and datamart or move datamart to a separate server (virtual machine).

Unmanaged CVS servers No support for unmanaged CVS integration servers. Managed CVS servers are supported as usual. Supported in TeamForge 17.11 and earlier | Not supported from TeamForge 18.2 and later During an upgrade, unmanaged CVS integration servers are "disabled" (converted to use the "generic adapter"). For more information, see Difference between managed and unmanaged CVS servers.
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.2 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.2 release.