[MOAB-dev] Backporting to version 4.5

[Steve Jackson]

Philosophy question: shouldn't the tags/4.5 tag code be permanent and fixed, with all fixes created in trunk and released periodically (and tagged) as 4.5.X?  I think that would be more in keeping with subversion best practice.  It seems to me that changing the code in the tag defeats the purpose of the tag-- i.e. having a fixed version so we can refer to "version 4.5.0" instead of "version 4.5 at r5000."  
~S

(Duplicating reply to mailing list this time.)

On Mar 28, 2012, at 11:17 , Tim Tautges wrote:

> Hi all,
>  As you may have seen, I just backported a fix to MOAB version 4.5.  For the next few months, I'd like everyone to continue backporting important fixes to 4.5.  I'll start pointing applications to use 4.5, esp ones that aren't dependent on lots of concurrent MOAB development.  On the MCS LAN, I'll also periodically update the /home/fathom/libs/MOAB-4.5-... directories as needed, which hold builds for the various compiler/configuration options (pgi/intel, serial/parallel).  For gcc, you should use the intel version.  If you're not sure whether something is important enough to backport, please ask.
> 
> Thanks.
> 
> - tim
> 
> -- 
> ================================================================
> "You will keep in perfect peace him whose mind is
>  steadfast, because he trusts in you."               Isaiah 26:3
> 
>             Tim Tautges            Argonne National Laboratory
>         (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
> phone (gvoice): (608) 354-1459      1500 Engineering Dr.
>            fax: (608) 263-4499      Madison, WI 53706
>