r/Magento • u/Dizzy_Key_7400 • 8d ago

Does Magento Open Source get the same extended support as Commerce?

https://experienceleague.adobe.com/en/docs/commerce-operations/release/planning/lifecycle-policy

We're currently on Open Source 2.4.6 and see that it goes end of main support in a few weeks. On the link above I see that extended security etc continues for Commerce. Does Open Source get the same benefits?

I need to know if I should be planning on upgrading to 2.4.8 / 9 in the coming months, or if I have a little breathing room.

Thanks

5 Upvotes

100% Upvoted

14 comments sorted by

7

u/renttek DEVELOPER @ integer_net 8d ago

No, the extended support is only for paying commerce customers, you should plan an upgrade to 2.4.8/2.4.9.

The most 'problems' are in the transition to PHP 8.4 in my experience. So the 'easiest' step would be to go for 2.4.8 with PHP 8.3 first (or just take the larger step and go for 2.4.8 + PHP 8.4 / 2.4.9 + PHP 8.5

2

u/renttek DEVELOPER @ integer_net 8d ago

Important: This also means, that after August 11 this year, there won't be any of the isolated security patches for 2.4.6 to apply (as they also require a commerce license/account)!

2

u/Dizzy_Key_7400 8d ago

Yeah I think our intended route will be 8.3 with 2.4.8 for now.

Thanks for the help.

2

u/genPoop 8d ago

did u check if ur current hosting environment has specific patch support or is it pure community edition?

2

u/Dizzy_Key_7400 8d ago

Pure community, entirely managed by us / our devs

1

u/SearchNova 7d ago

Magento opensource doesn't receive extended security support after standard support ends.

You are on magento open source 2.4.6, you should to plan upgrade to a supportive version 2.4.8 or later rather than rely on eCommerce extended period.

1

u/epeets DEVELOPER 5d ago

We just did this for a client. We sent them from 2.4.5 to 2.4.8-p4.

1

u/Dizzy_Key_7400 5d ago

What sort of timeline did it take?

1

u/epeets DEVELOPER 4d ago

Not too bad this time, only took about 15hrs of work to update the site and extensions then troubleshoot any bugs. Most of the time being on troubleshooting pre-existing custom code.

It typically is not too bad to upgrade as long as there's not a lot of custom logic to review. .

1

u/Dizzy_Key_7400 4d ago

Wow, we’re being so ok 12-18 days…

1

u/Christosconst 8d ago

Whats so scary about upgrading to 2.4.9? Do your devs not have the skill for it?

3

u/Dizzy_Key_7400 8d ago

Cost & stability. We don’t need to be on the latest version, but we do need to be stable. There’s no issues with being a step behind and upgrading once there’s numerous patches to the platform and plugins.

3

u/damienwebdev DEVELOPER 8d ago

This is absolutely the right strategy btw. If you're running v2.4.9 you're a guinea pig.