JBoss 7.2.0.Final --> JBoss 6.1.0.Alpha

[suikast42]

Hi Guys,

I'm a little bit confused about the new version strategy of JBoss. Why is the opensource branch marked as final and the eap branch as final ?

Can I assume that 7.2.0.Final is stable for production or not?

I see that the versions for hibernate and infinispan for example are x.x.x.CR1. So I assume that can't be a Final of JBoss.

[jaikiran]

https://community.jboss.org/blogs/mark.little/2013/03/07/eap-binaries-available-for-all-developers

http://www.jboss.org/jbossas/faq

[suikast42]

Hi Jaikiran,

thanks for fast response.

The startup logging of 7.2.0.Final says:

11:23:55,674 INFO  [org.jboss.as] JBAS015899: JBoss EAP 6.1.0.Alpha1 (AS 7.2.0.Alpha1-redhat-4) starting

Is the version of opensource branch 7.2.0.Alpha1 or Final ??

[nickarls]

There is a tag for 7.2.0.Final in github so you can build it yourself but it's the same as the EAP 6.1.0.Alpha1 (and the tag id appears to be the same as the prerelease1 for 7.2.0)

[suikast42]

Hi Niklas,

I know that I can build the tags from github. At the past we use jboss "Opensource Finals" for our production environment. The question is about the stability ? The 7.2.0.Final --> EAP 6.1.0.Alpha1 is for my word not stable.

For hibernate and infinispan for example 7.2.0.Final Candiate releses. Thats a force of redhat to use EAP, isn't it ??

[nickarls]

They can't force me to do anything! (only my wife can do that)

The code would be the same regardless on what the release would be called.

Having said that, I don't think it's an accident that the Alpha1 label has been stuck on the community relase.

Apparenlty RC:s are allowed on a case-to-case basis.

[suikast42]

They can't force me to do anything! (only my wife can do that)

I have the same problem .

So let's wait and drink some cofee .

[openlogic_support]

Here is a helpful link that discusses why Jboss did what they did, by the support and legal team at Open Logic.

http://www.openlogic.com/blog/bid/283299/Where-is-JBoss-7-2-0-Final