Hi...I love what you are doing in Hudson, but the Cog part it is quite a mess right now. I would love to see some organization. <br><br>1) Not all VMs have both: the build and the sources. Example, <a href="https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Cocoa/">https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Cocoa/</a> has only the sources. But <a href="https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Carbon/">https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog%20Mac%20Carbon/</a><br>
has both. If someone follows this: <a href="http://code.google.com/p/cog/wiki/CMakeVMMaker">http://code.google.com/p/cog/wiki/CMakeVMMaker</a><br>then such info is incorrect.<br><br>2) We are mixing "Release" VMs from experiments. I would create two Hudson tabs<br>
2.1) one for Cog, where we have the "release" VMs. This means, things like Cog Mac Carbon, Cog Mac Cocoa, Cog Unix, CogMT Mac Cocoa, MT Cog Unix, Stack VM Unix, StackVM Mac Carbon, StackVM Mac Cocoa, etc. <br clear="all">
<br> 2.2) One for experiments, like: Check <a href="http://cogvm.unthinkable.org">cogvm.unthinkable.org</a>, Cog Git Tracker (cog-osx), Cog Git Tracker (sig-cog), Cog.FreeBSD.unthinkable,Sista<br><br>Only if we do that, we will be able to use Hudson like a place to say to users to download a VM. Otherwise, we cannot. There are several targets and they are confusing. <br>
<br>Cheers<br><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>