On Wed, 12 Dec 2012, Derek Gaston wrote:
> I am not against this model... (it is VERY close to how we do things > with MOOSE... and our "stable merge" is automated by Bitten) > however, can we have a small "cooling off" period for a moment while > everyone gets up to date with using the new build system and pulling > from Git? I think John already made this point, and I didn't respond then, but I agree completely. I'm still figuring out the subtle differences between "git pull" and "svn update" and I have no desire to jump ahead to more sophisticated development workflows this month, despite my excitement when talking about it. > At the very least, I don't think we should move to a separate branch > from master with "stable merging" until we have a public BuildBot up > and running that is tracking libMesh development. The PECOS CI server actually is publicly accessible. It's so hammered right now that I'd rather not subject its interface to even more usage until we get some new hardware going, but email me privately if you want the URL to peek at occasionally. --- Roy ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
