I think I've had too much coffee this afternoon... let's try that last
email again... this time in English:
Sorry for one more email on this topic... but if you want to see how we
track libMesh revisions look at our repo: https://github.com/idaholab/moose
See that libMesh directory? Notice how it has a Git hash right next to it?
We're using Git Submodules... and that hash is the current version of
libMesh that we're using (ie that our customers are receiving)
automatically just by cloning our repo and running "git submodule init; git
submodule update" (they actually run a small script in our repo that does
that for them).
In this way - all we need to do is update the hash of the version of
libMesh we're using and all of our customers get the new revision of
libMesh automatically when they update their version of our software (and
after running "git submodule update"... again through a script).
Nice and tidy - and no waiting on libMesh releases.
On Fri, May 9, 2014 at 4:55 PM, Derek Gaston <fried...@gmail.com> wrote:
> Sorry for one more email on this topic... but if you want to see how we
> track libMesh revisions look at our repo:
> https://github.com/idaholab/moose
>
> See that libMesh directory? Notice how it has a Git has right next to it?
> We're using Git Submodules... and that hash the the current version of
> libMesh that we're using (ie that our customers are receiving)
> automatically just by checkout out our repo and running "git submodule
> init; git submodule update" (they actually run a small script in our repo
> that does that for them).
>
> In this way - all we need to do is update the hash of the version of
> libMesh we're using and all of our customers get the new revisions of
> libMesh automatically when they update their version of our software (and
> after running "git submodule update").
>
> Nice and tidy - and no waiting on libMesh releases.
>
> Derek
>
>
>
> On Fri, May 9, 2014 at 4:51 PM, Derek Gaston <fried...@gmail.com> wrote:
>
>> To be clear: we update libMesh about monthly... each time just updating
>> to HEAD in the Git repo...
>>
>> Derek
>>
>>
>> On Fri, May 9, 2014 at 4:50 PM, Derek Gaston <fried...@gmail.com> wrote:
>>
>>> Michael - can you really not use the Git version? A libMesh "release"
>>> really isn't much more special than any version in the Git repo... in fact
>>> all it means is that it's usually behind on bug fixes....
>>>
>>> We've never used a "release" and we distribute libMesh to hundreds of
>>> customers daily without issue. Each time we update to a new version of
>>> libMesh we simply run all of our tests and verify that everything is still
>>> working well (which is actually something we do all day anyway because our
>>> developers all use the latest GitHub version of libMesh for development)
>>> and then push it out the door to our users.
>>>
>>> Derek
>>>
>>>
>>>
>>> On Fri, May 9, 2014 at 3:14 PM, John Peterson <jwpeter...@gmail.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Fri, May 9, 2014 at 2:23 PM, Roy Stogner
>>>> <royst...@ices.utexas.edu>wrote:
>>>>
>>>> bugfix release for a regression this big. I'm swamped right now, but
>>>>> I'll try to get an 0.9.3.1 out next week. Any other fixes worth
>>>>> backporting while I'm at it?
>>>>>
>>>>
>>>> I'm not sure how crazy you want to get with backporting bugfixes, but I
>>>> looked through the logs and came up with a few candidates...
>>>>
>>>> 8901bce4 fixes a previous fix to our libtool script, but only affects
>>>> specific MPI/Fortran compiler combinations
>>>> 69cc60ee looks like a bugfix for the MeshfreeInterpolation stuff
>>>> f108b893 fixed a bug in plotting discontinuous solutions in Exodus
>>>> ac4b3b9d local_variable_indices bugfix
>>>> 700f26fb fix for --disable-amr
>>>> bec6e6da fixed bug in SerialMesh::stitching_helper
>>>> e33b68ae fix for Solaris Studio
>>>>
>>>> --
>>>> John
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Is your legacy SCM system holding you back? Join Perforce May 7 to find
>>>> out:
>>>> • 3 signs your SCM is hindering your productivity
>>>> • Requirements for releasing software faster
>>>> • Expert tips and advice for migrating your SCM now
>>>> http://p.sf.net/sfu/perforce
>>>> _______________________________________________
>>>> Libmesh-devel mailing list
>>>> Libmesh-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/libmesh-devel
>>>>
>>>>
>>>
>>
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
