[M3devel] slight hudson/opencsw oddity

Jay K jay.krell at cornell.edu
Mon Nov 8 11:11:38 CET 2010


> > The important thing is that cm3 and cm3cg need to be updated together.
> > They must always be taken as a matched pair.
> > You may never mix and match.
> >    Well, max/match *usually* works. But the way to allow interface changes
> >     is to not do that. But those changes are rare...
> 
> Our current separation of Hudson jobs for m3cc and cm3 will only work
> if we start with m3cc _and_ the new cm3cg can be used by the _old_
> cm3 front-end. If we expect more incompatible changes related to the


Hm. Well, it was good to discover this, eventually.
It is fine to split the tasks. You can build stuff in whatever order.
But the updated files should only be used/copied at the right times/combinations.
It shouldn't be difficult.

 - Jay
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20101108/1c174af9/attachment-0002.html>


More information about the M3devel mailing list