Upgrade from 5.0 Beta or RC1 to General Availability

[chad.hutchins]

We have upgraded to Sugar 5.0 Beta in a test environment and it appears to have solved many of our user issues as well as added critical functionality (Module Builder) that we are in great need of. While testing in the environment we feel that 5.0 Beta 2 is stable enough to place it on our production system due to the added benefits.

I read a forum post today that states there will not be an upgrade from 5.0 Beta2 or RC1. Is this truly the case? If so how do we go about getting the functionality that is greatly needed prior to the Release for General Availability?

Also, is there a time frame for the actual General Available release?

Thanks,

[malcolmh]

Hi,

Beta versions and RC versions are for testing only, which is clearly indicated when installing.

Sugar has never had a upgrade path for these versions

[chad.hutchins]

Thanks for the reply!!!

That is completely understood. We are a software development company ourself so we understand the risks associated. My question is basically, how long will we have to wait for the Release of the GA version? Some of the items that are in SugarCRM 5 we needed yesterday.

[susiewilliams]

Hi there,

We are targeting the end of November for general availability of 5.0. We are posting the Release Candidate (RC) tomorrow (Saturday, November 10th).

[GameboyRMH]

So I take it transplanting a Sugar 5 beta/RC database into a Sugar 5 GA installation won't be possible?

[susiewilliams]

It won't be supported via upgrade scripts, nor will we recommend that you do it.

Whether you can actually do it or not is up to you and your skillset...

[taa145]

I am anxious to see the 5.0 GA version. Are we still on target for this week release?

[susiewilliams]

Yes. I'll post another message if I hear otherwise.

[RaySugar]

Hello - We are a new user getting ready to purchase on SugarCRM Onsite Professional. I see the note of caution about migrating from a non-release version to a production version. Does the same apply if we install 4.51 and then decide to upgrade to 5.0 when it is finally released?

We want to get started ASAP and prefer not to wait until 5.0 is actally released.

Forgive my ignorance here - I am fairly new to open source versioning. Thanks for any info you can provide.

[susiewilliams]

We do support upgrades from the latest production release (4.5.1) to 5.0, so you can get started with your implementation on 4.5.1 and then upgrade when 5.0 is released.

You can even do a "dry run" now to see what the effort will be, because the RC (release candidate) has an upgrade component to it.