Changing Update Cycles and Maintenance Releases

OXID Announcements
1

Hi everybody,

starting with the release of version 4.6.0 we will introduce some changes in the OXID eShop update cycles. We will also expand our maintenance activities for previous versions of OXID eShop. Please read more in this related blog post by Erik:
http://www.oxid-esales.com/en/news/blog/oxid-eshop-update-cycles-and-maintenance-releases

Regards

2

Hi Marco,

great news, i really like the idea to give support to the previous version of the shop. This makes live more easy.

When do you think we can get more information about the Oxid 5.0 ?

cya

3

Hi,

[QUOTE=Firefax;87324]
great news, i really like the idea to give support to the previous version of the shop. This makes live more easy.[/QUOTE]

That’s the aim :slight_smile:
When do you think we can set your feature request to “completed”?

Maybe we should also talk about the status other one, at least to get the voices back:

[QUOTE=Firefax;87324]When do you think we can get more information about the Oxid 5.0 ?[/QUOTE]
As soon as we start working on it. Let us finish 4.6.0 before :wink:

Regards

4

Hi Marco,

[QUOTE=Marco Steinhaeuser;87614]Hi
When do you think we can set your feature request to “completed”?
http://oxid.uservoice.com/forums/31940-feature-requests/suggestions/957983-make-a-oxid-version-with-long-term-support-lts-
[/quote]
i think you can close this feature request, my needs and intentions with this feature request are included in this new maintainance cycle. This will take speed out of the update race and helps everyone who dont want to follow every update immediatly (e.g. with a highly customised shop)

Maybe we should also talk about the status other one, at least to get the voices back:
http://oxid.uservoice.com/forums/31940-feature-requests/suggestions/957995-fix-only-bugs-no-new-awesome-features

In my opinion, you should never close this feature request. The (blocked) voices are also a good rememberance for oxid to keep the effort high and to do a good job. That this feature request reached the 2nd places shows how important this topic is to the users.

Maybe i come to the commons, so we can have a talk about it. I really like to offer you a bet about resolved bugs and the upcoming 4.6 final. :wink:

cya