Status of the Openbravo ERP 2.35 Upgraders

One of the issues that in recent weeks has been troubling our Community the most is the status of the 2.35 Upgraders, so I feel it is appropriate for me to write a public explanation of what is going on.

For those not familiar with it, the problem is that we have published upgrade scripts (Upgraders) to our Community from 2.35 to 2.35 MP1 and from 2.35 MP5 to 2.40 beta; we haven't however published Upgraders from 2.35 MP1 to 2.35 MP4 nor from 2.35 MP4 to 2.35 MP5.
Effectively, this makes it very difficult for users on 2.35 MP1 to upgrade to 2.40.

We have a stated policy to publish an upgrade script within 2 weeks from the publication of a new release or maintenance pack. Yet, three and half months after the publication of 2.35 MP4, no Upgrader is yet available for it.

First of all, I would like to apologize for this delay and confirm that we do intend to publish these Upgraders; this issue is not the result of a policy change. In fact, we have been working very hard to complete them, but unfortunately we seem to keep running into technical issues that prevent their publication.

As of now, both Upgraders are available to our QA team who is verifying them against various configurations. If everything goes well, we hope to finally publish them before the end of the week. History, however, shows that it is very difficult to predict an exact completion date as any new issue might cause a few days of delay.

Given the importance of the Upgraders to our users, we intend to provide our Community with complete visibility into our progress. For that purpose, we have created a status page on our Wiki which we will update on a frequent basis with progress and any schedule change.

Going forward, we intend to publish the Upgrader concurrently with the publication of a new release. This way existing users will be able to immediately test the new version. We followed this approach already with 2.40beta (this is the reason why the 2.35MP5 to 2.40beta upgrader is already published) and we aim at continuing with this practice for all future releases.