<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Times New Roman; font-size: 12pt; color: #000000'>Also, will there be a swift_0.92.1 tag in CoG SVN? It would be nice to have identical tag names to check out under both repositories.<div><br></div><div>- Mike<br><br><hr id="zwchr"><blockquote style="border-left:2px solid rgb(16, 16, 255);margin-left:5px;padding-left:5px;">they should get it directly from tags instead of svn co <a href="https://svn.ci.uchicago.edu/svn/vdl2/branches/release-0.92" target="_blank">https://svn.ci.uchicago.edu/svn/vdl2/branches/release-0.92</a> swift ?<br><br><div class="gmail_quote">
On Wed, Apr 13, 2011 at 12:14 PM, 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 12:09 -0700, Sarah Kenny wrote:<br>
> alrighty, so, does this seem right to everyone?<br>
<br>
</div>Almost. The instructions for checking out the source code are not quite<br>
right.<br>
<div><div></div><div class="h5">><br>
> <a href="http://www.ci.uchicago.edu/%7Eskenny/swift/downloads/index.php" target="_blank">http://www.ci.uchicago.edu/~skenny/swift/downloads/index.php</a><br>
><br>
> i'm doing a run thru of the site tester now building from<br>
> tags/release-0.92.1 as a sanity test and assuming all goes well that's<br>
> what i will use to build the binary.<br>
><br>
> let me know if this sounds ok or if i'm missing anything here.<br>
><br>
> On Wed, Apr 13, 2011 at 11:53 AM, Mihael Hategan <<a href="mailto:hategan@mcs.anl.gov" target="_blank">hategan@mcs.anl.gov</a>><br>
> wrote:<br>
> On Wed, 2011-04-13 at 11:33 -0700, Sarah Kenny wrote:<br>
> > and should the binary then still be called 0.92 rather than<br>
> 0.92.1 ?<br>
><br>
><br>
> The binary would be called 0.92.1.<br>
> ><br>
> > being that 0.92 had such a substantial flaw and a warning<br>
> was posted<br>
> > on the site, it seems to me that we'd want to make it clear<br>
> (to users)<br>
> > that this is a new version/release by naming it<br>
> 0.92.1...does tagging<br>
> > adequately solve this?<br>
><br>
><br>
> Tagging doesn't solve that. Tagging is there so that we can<br>
> have some<br>
> label in SVN that matches the packages that we release as<br>
> opposed to<br>
> having to track a specific revision in the branch.<br>
> ><br>
><br>
><br>
><br>
<br>
<br>
</div></div></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>