I think bringing the large changes from the trunk via patches in the CMR style
is a non-starter, so I am glad that none of the options include this. So I am
for any of the options proposed.
I would just like the development branch (whether it be v1.5.X or v1.7) to be
released more often. The or
IMHO "B" will require a lot of attention from all developers/vendors, as well
it maybe quite time consuming task (btw, I think it is q couple of openib btl
changes that aren't on the list). So probably it will be good to ask all btl
(or other modules/features) maintainers directly.
Personally I
On Oct 27, 2010, at 9:14 AM, Jeff Squyres wrote:
> On Oct 26, 2010, at 5:52 PM, Barrett, Brian W wrote:
>
>>> B. Sync the trunk to the 1.5 branch en masse. Stabilize that and call it
>>> 1.5.2.
>>>
>>> Most people (including me) favored B. Rich was a little concerned that B
>>> spent too muc
On Oct 26, 2010, at 5:52 PM, Barrett, Brian W wrote:
>> B. Sync the trunk to the 1.5 branch en masse. Stabilize that and call it
>> 1.5.2.
>>
>> Most people (including me) favored B. Rich was a little concerned that B
>> spent too much time on maintenance/logistics when we could just be movi
On Oct 26, 2010, at 3:52 PM, Barrett, Brian W wrote:
> On Oct 26, 2010, at 3:07 PM, Jeff Squyres wrote:
>
>> There seem to be 3 obvious options about moving forward (all assume that we
>> do 1.5.1 as described above):
>>
>> A. End the 1.5 line (i.e., work towards transitioning it to 1.6), and
On Oct 26, 2010, at 3:07 PM, Jeff Squyres wrote:
> There seem to be 3 obvious options about moving forward (all assume that we
> do 1.5.1 as described above):
>
> A. End the 1.5 line (i.e., work towards transitioning it to 1.6), and then
> re-branch the trunk to be v1.7.
> B. Sync the trunk
On the teleconf today, two important topics were discussed about the 1.5.x
series:
-
1. I outlined my plan for a "small" 1.5.1 release. It is intended to fix a
small number of compilation and portability issues. Everyone seemed to think
that this was an ok idea. I have done some tomfool
