From: Brent Roman <brent@...>
Date: 2009-02-15T06:18:14+09:00
Subject: [ruby-core:22114] Re: A short memorandum (Re: 1.8.7 Specifics)


Charlie,

Much of the advantage I saw in moving 1.8.6 maintenance away from core
was to allow core to introduce new features and backports into the 1.8
series without
any fear that these might destabilize 1.8.6.

How can that work if the external maintainer of 1.8.6 is forced to take
every
patch core submits on the 1.8 branch?  

Would not a fork be appropriate?

If it did not fork, would the 1.8.6 maintainer be committing their changes
to HEAD,
possibility conflicting with core's work on 1.8.7+ or even 1.9?

I'm not a configuration management guru.
Am I missing something here?

- brent


Charles Oliver Nutter-2 wrote:
> 
> Brent Roman wrote:
>> There are some real advantages to using git to support external
>> collaboration, etc., but switching all of ruby-core over at once is a
>> non-starter.  I think this might be a good opportunity to ease into it.
> 
> The problem is that 1.8.6 is not supposed to accept commits that haven't 
> filtered down through other releases. See my other mail or Matz's 
> description of the process on ruby-talk:
> 
> http://groups.google.com/group/ruby-talk-google/msg/b37c751b88c08a67
> 
> So if every patch that comes into 1.8.6 has to go through SVN anyway, 
> what does the github repo gain us?
> 
> - Charlie
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-ruby-core%3A21997--1.8.7-Specifics-tp21961585p22017100.html
Sent from the ruby-core mailing list archive at Nabble.com.