On Dec 12, 2012, at 11:17 AM, Roy Stogner <royst...@ices.utexas.edu> wrote:

> 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.

My only urgency is that we have some minimal documentation & discussion to 
guide us - not that we define some Byzantine process with which to intimidate 
strangers and ridicule friends.  What was supposed to be a very deliberate move 
was hastened by the Allura svn import fiasco, so I feel a little guilty about 
pushing this faster than I intended. 

>> 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.

Understood, so then for the foreseeable future 'master' will continue to be at 
least my sandbox (to the same extent trunk was as of last week) - which seemed 
to be maybe what sparked the best practices discussion in the first place?

-Ben
------------------------------------------------------------------------------
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

Reply via email to