<html><body>
<p>Ted,<br>
<br>
On thinking it over, I can see problems with trunk projects pointing to releases. The main problem would be Osi.<br>
<br>
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.<br>
<br>
Does anyone else see this as a problem? I suppose I could keep a trunk and a branch?<br>
<br>
John<br>
<br>
<img width="16" height="16" src="cid:1__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt="Inactive hide details for Ted Ralphs ---06/30/2009 05:38:03 PM---Hi folks,"><font color="#424282">Ted Ralphs ---06/30/2009 05:38:03 PM---Hi folks,</font><br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">From:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">Ted Ralphs <ted@lehigh.edu></font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">To:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">project-managers <project-managers@list.coin-or.org></font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Date:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">06/30/2009 05:38 PM</font></td></tr>
<tr valign="top"><td width="1%"><img width="96" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2" color="#5F5F5F">Subject:</font></td><td width="100%"><img width="1" height="1" src="cid:2__=0ABBFF7BDFA487328f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">[Project-managers] BSP 2009 and changes to project management procedures</font></td></tr>
</table>
<hr width="100%" size="2" align="left" noshade style="color:#8091A5; "><br>
<br>
<br>
<font size="4">Hi folks,<br>
<br>
This e-mail is to (1) announce the 2009 </font><a href="https://projects.coin-or.org/CoinTLC/wiki/BugSquashingParty09"><u><font size="4" color="#0000FF">Bug Squashing Party</font></u></a><font size="4"> and (2) make you aware of important impending changes in the TLC's recommended project management procedures. I apologize for the lengthy explanation, but there is a lot to tell! <br>
<br>
1. The third annual </font><a href="https://projects.coin-or.org/CoinTLC/wiki/BugSquashingParty09"><u><font size="4" color="#0000FF">Bug Squashing Party</font></u></a><font size="4"> is scheduled to take place July 7-8. For those who are not familiar with this event, it is an annual on-line event in which volunteers gather in a virtual chat room to fix as many small bugs, compiler warnings, portability issues, memory leaks, etc. as possible in COIN projects. By gathering volunteers with access to a wide range of platforms and compilers, we have been able in the past to accomplish a lot in a short period of time. The procedure involves creating a temporary copy of the most recent stable branch of various projects, fixing the bugs in that copy and then merging the changes (at the PMs discretion) back into the stable branch and/or trunk, as appropriate. More information is available at the </font><a href="https://projects.coin-or.org/CoinTLC/wiki/BugSquashingParty09"><u><font size="4" color="#0000FF">Bug Squashing Party</font></u></a><font size="4"> wiki.<br>
<br>
PLEASE LET US KNOW IF YOU<br>
<br>
-- WANT TO HELP WITH THE EVENT YOURSELF<br>
-- DO OR DO *NOT* WANT BUGS TO BE FIXED IN YOUR PROJECT<br>
<br>
By default, all projects using the BuildTools will be included.<br>
<br>
2. As part of a multi-faceted, long-term effort to improve the usability of all COIN projects and ease the overall maintenance burden, we will be announcing over the next several months a number of changes to the recommended project management procedures for COIN projects. The first of these will be a recommendation to begin developing project trunks against release versions of other projects. There are many reasons for this and we will be providing a full explanation in the near future. In short, however, we would like to decouple development of independent COIN projects as much as possible in order to (1) reduce the impact of individual projects' release cycles on other projects, (2) ease the complexity of dependencies and make simultaneously installation of multiple projects easier on end users and (3) ultimately make it possible to support the development of a package management system that would enable easy installation and upgrade of COIN binary packages over time. At the moment, our procedures tend to couple the development of many of the projects and actually make the release cycle much slower. Our current handling of dependencies is also not very compatible with the maintenance RPMs for COIN, etc. You will here more about this over time.<br>
<br>
PLEASE LET US KNOW IF YOU<br>
<br>
-- WOULD LIKE US TO SWITCH THE EXTERNALS OF YOUR PROJECT'S TRUNK TO POINT TO RELEASES OF DEPENDENT PROJECTS AND TEST IT DURING THE BSP.<br>
-- PLAN ON DOING THIS YOURSELF.<br>
<br>
Of course, this is a completely voluntary step, but we are strongly encouraging it. Please let me know if you have any questions about any of this. Thanks for your support!<br>
<br>
Cheers,<br>
<br>
Ted<br>
-- <br>
Dr. Ted Ralphs<br>
Associate Professor, Lehigh University<br>
(610) 628-1280<br>
ted 'at' lehigh 'dot' edu</font><u><font size="4" color="#0000FF"><br>
</font></u><a href="http://coral.ie.lehigh.edu/~ted"><u><font size="4" color="#0000FF">coral.ie.lehigh.edu/~ted</font></u></a><font size="4"><br>
<br>
</font><tt>_______________________________________________<br>
Project-managers mailing list<br>
Project-managers@list.coin-or.org<br>
</tt><tt><a href="http://list.coin-or.org/mailman/listinfo/project-managers">http://list.coin-or.org/mailman/listinfo/project-managers</a></tt><tt><br>
</tt><br>
<br>
</body></html>