We’ve been waiting for Nuxeoworld to get the scoop on the Nuxeo v5.8 release. Today, CEO Eric Barroca confirmed that the upgrade will be available by the end of this month, and that there are some substantial upgrades under the hood.

It’s been a busy couple of months for Nuxeo, which in September managed to secure funding of US$ 3.8 million to continue its expansion in the US where, it says, more than 50% of its new subscriptions are being signed up.

What's Key in Nuxeo 5.8

During Nuxeoworld, which is currently underway in Paris, we spoke to CEO Eric Barroca, who explained the thinking behind Nuxeo v5.8. The first thing to say is that there has been extensive work done already with many of the new features appearing in the fast track releases over the last few months.

However, v5.8 will pull all those together, resulting in over 1100 tasks completed, 65,000 builds, and 35,000 tests on commits. Given that much of what will be released in v5.8 is for developers, that’s hardly a surprise.

But there are three principal areas of development:

1. Enhancements to the REST API: In keeping with the 5.7.3 release that was launched at the end of September, the new Nuxeo REST API provides several new endpoints for documents, users and groups, on top of the access to document resources that was introduced in the v5.7.2 version.

The expansion of the REST APIs corresponds with a move to make remote access to the Nuxeo content repository easier.

However, according to Barroca, the real bonus in the v5.8 release is that developers will be able to use it without any framework. It also lets users integrate with other Nuxeo applications using simple HTTP in the JSON format.

2. Workflow engines: This is the second big enhancement. Barroca says Nuxeo has developed new features around escalation rules and dashboards, as well as support for sub-processes, and a new task resolution screen. This is also in keeping with the v5.7.3 release, which enabled users to create a task per assignee while the workflow

3. Operations: A new set of metrics services.

Release Cycles Improve Support

Barroca has also confirmed that Nuxeo will continue the two different release cycles in the form a fast-release cycle that will take place every two months or so, and a slower, long term cycle that will incorporate the new improvements into a point upgrade.

This means that the last release of a tri-release cycle -- will be the long-term release. Explaining why it introduced fast-tracking, Barroca says that it offered users the chance to use new features in a stable environment without having to wait for the long-term release.

It also means that Nuxeo is able to control what products their customer base is using. He points out that in the past Nuxeo found that its customers were often using different product versions, which was difficult to control.

This way, he says, everyone is working from the same product, which ultimately improves the support that Nuxeo is able to offer its clients.

v6.0 or 5.10?

For the future then, Barroca says Nuxeo have yet to decide whether it will be moving to v5.10, or whether it will make the full jump to v6.0, but one way or the other it will be a full year before this happens.

Nuxeo is already planning for the next release, and while there are no precise plans as yet Barroca says it will focus on mobility and synchronization etiquette which governs the way you sync between Nuxeo server and mobile devices.

Nuxeo is also working on making the UI easier to use in the next version with the introduction of new features to support collaboration and synchronous editing.

In relation to the US$3.8 million funding that Nuxeo managed to raise in September, he says that the company’s stateside focus is driven by the fact that more than half of its new business is there. The plans for expansion are underlined by the fact that it now has a management team in New York.

That said, with its roots in Paris, it also has plans to continue its expansion in Europe with a new office in the pipeline in the middle of 2014. More from Nuxeoworld later.