<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>+1<br><br>John ZuHone<div>Laboratory for High-Energy Astrophysics<br><div>NASA/Goddard Space Flight Center</div><div>8800 Greenbelt Rd., Mail Code 662</div><div>Greenbelt, MD 20771</div><div>(w) 301-286-2531</div><div>(m) 781-708-5004</div></div><div><a href="mailto:john.zuhone@nasa.gov">john.zuhone@nasa.gov</a></div><div><a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a></div></div><div><br>On Jul 23, 2014, at 5:59 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">+1</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 23, 2014 at 10:59 PM, Nathan Goldbaum <span dir="ltr"><<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Wed, Jul 23, 2014 at 2:57 PM, Matthew Turk <span dir="ltr"><<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Alright, so it seems like there's a bit of a broad consensus on making<br>
"stable" mean 3.0. I think my reluctance may just be related to<br>
anxiety about breakage. But, let's push through it.<br>
<br>
So, when we release, how about this?<br>
<br>
yt-3.0 => deprecated, not closed. Eventually, we will close.<br>
yt => this will be merged *into* from yt-3.0<br>
stable => this will be merged *into* from yt, post-3.0 merge (i.e., it<br>
will be 3.0)<br>
yt-2.x => this will be a new branch that starts at the current "stable" tip.<br>
<br>
How's that sound?<br></blockquote><div><br></div></div><div>+1</div><div><br></div><div><a href="http://i.imgur.com/vwMin.gif" target="_blank">http://i.imgur.com/vwMin.gif</a><br></div><div><div class="h5"><div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div><div><br>
On Wed, Jul 23, 2014 at 1:01 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com" target="_blank">samskillman@gmail.com</a>> wrote:<br>
> Also late to the discussion, but have been following along. I think I like<br>
> Britton's suggestion here. Named yt-2 branch will allow it exist in history<br>
> and if for some reason additional development is done on it, there is an<br>
> obvious path forward. I also agree that when yt-3.0 is released it should be<br>
> merged into yt and stable.<br>
><br>
> Sam<br>
><br>
><br>
> On Wed, Jul 23, 2014 at 10:54 AM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Hi everyone,<br>
>><br>
>> I'm late to the discussion, but here's my opinion:<br>
>><br>
>> 1. yt-x.2 should become a named branch (maybe just "yt-2").<br>
>> 2. yt-3.0 goes into "yt" and "stable" at the time of the release. Further<br>
>> development happens in "yt" just as it used to.<br>
>> 3. yt-3.0 the branch closes as soon as is feasible.<br>
>><br>
>> I don't like names like "legacy", "modern", etc that do not really<br>
>> describe what it is. yt-2.x may get one or more final point releases and/or<br>
>> bugfixes that will need a home and I think it's worthwhile that yt-2.x live<br>
>> some place visible.<br>
>><br>
>> The "stable" branch should always stand for "if you don't know what you<br>
>> want, you want this" which to me is the latest trusted release, or the thing<br>
>> you want people starting on. Once yt-3.0 is released, that should be<br>
>> yt-3.0.<br>
>><br>
>> Britton<br>
>><br>
>> On Wed, Jul 23, 2014 at 6:32 PM, Nathan Goldbaum <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>><br>
>>><br>
>>> On Wed, Jul 23, 2014 at 10:26 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>><br>
>>> wrote:<br>
>>>><br>
>>>> On Wed, Jul 23, 2014 at 12:07 PM, Nathan Goldbaum<br>
>>>> <<a href="mailto:nathan12343@gmail.com" target="_blank">nathan12343@gmail.com</a>> wrote:<br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > On Wed, Jul 23, 2014 at 4:18 AM, Matthew Turk <<a href="mailto:matthewturk@gmail.com" target="_blank">matthewturk@gmail.com</a>><br>
>>>> > wrote:<br>
>>>> >><br>
>>>> >> Hi everyone,<br>
>>>> >><br>
>>>> >> Yesterday during the doc sprint, the question of what to do about<br>
>>>> >> branches post-3.0 came up. Currently there are three branches, which<br>
>>>> >> correspond to different names on the front page of the yt homepage.<br>
>>>> >><br>
>>>> >> * Stable => The branch into which bug fixes are merged, but not a<br>
>>>> >> lot<br>
>>>> >> of active development occurs.<br>
>>>> >> * yt => The 2.x development branch, which has slowed almost to a<br>
>>>> >> halt<br>
>>>> >> * yt-3.0 => The 3.0 development branch<br>
>>>> >><br>
>>>> >> It seems there is broad consensus that after the release, the yt-3.0<br>
>>>> >> branch would be merged into the yt branch. (I would like to hold off<br>
>>>> >> on "closing" the yt-3.0 branch for a while, however.)<br>
>>>> ><br>
>>>> ><br>
>>>> > Why is that?<br>
>>>> ><br>
>>>><br>
>>>> Because until we get to the point that every developer has issued PRs<br>
>>>> for all of their yt-3.0 development, we're going to have multiple<br>
>>>> instances of "closing yt-3.0". Because it's decentralized, we can't<br>
>>>> force all, everywhere, to be closed.<br>
>>><br>
>>><br>
>>> Ah, of course that makes sense. I guess we'll need to have two open<br>
>>> development branches and merge from the yt-3.0 branch into the yt branch<br>
>>> regularly.<br>
>>><br>
>>>><br>
>>>><br>
>>>> >><br>
>>>> >> But, what is<br>
>>>> >> then to be done about the "stable" branch? My thought was:<br>
>>>> >><br>
>>>> >> * stable => will be on 2.x for at least one release, until 3.1<br>
>>>> >> * yt => 3.0<br>
>>>> >> * yt-3.0 => we try to migrate development onto the yt branch, which<br>
>>>> >> is 3.0, but don't force yet<br>
>>>> ><br>
>>>> ><br>
>>>> > I'd be -1 on having bugfixes for 3.0 on two branches.<br>
>>>> ><br>
>>>> >><br>
>>>> >><br>
>>>> >> The alternate idea was:<br>
>>>> >><br>
>>>> >> * stable => 3.0<br>
>>>> >> * yt => 3.0<br>
>>>> >> * yt-3.0 => closed<br>
>>>> >><br>
>>>> ><br>
>>>> > I'd prefer this, possibly with another named branch named "legacy"<br>
>>>> > that<br>
>>>> > contains 2.x.<br>
>>>> ><br>
>>>> >><br>
>>>> >> I think we need a longer migration time for 2.x, though. I will<br>
>>>> >> update YTEP-0008 with whatever we come up with, but is there a strong<br>
>>>> >> opinion for either of these options? Option 1: stable stays 2.x for<br>
>>>> >> now, Option 2, stable becomes 3.0.<br>
>>>> >><br>
>>>> >> -Matt<br>
>>>> >> _______________________________________________<br>
>>>> >> yt-dev mailing list<br>
>>>> >> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>> >> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>> ><br>
>>>> ><br>
>>>> ><br>
>>>> > _______________________________________________<br>
>>>> > yt-dev mailing list<br>
>>>> > <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>> > <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>>> ><br>
>>>> _______________________________________________<br>
>>>> yt-dev mailing list<br>
>>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>><br>
>>><br>
>>><br>
>>> _______________________________________________<br>
>>> yt-dev mailing list<br>
>>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>>><br>
>><br>
>><br>
>> _______________________________________________<br>
>> yt-dev mailing list<br>
>> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
>> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> yt-dev mailing list<br>
> <a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
> <a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
><br>
_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
</div></div></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
yt-dev mailing list<br>
<a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" target="_blank">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a><br>
<br></blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>yt-dev mailing list</span><br><span><a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a></span><br><span><a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org</a></span><br></div></blockquote></body></html>