<html><head><meta http-equiv="Content-Type" content="text/html charset=iso-8859-1"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Can we detail how to get changes in our yt_analysis/yt-3.0 repos into the yt-3.0 branch of yt_analysis/yt? I'm guessing it's simple but probably not as simple as hitting the PR button on Bitbucket.<div><br><div><div>On Nov 26, 2013, at 9:52 AM, Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">+1</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Nov 26, 2013 at 6:38 AM, j s oishi <span dir="ltr"><<a href="mailto:jsoishi@gmail.com" target="_blank">jsoishi@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">+1. Let's do this.</div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">
On Tue, Nov 26, 2013 at 9: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">Hi all,<br>
<br>
I'd be +1 on this. Keep the yt-3.0 branch separate, make<br>
yt_analysis/yt-3.0 read-only, and move yt-3.0 the branch itself into<br>
the main yt_analysis/yt repository.<br>
<div><br>
On Tue, Nov 26, 2013 at 7:29 AM, John Wise <<a href="mailto:jwise@physics.gatech.edu" target="_blank">jwise@physics.gatech.edu</a>> wrote:<br>
> Hi,<br>
><br>
> As someone that just moved to the yt-3.0 repo (and not having much time for<br>
> dev anymore...), I think this is a good idea. Having it separate was a<br>
> barrier for me because 2.x worked for most of my analysis, and I just kept<br>
> on using 2.x because of convenience. However, if the latest changes were in<br>
> the main repo, then users could easily switch to the 3.0 branch and test<br>
> things out.<br>
><br>
> +1<br>
><br>
> Cheers,<br>
> John<br>
><br>
><br>
> On 11/26/2013 07:20 AM, Britton Smith wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> Now that we have pushed out the last (or nearly the last) major release<br>
>> of yt-2.x, many are now joining the effort to work on yt-3.0. As you<br>
>> may have noticed, there is a yt-3.0 branch in the main yt repo hosted at<br>
>> <a href="https://bitbucket.org/yt_analysis/yt" target="_blank">https://bitbucket.org/yt_analysis/yt</a>. However, most of the actual<br>
>> development has been happening in a separate yt-3.0 repo<br>
>> (<a href="https://bitbucket.org/yt_analysis/yt-3.0" target="_blank">https://bitbucket.org/yt_analysis/yt-3.0</a>).<br>
>><br>
>> I think it may now be time to consider moving yt-3.0 development over to<br>
>> the main repository. I think this will lower the barrier of entry for a<br>
>> number of people and should not be a big problem to users of 2.x now<br>
>> that that version has mostly stabilized.<br>
>><br>
>> As for logistics, a number of people have done work in forks of the<br>
>> yt-3.0, so we should not remove it entirely. Instead, I propose making<br>
>> it read-only, and having people push their changes to a fork of the main<br>
>> yt repo and working off of that from now on. The magic of mercurial<br>
>> should make this relatively painless.<br>
>><br>
>> Thoughts? +/-1?<br>
>><br>
>> Britton<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>
> John Wise<br>
> Assistant Professor of Physics<br>
> Center for Relativistic Astrophysics, Georgia Tech<br>
> <a href="http://cosmo.gatech.edu/" target="_blank">http://cosmo.gatech.edu</a><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>
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></blockquote></div><br></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>
_______________________________________________<br>yt-dev mailing list<br><a href="mailto:yt-dev@lists.spacepope.org">yt-dev@lists.spacepope.org</a><br>http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org<br></blockquote></div><br></div></body></html>