Confused about versioning

[camunda]

Hey guys,

I am bit confused at the moment: I thought the current jbpm 3.2.x development is QA for the "old" version and thus I expected it to be branched. Correct? This is because of some supported platform, right?

But why is the pom.xml in jbpm3 HEAD switched to version "3.2.6-SNAPSHOT"? Shouldn't HEAD currently point to 3.3.2-SNAPSHOT"?

Or did I miss anything?

Thanks
Bernd

[camunda]

Ah yeah: And jbpm 3.3.2.GA is still missing as version in JIRA...

[camunda]

Still more confused, seems all the jbpm 3.2.6 scommits go in jbpm3-HEAD? Can somebody shed some light on me?
Thanks...

[bradsdavis]

I think that 3.2.6 is the same as the 3.3.x branch, but without the jbpm console from 3.3 branch. The 3.3 console has GWT, and it is not supported in the 3.2 branch. So, they have taken patches for the 3.3 branch not related to the console, and also applied them to the 3.2 branch.

[tom.baeyens]

you're right brad.

33x is with gwt console
32x is without gwt console

32x productization is being finalized.

[camunda]

Is there information on this available anywhere? This is a important information for end users as well!

So any commits in the core should be targeted to the current 32x (in jira)? And they are automatically released as 33x as well?

So there is no distinction in the core itself? Confusing...

32x productization is being finalized.

Any Influences on this? What does this mean exactly?

[camunda]

Additional question: The SP release in jira is only for special service packs done by support? Or...?

Target releases for JIRA for me is the next GA?

[thomas.diesler]

Yes, everything you commit to trunk will go into the next jbpm-3.2.x release. There will be no further jbpm-3.3.x release anymore.

All additional features that went into jbpm-3.3.x have been taken out again in favour of upcoming jbpm4 releases. Specifically, you should see support for the GWT console in jbpm-4.0.0.Alpha2, which should come out on 1-Mar-2009.

Future jbpm-3.2.x releases must be strictly backward compatible in DB and API for former jbpm-3.2.x releases and will only contain bug fixes - and no new features.

Hope that clarifies it.

[mauromol]

Yes, everything you commit to trunk will go into the next jbpm-3.2.x release. There will be no further jbpm-3.3.x release anymore.

No further 3.3.x releases?!?!?!

We recently migrated our jBPM integration from 3.2.x to 3.3.x and now you say that you'll go to update just 3.2.x branch? Why?

What should we do now?

Mauro.

[kukeltje]

From what I know there is no functional and api difference between 3.2.x and 3.3.x, so you should be able to use 3.2.x from now on. The only difference was the console afaik....

[mauromol]

"kukeltje" wrote:
From what I know there is no functional and api difference between 3.2.x and 3.3.x, so you should be able to use 3.2.x from now on. The only difference was the console afaik....

Actually, these are the differences I could remember:
- the DB schema for 3.3.x has one more column in JBPM_NODE than that of 3.2.x (column PARENTLOCKMODE_)
- some methods were refactorized from 3.2.2 to 3.3.0: for instance org.jbpm.util.ClassLoaderUtil.getProcessClassLoader(ProcessDefinition) was moved to org.jbpm.JbpmConfiguration.getProcessClassLoader(ProcessDefinition)

Unless a "rollback" or a compatibility enhancement between 3.2.x and 3.3.x has been performed, it is not really true that there are no differences between the two branches except for the GWTConsole...

[mauromol]

Sorry for taking again this discussion, but I still need some clarification.

Given that the addition of PARENTLOCKMODE column mentioned in my previous message seems to have been reverted in 3.2.5.SP5 (as of https://jira.jboss.org/jira/browse/JBPM-2119), it's still not clear to me what should be the upgrade direction to follow.

I'm now using jBPM 3.3.0 GA and I see that a 3.3.1 GA is available.
But I see that a 3.2.6.SP1 is available too, and 3.2.6.SP1 is newer than 3.3.1 GA.

Now, I would need the fix for https://jira.jboss.org/jira/browse/JBPM-2036, which should be fixed in 3.2.6.SP1. Moreover, you suggest to upgrade from 3.3.1 to 3.2.6.SP1, which has to be considered the successor of 3.3.1.

From this I understand that I should upgrade from 3.3.0GA to 3.2.6.SP1.

However... what's next?

In JIRA, I see:
- a planned 3.3.2, "formerly known as 3.2.7", which I suppose should be the successor of 3.2.6.SP1?
- a planned 3.2.9, for which I can't understand the collocation

Given that I don't need the GWT console and that I would like to keep on the more recent version of jBPM 3, which upgrade path should I follow?

[kukeltje]

The 3.2.x path. 3.3 is resting in peace. The 3.3.2 has only two issues and those are only minor, so I'd not place my bet on them.

3.2.7 and 3.2.8 are silently released as part of the SOA platform afaik, so those are certainly the most up to date 3 releases. Getting 3.2.8 from source instead of 3.2.6SP1 would definitely be my bet.

Otoh, I'm not sure how easy it is to upgrade by 'downgrading'. Never tried that, not sure anybody has. The main thing I'd focus on would be DB compatibility

[kukeltje]

Oops, I see 3.3.2 has 2 OPEN issues on them and the other issues are related to issues that are also 'fixed' on 3.2.7 so maybe it is also or nearly as good as 3.3.2. Hopefully Tom or Alejandro can shed some light on this