11 Replies Latest reply on Jul 17, 2013 4:37 AM by henk de boer

    What is the difference between EAP and community of 6.1.0

    Gerry Deng Newbie

        

      Hi,  i found the JBoss EAP 6.1.0 can be downloaded on this community site. Does it mean there is no difference between EAP and community of 6.1.0?

        • 1. Re: What is the difference between EAP and community of 6.1.0
          Tomaz Cerar Master

          Hi,

           

          there is huge difference between community 6.1 and EAP 6.1

           

          EAP 6.1 is based on Community 7.2.0.Final.

           

          so in short releases went something like this

           

          community 6.1.0 --> 7.1.0 --> 7.0.1 --> 7.0.2 --> 7.1.0 --> 7.1.1 --> 7.2.0

          and from 7.1.x community ther was EAP 6.0

          and from 7.2.x there is EAP 6.1

           

          --

          tomaz

          • 2. Re: What is the difference between EAP and community of 6.1.0
            henk de boer Master

            Tomaz Cerar wrote:

             

            there is huge difference between community 6.1 and EAP 6.1

             

            EAP 6.1 is based on Community 7.2.0.Final.

             

            so in short releases went something like this

             

            community 6.1.0 --> 7.1.0 --> 7.0.1 --> 7.0.2 --> 7.1.0 --> 7.1.1 --> 7.2.0

            and from 7.1.x community ther was EAP 6.0

            and from 7.2.x there is EAP 6.1

             

            Why not have one version number and one name? Suffix the versions that are eligible for support with something (like Ubuntu does with LTS).

             

            I think that will be MUCH clearer to everyone. By using a totally different version number for something that's essentially the same thing you're (IMHO) only creating confusion.

            • 3. Re: What is the difference between EAP and community of 6.1.0
              Tomaz Cerar Master

              henk de boer wrote:

               

              Why not have one version number and one name? Suffix the versions that are eligible for support with something (like Ubuntu does with LTS).

               

              I think that will be MUCH clearer to everyone. By using a totally different version number for something that's essentially the same thing you're (IMHO) only creating confusion.

              I agree with you that this is confusing and to be fair I hope that now that jboss as was renamed to WildFly this confiusion will go away.

              From my point of view, when there is next major version of EAP it will be called JBoss EAP 7.0 and that will be based on some future version of WildFly, i say future version as I don't know which version will be selected for basis for next EAP.

               

              So in time, there will be only JBoss EAP releases that will still carry JBoss banner in name, and that should solve confiusion i hope.

              • 4. Re: What is the difference between EAP and community of 6.1.0
                henk de boer Master

                Tomaz Cerar wrote:

                 

                 

                So in time, there will be only JBoss EAP releases that will still carry JBoss banner in name, and that should solve confiusion i hope.

                 

                That's one way to look at it, and perhaps this will solve some of the confusion indeed.

                 

                Still, it maybe increases the illusion that it are really two different products. Commercially they might well be, but as developers we know this is not the case. Each EAP release is in reality just a specic AS release with extra testing and an amount of bugs fixed. In a continous numbering, JBoss EAP 6.0.0 would probably be JBoss AS 7.1.2.1, JBoss EAP 6.0.1 would be JBoss AS 7.1.3.1, JBoss EAP 6.1 would be JBoss AS 7.2.2 etc. Internal version numbers even seem to reflect that.

                 

                Using a Ubuntu LTS marking like thing, you could then indicate which version is supported by Red Hat. That marking could be e.g. RHS (Red Hat Supported). We would then get something like:

                 

                1. JBoss AS 7.1.0
                2. JBoss AS 7.1.1
                3. JBoss AS 7.1.2
                4. JBoss AS 7.1.2.1 RHS
                5. JBoss AS 7.1.3
                6. JBoss AS 7.1.3.1 RHS
                7. JBoss AS 7.2.0
                8. JBoss AS 7.2.1
                9. JBoss AS 7.2.2 RHS
                10. etc

                 

                With that scheme it would be directly clear at what point the EAP versions belong codewise, and anyone could also see at a glance that there are 3 supported versions and 6 unsupported ones.

                • 5. Re: What is the difference between EAP and community of 6.1.0
                  Gerry Deng Newbie

                  As I know JBoss community is free, but JBoss EAP is not, and we can download JBoss EAP here, does it mean we can use JBoss EAP 6.1.0 without any fee?

                  • 7. Re: What is the difference between EAP and community of 6.1.0
                    Gerry Deng Newbie

                    Thanks.

                     

                    I think this is the clear answer:

                     

                    The EAP binaries have their own release cycle. The EAP 6.1 release cycle had a Alpha, a Beta which ultimately led to the 6.1 GA.

                     

                     

                    The 6.1 Alpha binary is made available for free (both for development and production use) to the entire community. This allows community users who have been using the community server JBoss AS (now renamed to WildFly) a chance to get the bug fixes and possibly other features which had been added while the productization work was in progress.

                     

                     

                    The 6.1 Beta binary is made available under the zero-dollar developer subscription scheme (the terms and conditions are here http://www.jboss.org/developer-program/termsandconditions). This zero dollar subscription allows users to use the binray in development environments but not in production, unless of course the user additionally is also a paid subscriber/customer of EAP.

                     

                     

                    The 6.1 GA binary is available for production use only for paid subscribers/customers. Zero-dollar subscribers can use it only for development purposes. In other words, the usage terms are the same as 6.1 Beta binary.

                     

                    • 8. Re: What is the difference between EAP and community of 6.1.0
                      Tomaz Cerar Master

                      henk de boer wrote:

                       

                      Tomaz Cerar wrote:

                       

                       

                      So in time, there will be only JBoss EAP releases that will still carry JBoss banner in name, and that should solve confiusion i hope.

                       

                      That's one way to look at it, and perhaps this will solve some of the confusion indeed.

                       

                      Still, it maybe increases the illusion that it are really two different products. Commercially they might well be, but as developers we know this is not the case. Each EAP release is in reality just a specic AS release with extra testing and an amount of bugs fixed. In a continous numbering, JBoss EAP 6.0.0 would probably be JBoss AS 7.1.2.1, JBoss EAP 6.0.1 would be JBoss AS 7.1.3.1, JBoss EAP 6.1 would be JBoss AS 7.2.2 etc. Internal version numbers even seem to reflect that.

                       

                      Using a Ubuntu LTS marking like thing, you could then indicate which version is supported by Red Hat. That marking could be e.g. RHS (Red Hat Supported). We would then get something like:

                       

                      1. JBoss AS 7.1.0
                      2. JBoss AS 7.1.1
                      3. JBoss AS 7.1.2
                      4. JBoss AS 7.1.2.1 RHS
                      5. JBoss AS 7.1.3
                      6. JBoss AS 7.1.3.1 RHS
                      7. JBoss AS 7.2.0
                      8. JBoss AS 7.2.1
                      9. JBoss AS 7.2.2 RHS
                      10. etc

                       

                      With that scheme it would be directly clear at what point the EAP versions belong codewise, and anyone could also see at a glance that there are 3 supported versions and 6 unsupported ones.

                      Thing is that EAP is not just community version repacked. At least not after major release.

                      For instance 6.1 & 6.2 will have backported some features from WildFly 8/9.

                      This is the same as it always was, for instance with EAP 5.1, 5.2, 5.3 only EAP 5.0 was based on community 5.1.GA.

                      Only difference there is we did not publicly talk much about that.

                       

                      --

                      tomaz

                      • 9. Re: What is the difference between EAP and community of 6.1.0
                        henk de boer Master

                        Tomaz Cerar wrote:

                         

                        Thing is that EAP is not just community version repacked. At least not after major release.

                         

                        Of course, it's not just a repacking of the AS version it was branched from, but I personally just feel there's not necessarily a need for a completely different version number.

                         

                        Oracle's JDK 6 also contained some backported features from JDK 7, but it was just called Java 6 u10, Java 6 u11, etc.

                        • 10. Re: What is the difference between EAP and community of 6.1.0
                          Wolf-Dieter Fink Master

                          henk de boer schrieb:

                           

                          Of course, it's not just a repacking of the AS version it was branched from, but I personally just feel there's not necessarily a need for a completely different version number.

                           

                          Oracle's JDK 6 also contained some backported features from JDK 7, but it was just called Java 6 u10, Java 6 u11, etc.

                           

                          There is no complete different version number for that.

                           

                          JBoss AS - or now WildFly - is a open source project, you can use it for free and get help from the commuity. But there are no patches bugfixes - only the next version or github repository.

                          EAP is the "enterprise edition" - for customers which need a long term installation and by a subscription - with security updates, patches, maybe backports of small features and a longer timeline for support 

                           

                          I don't think about the numbers and I hope that the new name 'WildFly' will solve the confusion.

                          • 11. Re: What is the difference between EAP and community of 6.1.0
                            henk de boer Master

                            There is no complete different version number for that.

                             

                            JBoss AS - or now WildFly - is a open source project, [...]

                            EAP is the "enterprise edition" - [...]

                             

                            The way it feels to me (and that's of course my personal opinion only) is that it's simply a continuous stream of development for the exact same product. Specific versions are picked from this stream and branded as EAP and given a different version number to somehow create the illusion that it's a different product altogether.

                             

                            Commercially it's maybe a different product indeed, as the support options are totally different, but technically ("the binary bits" and the source code) it's exactly the same. Internally JBoss does keep using the continious version number. When you start up JBoss EAP 6.1 it says "7.1.3.Final-redhat-4 started".