[Project-managers] BSP 2009 and changes to project management procedures

[Stefan Vigerske]

Hi,

>> On thinking it over, I can see problems with trunk projects pointing to
>> releases.  The main problem would be Osi.
>>
>> Suppose I make an improvement to Clp which I want to be available in Cbc.
>> I can make a release of Clp if I want to, but there may have to be changes
>> to OsiClp.  This would mean a new release of Osi which might not be
>> convenient as Osi has so many solvers.
> 
> Actually, that's the whole idea :-). This way improvements get 
> released more frequently. But what you suggest is a valid concern... 
> How about splitting up Osi in the sense that each solver can be 
> released separately? We are creating separate libraries from the 
> solverinterfaces anyway... And the same problem applies to cgl as 
> well...

I would support the idea to put OsiClp into Clp.
Not making Osi a requirement for Clp, but if Osi is available during the
Clp build, then also an OsiClp library should be build.
Similar, OsiDylp could move to Dylp, OsiSymphony to Symphony, ...
And for the Osi interfaces to solvers that are not in COIN-OR (yet ;-)),
the OsiXXX might either go into a separate place (as Laci suggested) or
just stay in Osi for now.

For Clp+OsiClp, I see the main advantage that it is much easier for John
to do this coupled development. Further, OsiClp is not much useful
without Clp anyway.

Best,
Stefan