Sugar version 5.0/5.1 is a platform release with significant advancements in the product's core architecture and infrastructure. The new architecture provides enhanced performance, scalability, extensibility and overall product quality. As we continue to build new features for the 5.0 platform, SugarCRM will no longer be producing maintenance patches for earlier versions of our products.
Effective November 30, 2008, SugarCRM will no longer provide maintenance patches for versions prior to and including Sugar v.4.2.1. Effective February 28, 2009, SugarCRM will no longer provide maintenance patches for versions prior to and including Sugar v.4.5.0. If you are on an earlier version, we strongly encourage you to upgrade to the latest supported version. For those who remain on an unsupported version, only very critical security issues will be considered after the above dates.
The following sections outline SugarCRM's end-of-versioning (EOV) plan. Additionally we've included a short FAQ that provides answers to some common questions in this context.
What is the EOV plan?
We will be retiring Sugar product lines in a phased manner as shown below:
Sugar 4.2.1 - End of version effective from November 30 , 2008
Sugar 4.5.0 - End of version effective from February 28, 2009
Why should I upgrade to 5.0/5.1?
We have added many platform and functional improvements on the 5.0 platform. A few are listed below.
• Improved performance and scalability provide by the new metadata-driven model
• Advanced customization capabilities using Module Builder and Studio
• New AJAX based email client
• New customizable Homepage and Dashboards
• New Flash chart engine with Gauge and Funnel charts
• Scalable importing engine
What does End-of-Version mean?
End of Version means that SugarCRM will not be producing any further maintenance patches or bug fixes for an affected version, after the effective dates. SugarCRM's Customer Support can assist you with upgrading to the current version of Sugar.
What will happen to the add-on products and plug-ins?
All add-on's and plug-in's will also be impacted by this plan.
How does it impact me?
Community members who are using the affected versions will no longer be able to get fixes for the bugs that are reported. It is advised that user move to SugarCRM's most current version.
Please let us know what you think. For more details and feedback, please contact: email@example.com
SugarCRM Product Team