On 23/11/2011 12:57, Stéphane Ducasse wrote: 
Hi guys

We are writing some articles on the work of veronica to support merging activities.  We need your input great smalltalk community :)
What are the questions that you ask yourselves when you are/want to merge some code in your project?
We would like to do a compilation of questions and also evaluate how the solution of veronica solves them or part of them.
At my job we have several programming rules hat we check on pieces of code before integrating.
Some of these checks could be automated, some cannot.

Besides, there is a more subtle analysis about two things: the alignment of the changes with the software design and politics; and a little cost-benefit considering added complexity as a cost (could yield negative when it is a refactoring, for instance) and additional functionality or enhancements or clarity or performance as benefits.
I don't think this could be automated, but it could be supported to some extent (we could measure the added complexity and raise hints about some design invariants).

I think this goes to the line that Sean T Allen pointed: why do we want to integrate these changes.

Regards
--
signature

carlos e. ferro | senior developer|  caesar systems | see clearly. decide smarter.

ceferro@caesarsystems.com | t: +1.281.598.8790 | t: +54.11.4389.0126 | blog.caesarsystems.com | www.caesarsystems.com 

This message and any attached documents contain information from Caesar Systems LLC that may be confidential/trade secret and/or privileged. If you are not the intended recipient, you may not read, copy, distribute or use this information. If you have received this transmission in error, please notify the sender immediately by telephone or by reply e-mail and then delete this message.