Thomas E Enebo wrote:
I would like to keep putting out 1.1.x until we encounter something which changes existing semantics. I don't consider 1.8.7 as a big change. All the stuff in 1.2 can be in point releases of 1.1.x. Actually additions to 2.0 (rubinius/1.9) can also be done during point releases of 1.1.
Tom hates branches. I do not, but I recognize they're cumbersome. "Innovation" on the 1.0 line stopped the minute that branch was created, and while I think that was probably the right thing to do to stabilize 1.0, 1.1 is already in far better shape and we're not likely to do serious damage in the short term. So I think continuing to develop off trunk can work for a while.
I also agree that we can keep even larger additions in trunk and pull off dot releases where those features are present but perhaps not supported. Adding is easy to do without breaking a lot of stuff.
The key to whether we should finally pull off a branch would be when we reach the point we need to rewrite some major part of the system in a user-visible way. Java integration would do that, and obviously anything relating to lightweights would as well.
The reason to make a major release will be when we tackle and reboot Java Integration. So I think that is a driving force for 2.0 (of whatever we call it).
Yes, whatever we call it :) Maybe "JRoovy"! - Charlie --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
