Hi Jeff<br><br>> Holy crap, I didn't realize<br>
> <br>
> pip install yt<br>
> <br>> was a goal! that would be awesome.<br><br>In that case you may be interested in this ubuntu PPA I made a little while ago, for yt (2.4) and yt-devel (2.5): <a href="https://launchpad.net/~kuhlen/+archive/ppa">https://launchpad.net/~kuhlen/+archive/ppa</a><br>
<br>The current version of yt-devel is based on changeset 467f57b (from 08/24). I need to update it...<br><br>Cheers,<br><br>Mike<br><br><div class="gmail_quote">On Tue, Oct 9, 2012 at 4:03 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Casey,<br>
<div class="im"><br>
On Tue, Oct 9, 2012 at 3:59 PM, Casey W. Stark <<a href="mailto:caseywstark@gmail.com">caseywstark@gmail.com</a>> wrote:<br>
> Just so this is clear, if we are working on development that is not testing,<br>
> should we move over to 3.0 now?<br>
<br>
</div>Not yet, but soon. Sorry, I should have been more clear -- I believe<br>
it's almost ready for primetime, and in a settled state for<br>
rectilinear, patch-based data. I will update the list very, very soon<br>
on its state. I'll go through the milestone list and take a crack at<br>
updating the tickets, the scripts, and report back.<br>
<br>
-Matt<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> - Casey<br>
><br>
><br>
> On Tue, Oct 9, 2012 at 2:38 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>> wrote:<br>
>><br>
>> Sounds good to me. I was actually also holding out a bit to incorporate<br>
>> testing into some of the new rendering capabilities anyways.<br>
>><br>
>><br>
>> On Tue, Oct 9, 2012 at 3:36 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>> wrote:<br>
>>><br>
>>> Hi Sam,<br>
>>><br>
>>> On Tue, Oct 9, 2012 at 2:30 PM, Sam Skillman <<a href="mailto:samskillman@gmail.com">samskillman@gmail.com</a>><br>
>>> wrote:<br>
>>> > If the release timeframe is end of year, I will put in the alpha<br>
>>> > channel<br>
>>> > rendering, enabling a lot of cool things. It is already functional in<br>
>>> > one<br>
>>> > of my forks, but it needs to be cleaned up.<br>
>>><br>
>>> What if we said instead that we'd release as soon as unit testing is<br>
>>> ready and 3.0 is ready for daily use for patch-based AMR, and then if<br>
>>> you have time before that point to get the alpha channel in good, but<br>
>>> otherwise toss it into 3.0?<br>
>>><br>
>>> -Matt<br>
>>><br>
>>> ><br>
>>> > Sam<br>
>>> ><br>
>>> ><br>
>>> > On Tue, Oct 9, 2012 at 3:28 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>> > wrote:<br>
>>> >><br>
>>> >> Hi Jeff,<br>
>>> >><br>
>>> >> On Tue, Oct 9, 2012 at 2:19 PM, j s oishi <<a href="mailto:jsoishi@gmail.com">jsoishi@gmail.com</a>> wrote:<br>
>>> >> > Hi,<br>
>>> >> ><br>
>>> >> > Since testing is something that is so high priority for this, and<br>
>>> >> > otherwise 2.5 is just a stepping stone to 3.0 (which a *lot* of<br>
>>> >> > people<br>
>>> >> > are already diving into), maybe we should *only* include testing,<br>
>>> >> > unless there are some already done things we could toss in?<br>
>>> >> ><br>
>>> >> > j<br>
>>> >><br>
>>> >> Come to mention it, I *really* like this idea. Perhaps we should<br>
>>> >> identify a threshold for building out the non-core infrastructure<br>
>>> >> fixes (i.e., having "pip install yt" work, having a good set of<br>
>>> >> testing, etc etc) and then any other fixes or improvements that happen<br>
>>> >> along the way are just icing on the cake? I think having better<br>
>>> >> testing should definitely be the focus, particularly as we transition<br>
>>> >> the codebase.<br>
>>> >><br>
>>> >> -Matt<br>
>>> >><br>
>>> >> ><br>
>>> >> > On Tue, Oct 9, 2012 at 5:14 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>><br>
>>> >> > wrote:<br>
>>> >> >> Hi all,<br>
>>> >> >><br>
>>> >> >> We should probably try to get a 2.5 release together by the end of<br>
>>> >> >> the<br>
>>> >> >> year. It would be really helpful if you are working on something,<br>
>>> >> >> to<br>
>>> >> >> fill it out and target both milestone 2.5 and version 2.5 as an<br>
>>> >> >> issue.<br>
>>> >> >> That way we can identify goals and push to stable. Testing should<br>
>>> >> >> perhaps be a huge focus of this release. But, once it's done, I<br>
>>> >> >> think<br>
>>> >> >> we can try to transition to 3.0 for development.<br>
>>> >> >><br>
>>> >> >> Here's the current list, which may need curation a bit as some seem<br>
>>> >> >> to<br>
>>> >> >> be completed or in progress:<br>
>>> >> >><br>
>>> >> >><br>
>>> >> >><br>
>>> >> >> <a href="https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open&milestone=2.5" target="_blank">https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open&milestone=2.5</a><br>
>>> >> >><br>
>>> >> >> If you want to subdivide something, create a new milestone and<br>
>>> >> >> target<br>
>>> >> >> *that*, but with *version* 2.5.<br>
>>> >> >><br>
>>> >> >> -Matt<br>
>>> >> >><br>
>>> >> >> PS The new bitbucket redesign is quite nice!<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>
>>> >> > 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>
>>> >> 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>
>>> ><br>
>>> ><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>
>>> _______________________________________________<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>
>><br>
>><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>
><br>
><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>
_______________________________________________<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>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>*********************************************************************<br>* *<br>* Dr. Michael Kuhlen Theoretical Astrophysics Center *<br>
* email: <a href="mailto:mqk@astro.berkeley.edu" target="_blank">mqk@astro.berkeley.edu</a> UC Berkeley *<br>* cell phone: (831) 588-1468 B-116 Hearst Field Annex # 3411 *<br>* skype username: mikekuhlen Berkeley, CA 94720 *<br>
* *<br>*********************************************************************<br><br>