mike wilde was suggesting that trunk and branches/1.0 are equally stable so he wants to do a release of what's currently in trunk (which means we need to branch it). the users i'm supporting only use branches/1.0 and have been doing so reliably for many months...the actual 'usability' of trunk i'm less familiar with but mike was hoping to put effort towards releasing that rather than spending time/effort on releasing branches/1.0 since it lacks many of the newer fixes and features. <br>
<br>~sk<br><br><div class="gmail_quote">On Mon, Dec 6, 2010 at 7:26 PM, Mihael Hategan <span dir="ltr"><<a href="mailto:hategan@mcs.anl.gov">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;">
I am of the opinion that if we have a choice of releasing branches/1.0<br>
now or releasing trunk at the end of January, we should release<br>
branches/1.0 now.<br>
<font color="#888888"><br>
Mihael<br>
</font><div><div></div><div class="h5"><br>
On Mon, 2010-12-06 at 14:01 -0600, Michael Wilde wrote:<br>
> Im loosing track, but I thought trunk will become branch 0.10?<br>
><br>
><br>
> I wanted to name it based on what we're trying to say to the user<br>
> community: this next release I feel is still pre-1.0 quality.  After<br>
> more doc cleanup and usability cleanup and web polishing, I feel we're<br>
> ready to try to make a broader announcement and call it 1.0.  Im<br>
> thinking end of this January for that.<br>
><br>
><br>
> - Mike<br>
><br>
><br>
> ______________________________________________________________________<br>
>         feel free, justin. i'm currently editing stuff that i think<br>
>         should go into doc for the 12/20 release (e.g. describing<br>
>         features that exist but aren't documented, etc.).<br>
><br>
>         so, branch 1.0 will become release 0.10...seems a bit<br>
>         confusing to me...also considering the differences between 0.9<br>
>         and what we're releasing doesn't calling it 1.0 make sense?<br>
>         just a thought...<br>
><br>
>         ~sk<br>
><br>
>         On Mon, Dec 6, 2010 at 7:51 AM, Justin M Wozniak<br>
>         <<a href="mailto:wozniak@mcs.anl.gov">wozniak@mcs.anl.gov</a>> wrote:<br>
><br>
>                 Sounds great- I was actually thinking about setting up<br>
>                 the branch-specific docs later this week, do you<br>
>                 already have a start on that?<br>
><br>
><br>
><br>
>                 On Mon, 6 Dec 2010, Sarah Kenny wrote:<br>
><br>
>                         so, my expectation for the release, as we've<br>
>                         discussed somewhat on the list<br>
>                         already, is to put out swift 1.0 on 12/20<br>
>                         which, as i see it,  involves<br>
>                         primarily editing of the documentation/web<br>
>                         content more so than anything<br>
>                         else since all new code (and documentation<br>
>                         associated with the new code)<br>
>                         going into trunk is expected to be in the 1.1.<br>
>                         release--which hopefully we<br>
>                         can have out in the next few months. i'm also<br>
>                         assuming we're sticking with<br>
>                         the plan to allow each release to have its own<br>
>                         doc version along with the<br>
>                         code.<br>
><br>
>                         let me know if anyone thinks there are other<br>
>                         things that can/should go into<br>
>                         the 12/20 release.<br>
><br>
>                         ~sk<br>
><br>
>                         On Tue, Nov 23, 2010 at 2:10 PM, Michael Wilde<br>
>                         <<a href="mailto:wilde@mcs.anl.gov">wilde@mcs.anl.gov</a>> wrote:<br>
><br>
>                                 All,<br>
><br>
>                                 Sarah is going to take the lead in<br>
>                                 producing the next Swift release, and<br>
>                                 will propose a release definition and<br>
>                                 plan. We want to have the release done<br>
>                                 by Dec 20.<br>
><br>
>                                 - Mike<br>
><br>
>                                 _______________________________________________<br>
>                                 Swift-devel mailing list<br>
>                                 <a href="mailto:Swift-devel@ci.uchicago.edu">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>
><br>
><br>
>                 --<br>
>                 Justin M Wozniak<br>
><br>
><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>
> _______________________________________________<br>
> Swift-devel mailing list<br>
> <a href="mailto:Swift-devel@ci.uchicago.edu">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>
</div></div></blockquote></div><br>