[Project-managers] New CoinUtils release

[Ted Ralphs]

Hmm, this is true for the codes themselves, but you might up end with 
incompatible configure scripts, i.e., the configure script in CoinUtils 
was generated with version 0.5.2, while the configure script in Clp was 
generated with 0.5.1. As I understand it, this can cause problems and is 
precisely why Andreas wanted to upgrade all the stable releases at the 
same time. Andreas, can weigh in and say for sure?

Cheers,

Ted

Laszlo Ladanyi wrote:
> Actually, this is not quite true. As long as only the tiny version changes    
> (meaning that only bugfixes and minor changes happened, but nothing that would
> change either the interface or the expected behavior of a method) you can go  
> ahead and switch to the new one. And then, when SYMPHONY is checked out, Clp  
> and the rest will use the new version of CoinUtils, because that's SYMPHONY's
> external. Of course, you should test that it works, but in theory it should.
> 
> --Laci
> 
> PS: It's release 1.0.2 now... a small change was left out...
> 
> On Wed, 25 Oct 2006, Ted Ralphs wrote:
> 
> 
>>Don't forget, this has to be done in sequence, since we have the same 
>>dependency problem with releases that we had with stable versions. I 
>>cannot make a new release for my projects until every project that I 
>>depend on (and that subsequently also depends on CoinUtils) has made a 
>>new release. Therefore, it would be very helpful if project managers of 
>>projects that others depend on (Clp, Osi, Cgl, CoinUtils) would announce 
>>when they have made a new release and what version of BuildTools it 
>>depends on.
>>
>>Cheers,
>>
>>Ted
>>
>>Andreas Waechter wrote:
>>
>>>Hi all,
>>>
>>>Just a clarification:
>>>
>>>
>>>>This message is for those whose project uses CoinUtils.
>>>>
>>>>The latest release of CoinUtils is 1.0.1. It relies on BuildTools 0.5.2.
>>>>Please, update your stable/release branches when you have some time. 
>>>>Don't
>>>>forget to do *both* CoinUtils and BuildTools, otherwise it'll crash and
>>>>burn...
>>>
>>>In your stable branch, your externals should point to the stable 
>>>branches of the dependencies, including that of CoinUtils.  If you do 
>>>this, you will not have to change anything when a new release of 
>>>CoinUtils of BuildTools happens, since the latest stable version is 
>>>automatically pulled in.  (That might be the easiest solution, but you 
>>>can of course handle this differently and point at specific releases if 
>>>you feel like you want to keep updating externals a lot.)
>>>
>>>As for releases, Laci's message didn't ask you to update any EXISTING 
>>>release. (Remember, RELEASES MUST NEVER BE CHANGED ONCE THEY HAVE BEEN 
>>>CREATED!)  It is rather that you would need to make a NEW release 
>>>(following the instruction at 
>>>https://projects.coin-or.org/BuildTools/wiki/pm-svn-externals#PreparingExternalsForAPointRelease) 
>>>for your project if you want to take into account the latest release of 
>>>CoinUtils with the bug fixes etc.
>>>
>>>Regards,
>>>
>>>Andreas
>>>_______________________________________________
>>>Project-managers mailing list
>>>Project-managers at list.coin-or.org
>>>http://list.coin-or.org/mailman/listinfo/project-managers
>>
>>
>>-- 
>>Dr. Ted Ralphs
>>Associate Professor
>>Industrial and Systems Engineering
>>Lehigh University
>>(610)758-4784
>>tkralphs at lehigh.edu
>>www.lehigh.edu/~tkr2
>>
> 
> 
> _______________________________________________
> Project-managers mailing list
> Project-managers at list.coin-or.org
> http://list.coin-or.org/mailman/listinfo/project-managers


-- 
Dr. Ted Ralphs
Associate Professor
Industrial and Systems Engineering
Lehigh University
(610)758-4784
tkralphs at lehigh.edu
www.lehigh.edu/~tkr2