Release cycle and tools

[talex1]

Since there is no relevant category in the forum, I am posting my questions to this category. Sorry for this.

I have 2 questions.

• Release cycle for Activiti is 1 month. But release 5.7 last 2,5 months. What is the reason for this latency? What is the time period for future releases?


• In the release notes it is stated that Modeler, Cycle and KickStart will live as separate projects. Why are they separated?

I'm not criticizing you. We are using Activiti in an enterprise application. I'm just trying to minimize uncertainty.

Thanks in advance

[jbarrez]

Good question.

The Cycle and Modeler tools have always been developed by another team (ie not the core team working for Alfresco).
The Activiti core team decided to separate these tools, as we also didnt have much control over it (bugs, features, etc.).
This way, we focus on what we are good at: the best embeddable BPMN and workflow engine.

This explains the difference in release cycle. The Cycle and Modeler will still evolve, but on a different pace than the engine.

KickStart is another story: I wrote it a while back as a prototype. It isnt the direction we want to go in with the Activiti product.
The code will be moved to github shortly (I have the blog ready), so people who are interested can still find it there,and hopefully I will be able to spend some free time on it.

[bernd_ruecker]

Hi talex.

We are currently working on the next release of Cycle working together with the Signavio Modeler (see http://www.camunda.com/fox/components/cycle/ for details), stay tuned, we plan to release it in September… As camunda fox stack we provide a bundled stack with Signavio, Cycle and Activiti as well…

Cheers
Bernd