Hi, This subject is quite interesting. I read that one of the main expected goal of integrating SCM and BT is to help release manager in its task. In my point of view, we have to keep in mind that it's not because a commit solved a problem, that all the following commits will always solve the problem. Development ALWAYS suffers regression. The really way to avoid this is to have an organisation of code that allows automatic tests. So it needs something greater than the SCM: you have to be organized for this. One interesting project to have a look for is aegis ( http://aegis.sourceforge.net/ ). It proposes a sort of SCM, that integrates process to ensure quality of code. One of them is that the /SCM/ will control the non regression before commiting. I hope these informations will help defining how we can design a system that integrates SCM and BT in a distributed manner. -- Guilhem BONNEFILLE -=- #UIN: 15146515 JID: guyou@xxxxxxxxxxxx MSN: guilhem_bonnefille@xxxxxxxxxxx -=- mailto:guilhem.bonnefille@xxxxxxxxx -=- http://nathguil.free.fr/ - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
