It was just a matter of time before JBoss was fully assimilated into Red Hat. Now, with the transition from JBoss' pure services/support model to Red Hat's Fedora/RHEL model, the acquisition is truly complete. The move would mean that JBoss would deliver a Fedora-like community edition of its core software that only looks forward. As with the Fedora Linux project, no backward compatibility is guaranteed—Fedora i It was just a matter of time before JBoss was fully assimilated into Red Hat. Now, with the transition from JBoss’ pure services/support model to Red Hat’s Fedora/RHEL model, the acquisition is truly complete. The move would mean that JBoss would deliver a Fedora-like community edition of its core software that only looks forward. As with the Fedora Linux project, no backward compatibility is guaranteed—Fedora is focused on the future and new features. Typically, a Fedora release is targeted as the next Red Hat Enterprise Linux release. RHEL forks or branches a specific Fedora release. The RHEL team stabilizes the Fedora code tree it branches, productizes it and certifies it for a number of different platforms.I think this is a highly positive move for Red Hat – it brings all of its products under the same release and business model, lowering costs and providing for a cleaner story to the market. By focusing JBoss Community (or whatever it will be called – it will be interesting to see if Red Hat creates an entirely separate brand for it, as with Fedora) on the cutting edge and not worrying about backward compatibility, Red Hat delivers a strong development platform without eating into potential revenues that will follow the tried-and-true, productized version. Very smart. Open Source