I'm trying to understand how the concept of release bindings apply to ARC cases for Free/Open Source Software(specifically Ruby/Rails). The "release-taxonomy" page[1] on OpenSolaris.org seems, to my ARC-novice eyes, targeted at Software that is released by Sun since it's inception, rather than F/OSS projects that we're including in Solaris at a later stage in the project's life.
The inclusion of RubyOnRails should be a major release based on section 4.1, since it " . . . introduces or changes significant software functionality . . ." into Solaris. Yet it's not a major release because, (1) It's not a X.0.0 release for the F/OSS projects that are being proposed. (2) It fits better into the X.Y.A model that's specified in section 4.3. I'm gravitating toward the X.Y.A model, which maps to a micro release binding for the Ruby/Rails case. Even though we're introducing significant software functionality, it's not a major release for the software we're including. Ruby, Rails, and dependencies are well used pieces of software. Thanks, -ps [1] http://www.opensolaris.org/os/community/arc/policies/release-taxonomy/ -- Prashant Srinivasan F/OSS Enthusiast Sun Microsystems, Inc. http://blogs.sun.com/prashant GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x82FBDE5A
