Skip to main content

WHAT IS OUR NEW END OF LIFE POLICY?


We're writing to you today to announce a new End of Life (EOL) policy for our software products and features. This policy outlines a consistent and transparent process for managing the lifecycle of our offerings and provides you with clear timelines for when products or features will be retired.

You can read the full, detailed policy document attached. We highly encourage you to review it, but for now, here is a summary of what you can expect.

 

WHY ARE WE INTRODUCING THIS POLICY?


At Oleeo, our commitment is to provide you with the most secure, stable, and valuable tools for your recruiting needs. To do that, we need to continually innovate and focus our resources on new technology and enhancements.

Introducing a formal EOL policy allows us to:

  • Innovate faster by concentrating our development efforts on new and improved features.
  • Enhance security and stability by removing outdated components that could pose a risk.
  • Improve performance by maintaining a clean and efficient codebase.
  • Provide predictability for you, our customers, so you can plan for transitions and upgrades with clear, advance notice.

 

KEY DEFINITIONS AND LIFECYCLE STAGES


This policy uses a few key terms to define the stages of a product or feature's life. Here’s a quick overview:

  • End of Life (EOL): The date after which a feature will no longer be actively developed or enhanced.
  • End of Sale (EOS): The date after which a feature is no longer offered for sale to new customers.
  • End of Support (EOSu): The date after which Oleeo will no longer provide technical support, bug fixes, or security patches. After this date, the feature or code may be removed and will no longer be accessible.

In between these stages, a feature may enter Maintenance Mode, where it's no longer getting new features but will still receive critical bug fixes and security patches.

 

HOW WILL WE NOTIFY YOU?


When a product or feature is reaching its EOL, we will provide you with advance notice through multiple channels, including:

  • Email notifications to designated customer contacts.
  • In-app notifications within the Oleeo platform.
  • Announcements on the Oleeo Community and in our release notes.
  • Direct communication from your Customer Success Manager or Commercial Director.

The amount of notice you receive will depend on the type of offering, but we are committed to providing you with ample time to prepare. For example, for major products like Oleeo Recruit or Engage, we will provide a 12-18 month notice period before the EOL date. For smaller features, integrations, or APIs, the notice period will be shorter.

All EOL notifications will include:

  • The name of the affected product or feature.
  • The scheduled EOL, EOS, and EOSu dates.
  • The reason for the change.
  • Information on any Successor Product/Feature (the recommended replacement).
  • Clear guidance on the recommended Migration Path to the new tool.

 

SUPPORT AND MIGRATION ASSISTANCE


We are committed to helping you with any transitions. We will provide resources to assist you in migrating to successor products or features, including:

  • Detailed documentation and step-by-step migration guides.
  • Access to our support team for guidance and assistance.
  • Options for professional services for more complex migrations (which may be subject to additional costs).

 

NEXT STEPS


This policy is now in effect. We encourage all customers to review the full policy document. We will keep you informed of any future product or feature retirements via the communication channels listed above.

If you have any questions about this policy, please reach out to your Customer Success Manager or contact the Oleeo Support team.

Thank you for your continued partnership.

Be the first to reply!