4 Aug
2016
4 Aug
'16
2:33 a.m.
Thanks Peter for fixing this!
And yes I am aware that I am on a development branch so some instability can happen and
functionality can change. So I am OK with that. That being said, committers should ensure
that all tests always pass. Situations like this cause time to be wasted and are bad
publicity for Roassal.
--
Does this mail seem too brief? Sorry for that, I don’t mean to be rude! Please see
http://emailcharter.org .
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile
On Aug 3, 2016, at 14:27, Peter Uhnak
<i.uhnak(a)gmail.com> wrote:
On Wed, Aug 03, 2016 at 01:49:30PM -0400, Johan Fabry wrote:
latest version
This is the core of the issue.
We can either use #bleedingEdge and slit our wrists with it from time to time (because
there are no guarantees), or change ConfigurationOf after every single functional change
(so you commit your changes, see the build to pass, then you go back and edit the code
again).
(Or use git, but people apparently like the approach above.)
Peter
_______________________________________________
Moose-dev mailing list
Moose-dev(a)list.inf.unibe.ch
https://www.list.inf.unibe.ch/listinfo/moose-dev