<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Sarah, I think the binary should be called 0.92.1, and it should be built from the 0.92.1 tag which should be a tag of the latest revision in the 0.92 branches of both Swift and CoG.<div><br></div><div>We should never put out two different releases with the same version number.</div><div><br></div><div>Ketan or Justin, you should create a Swift_0.92.1 module on Beagle per Justin's email based on my Cray support mods, and all future modules we create should be based on a tag, just like the general releases. (Ideally in the future the Cray modules should just *be* general releases).</div><div><br></div><div>- Mike</div><div><br></div><div><br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;">and should the binary then still be called 0.92 rather than 0.92.1 ? <br>
<br>
being that 0.92 had such a substantial flaw and a warning was posted on
the site, it seems to me that we'd want to make it clear (to users) that this is a
new version/release by naming it 0.92.1...does tagging adequately solve
this?<br><br><br><div class="gmail_quote">On Wed, Apr 13, 2011 at 11:30 AM, Mihael Hategan <span dir="ltr"><<a href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, 2011-04-13 at 11:26 -0700, Sarah Kenny wrote:<br>
> oh, i thought we were branching it...should i move that back?<br>
<br>
</div>We're tagging point releases. I.e. branches/0.92 -> tags/0.92.1<br>
<br>
Mihael<br>
<div><div></div><div class="h5">><br>
> On Wed, Apr 13, 2011 at 11:23 AM, Michael Wilde <<a href="mailto:wilde@mcs.anl.gov" target="_blank">wilde@mcs.anl.gov</a>><br>
> wrote:<br>
> Sarah, All,<br>
><br>
> Is this 0.92.1 branch just a last-time special-case for the<br>
> 0.92.1 release?<br>
><br>
> While the plan, as I understood it, is that in the future we<br>
> will only create branches for a "point" release (e.g. 0.93)<br>
> but all sub-point releases based on that branch (e.g. 0.93.1,<br>
> 0.93.2, etc) will be just tags on the 0.93 branch rather than<br>
> new branches?<br>
><br>
> - Mike<br>
><br>
><br>
><br>
><br>
><br>
> ----- Original Message -----<br>
> > Author: skenny<br>
> > Date: 2011-04-13 13:02:28 -0500 (Wed, 13 Apr 2011)<br>
> > New Revision: 4363<br>
> ><br>
> > Added:<br>
> > branches/release-0.92.1/<br>
> > Removed:<br>
> > branches/release-0.92/<br>
> > Log:<br>
> > 0.92 release fixed, moving to 092.1<br>
> ><br>
> > Copied: branches/release-0.92.1 (from rev 4362,<br>
> branches/release-0.92)<br>
> ><br>
> > _______________________________________________<br>
> > Swift-commit mailing list<br>
> > <a href="mailto:Swift-commit@ci.uchicago.edu" target="_blank">Swift-commit@ci.uchicago.edu</a><br>
> > <a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-commit" target="_blank">http://mail.ci.uchicago.edu/mailman/listinfo/swift-commit</a><br>
><br>
><br>
> --<br>
> Michael Wilde<br>
> Computation Institute, University of Chicago<br>
> Mathematics and Computer Science Division<br>
> Argonne National Laboratory<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> Swift-devel mailing list<br>
> <a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a><br>
> <a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel" target="_blank">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a><br>
<br>
<br>
</blockquote></div><br>
</blockquote><br><span><br><br>-- <br><span name="x"></span>Michael Wilde<br>Computation Institute, University of Chicago<br>Mathematics and Computer Science Division<br>Argonne National Laboratory<br><span name="x"></span><br></span></div></div></body></html>