Cookie Policy

We have placed cookies on your device to help make this website better. Find out more here

Necessary Cookies

These cookies are necessary for the function and operation of this website. Without these cookies we would not be able to offer you services such as contact forms and territory selection. These cookies collect anonymous information and cannot track your movements on other websites.

show CookiesHide Cookies

Name

Domain

_hs_opt_out

censhare.com

_hssc

censhare.com

_hssrc

censhare.com

_hstc

censhare.com

_ga

censhare.com

_gid

censhare.com

allowCookies

censhare.com

hsfirstvisit

censhare.com

hubspotutk

censhare.com

prefGeo

censhare.com

driftt_aid

censhare.com

drift_campaign_refresh

censhare.com

drift_aid

censhare.com

Marketing Cookies

Marketing Cookies are being used to deliver adverts and other communications relevant to you and your interests, to limit the number of times you see an advertisement and to help measure the effectiveness of advertising campaigns.

show CookiesHide Cookies

Name

Domain

_gat_UA-59173416-1

censhare.com

hubspotutk

censhare.com

Product Life Cycle

The life cycle of the censhare product

censhare Upgrades follow a regular release cycle. This not only provides planning reliability when it comes to new releases and availability of new functionality, but also allows us a coherent and rigorous product development.

End of Life / End of Service

With the release of an Upgrade, all previous versions of the Licensed Software reach their End of Life (EOL). Still, we do provide full support and bug fixes for additional 36 months for previous versions until they reach their End of Service (EOS). Of course, we support our customers with the planning of and migration to newer versions of censhare.

With the release of a new Upgrade, no more new functionalities are being added to previous versions, they reach their End of Life (EOL).

All versions below 2019.1 have already reached their End Of Life / End Of Service!

End of service 2022

Please upgrade from versions 2018.3.x to 2019.2.x to a later version in 2022 to avoid running out of service.

25 January 2022 Version 2018.3.x

Released: 23 November 2018 | End of Life: 25 January 2019

18 April 2022 Version 2019.1.x

Released: 25 January 2019 | End of Life: 18 April 2019

22 November 2022 Version 2019.2.x

Released: 18 April 2019 | End of Life: 22 November 2019

End of service 2023

Please upgrade from versions 2019.3.x to 2020.2.x to a later version in 2023 to avoid running out of service.

20 March 2023 Version 2019.3.x

Released: 22 November 2019 | End of Life: 20 March 2020

7 August 2023 Version 2020.1.x

Released: 20 March 2020 | End of Life: 7 August 2020

16 Oktober 2023 Version 2020.2.x

Released: 7 August 2020 | End of Life: 16 Oktober 2020

End of service 2024

Please upgrade from versions 2020.3.x to 2021.2.x to a later version in 2023 to avoid running out of service.

30 July 2024 Version 2020.3.x

Released: 12 January 2021 | End of Life: 30 July 2021

26 November 2024 Version 2021.1.x

Released: 30 July 2024 | End of Life: 26 November 2021

Support for a version which is End of service

With the Service Level Agreement (SLA), the customer agrees to our product life cycle and thus to the "End of Service". If a version reaches the "End of Service" status, this has the following support consequences:

  • The SLA is still valid and we are bound to support availability and response time.

  • We continue to strive to provide the customer with satisfactory support.

  • No bugfixes will be provided for this version.

  • A simple workaround, such as restarting the system, should be accepted as the final solution.

  • It is also possible that neither a solution nor workaround can be provided.

  • No special readiness can be guaranteed, e.g. on weekends or public holidays.

  • We are allowed to charge our efforts.

Product Release Cycles

Public releases (upgrade versions)

Upgrades deliver substantial performance improvements, architectural changes and/or new features and functionalities and appear regularly. An Upgrade will change the second digit of the version number of the licensed software (e.g. 2021.1 to 2021.2). The first Upgrade after the turn of a year also changes the first digit of the version number (e.g. 2021.2 to 2022.1).

Version schema: year date + sequence number for each release

Release Candidates

A Release Candidate is a beta versions of a public release/upgrade version and serves for internal testing purposes only.

Revision releases (update versions)

Revision releases delivered as needed. Updates deliver fault revisions (“bugfixes”) and minor improvements to the licensed software and are released on demand. An Update will change the third digit ofthe version number of the Licensed Software, e.g. from version 2021.2.1 to 2021.2.2.

Version schema: year date + release sequence number + revision sequence number

We make all internal releases available for beta testing to censhare colleagues and partners.

After the release of a public version an upgrade to an official public version is mandatory.