I'm not sure the best place to ask this but figure this is the likely place to start... My question is:
Would it make sense to "skip" EAP 6.0 and call the next release EAP 7.0?
I work for a company that does a lot of training and consulting for JBoss clients. One thing we have noticed is that a lot of clients that are willing to pay for our services are also the ones that pay for a JBoss EAP subscription. Truthfully this means that we have to balance between what is going on in the JBoss AS open source world with what is going on with JBoss EAP.
Lately I've been thinking a lot about how we will explain the versioning of some of the latest JBoss releases. I'm not looking forward to it. Right now if a client says "JBoss 6" that may mean very different things. If they mean "JBoss AS 6.0" I would probably reply "That's not the version you want to be using because the 7.0/7.1 version is much better". But if they mean "JBoss EAP 6.0" that is exactly not the thing I want to be saying to them as that will be the latest EAP version.
Also explaining that "JBoss EAP 6.0 is built on JBoss AS 7.1" is not a relationship I look forward to explaining. I'm sure I'm not the only one as there are probably developers out there who may be already trying to figure out how to explain it to managers.
I realized recently that all of us in this position might have a much easier time if the versioning for the EAP simply "skipped" a version. Certainly it might cause some initial confusion for JBoss to go from EAP 5.1 to EAP 7.0 and not have a 6.0 but I think this would be short lived.
Thinking from a product marketing perspective I would think having version numbers that are "off" between the two might also hurt the EAP. After all, who might want to pick a "previous" version (EAP 6.0) when there is a "later" version (JBoss AS 7.0/7.1) out there. I realize one is built on the other but again, not everyone is going to suffer through the explanation to understand that. Most people will just think of things as "JBoss 6", "JBoss 7", etc.
Just a thought I figured I'd throw out there. I figure now is the time to consider this instead of after JBoss AS 7.1 or EAP 6.0 is released.