<div dir="ltr">Also late to the discussion, but have been following along. I think I like Britton's suggestion here. Named yt-2 branch will allow it exist in history and if for some reason additional development is done on it, there is an obvious path forward. I also agree that when yt-3.0 is released it should be merged into yt and stable.<div>
<br></div><div>Sam</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jul 23, 2014 at 10:54 AM, Britton Smith <span dir="ltr"><<a href="mailto:brittonsmith@gmail.com" target="_blank">brittonsmith@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">Hi everyone,<div><br></div><div>I'm late to the discussion, but here's my opinion:</div><div><br>
</div><div>1. yt-x.2 should become a named branch (maybe just "yt-2").</div><div>2. <span style="font-family:arial,sans-serif;font-size:13px">yt-3.0 goes into "yt" and "stable" at the time of the release. Further development happens in "yt" just as it used to.</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px">3. </span><span style="font-family:arial,sans-serif;font-size:13px">yt-3.0 the branch closes as soon as is feasible.</span></div><div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">I don't like names like "legacy", "modern", etc that do not really describe what it is. yt-2.x may get one or more final point releases and/or bugfixes that will need a home and I think it's worthwhile that yt-2.x live some place visible.</div>
<div style="font-family:arial,sans-serif;font-size:13px"><br></div><div style="font-family:arial,sans-serif;font-size:13px">The "stable" branch should always stand for "if you don't know what you want, you want this" which to me is the latest trusted release, or the thing you want people starting on. Once yt-3.0 is released, that should be yt-3.0.</div>
<span class="HOEnZb"><font color="#888888">
</font></span></div><span class="HOEnZb"><font color="#888888"><div class="gmail_extra"><br></div><div class="gmail_extra">Britton</div></font></span><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">
On Wed, Jul 23, 2014 at 6:32 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"><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Wed, Jul 23, 2014 at 10:26 AM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>On Wed, Jul 23, 2014 at 12:07 PM, Nathan Goldbaum <<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>> 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 lot<br>
>> of active development occurs.<br>
>> * yt => The 2.x development branch, which has slowed almost to a 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>
</div>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></blockquote><div><br></div></div><div>Ah, of course that makes sense. I guess we'll need to have two open development branches and merge from the yt-3.0 branch into the yt branch regularly.</div>
<div><div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div><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" 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>
</div></div></blockquote></div></div></div><br></div></div>
<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></blockquote></div><br></div></div></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>