[yt-dev] yt 3.1?

Mon Nov 3 09:10:11 PST 2014

#1253 can go, but the tests will need to be updated.

It might be a good idea to do #1281 after the release to give it some time
to be used.  Tests also need to be updated for this one.

On Mon, Nov 3, 2014 at 5:07 PM, Douglas Harvey Rudd <drudd at uchicago.edu>
wrote:

>  I’m happy with #1264 going in.
>
>  Douglas Rudd
> Scientific Computing Consultant
> Research Computing Center
> drudd at uchicago.edu
>
>  On Nov 3, 2014, at 11:02 AM, Matthew Turk <matthewturk at gmail.com> wrote:
>
> Which PRs are ready to go and should be put in before the 3.1 release?  I
> am okay with us putting out 3.1, and then aiming for VR at 3.2.
>
>  -Matt
>
> On Fri Oct 31 2014 at 9:56:04 AM John ZuHone <jzuhone at gmail.com> wrote:
>
>> So where do we stand on 3.1?
>>
>>   On Oct 29, 2014, at 1:10 PM, John ZuHone <jzuhone at gmail.com> wrote:
>>
>>  I understand your reservations. Maybe we should wait for 3.2 for the VR
>> release. It sounds like we should put it through the paces.
>>
>>  Any chance anyone can push the button on the equivalence and particle
>> generator PRs? I need to narrow things down on the FITS one still.
>>
>>  On Oct 29, 2014, at 1:04 PM, Nathan Goldbaum <nathan12343 at gmail.com>
>> wrote:
>>
>>
>>
>> On Wed, Oct 29, 2014 at 6:47 AM, John ZuHone <jzuhone at gmail.com> wrote:
>>
>>> We’re due for a 3.0.3 soon, so it sounds like that’s what we should do.
>>>
>>
>>  Should we?
>>
>>  I worry about releasing new features in a "bugfix" release.
>>
>>  Can we call the VR release yt 3.2?
>>
>>
>>>
>>>  I’d like to see my 3 PRs pulled in as well as Doug’s compose PR. Are
>>> there any others folks want to advocate for?
>>>
>>>  John
>>>
>>>   On Oct 29, 2014, at 9:45 AM, Michael Zingale <
>>> michael.zingale at stonybrook.edu> wrote:
>>>
>>>  Once the new VR is pulled in, we should have a month or so of shaking
>>> out before a public release.  This way we can all try our favorite scripts
>>> and give feedback, etc.  We want VR to continue to work in the new release
>>> (API changes are fine).  I'm happy to do what I can to test things out when
>>> the time is right.
>>>
>>>  Mike
>>>
>>> On Tue, Oct 28, 2014 at 9:20 PM, Matthew Turk <matthewturk at gmail.com>
>>> wrote:
>>>
>>>> Well, then we shouldn't call it 3.1, I think.
>>>>
>>>>
>>>> On Tue Oct 28 2014 at 8:19:38 PM Cameron Hummels <chummels at gmail.com>
>>>> wrote:
>>>>
>>>>> I'm good with this.  I'm personally anxious about pushing the VR out
>>>>> right now, because there may be some API mods as the VR goes towards
>>>>> including movie stuff.  My concern is that if we push the new VR module
>>>>> into the public, people will use it and modifying the API will be very hard
>>>>> at that point because it will then break people's code.  The movie VR stuff
>>>>> is something I was going to begin working on once the static frame VR stuff
>>>>> was more set, which is what we're working on now.  I figured timeframe for
>>>>> both to be done was end of January, but Sam may have different ideas.
>>>>>
>>>>>  Cameron
>>>>>
>>>>> On Tue, Oct 28, 2014 at 4:48 PM, Britton Smith <brittonsmith at gmail.com
>>>>> > wrote:
>>>>>
>>>>>> Sounds good to me, too.
>>>>>>
>>>>>> On Tue, Oct 28, 2014 at 5:26 PM, Matthew Turk <matthewturk at gmail.com>
>>>>>>  wrote:
>>>>>>
>>>>>>> Sounds good to me.  I think we were due anyway.
>>>>>>>
>>>>>>> Sam, what do you think the chances of getting the VR PR landed are?
>>>>>>>
>>>>>>>  On Tue Oct 28 2014 at 4:26:22 PM Nathan Goldbaum <
>>>>>>> nathan12343 at gmail.com> wrote:
>>>>>>>
>>>>>>>>  Hi all,
>>>>>>>>
>>>>>>>>  There have been a number of cool new features in the pull request
>>>>>>>> queue recently. Some of these have added new features and I think it might
>>>>>>>> be worthwhile to indicate that by bumping the minor version number on the
>>>>>>>> next release.
>>>>>>>>
>>>>>>>>  I think it would be a good idea to try to integrate the open PRs
>>>>>>>> as well as any that come in over the next couple of weeks that can be
>>>>>>>> reviewed, call it yt 3.1 and release on or around Dec. 1. This
>>>>>>>> will mean generating a proofread docs build and perhaps a few days of
>>>>>>>> low-hanging issue triaging.
>>>>>>>>
>>>>>>>>  I'd nominate John ZuHone to send out the release email to
>>>>>>>> recognize the hard work he's been putting in recently.
>>>>>>>>
>>>>>>>>  Just an idea, but I've tried to include specifics as a basis for
>>>>>>>> further discussion.  What do you all think?
>>>>>>>>
>>>>>>>>  Nathan
>>>>>>>>  _______________________________________________
>>>>>>>> yt-dev mailing list
>>>>>>>> yt-dev at lists.spacepope.org
>>>>>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> yt-dev mailing list
>>>>>>> yt-dev at lists.spacepope.org
>>>>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> yt-dev mailing list
>>>>>> yt-dev at lists.spacepope.org
>>>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>  --
>>>>> Cameron Hummels
>>>>> Postdoctoral Researcher
>>>>> Steward Observatory
>>>>> University of Arizona
>>>>> http://chummels.org
>>>>>  _______________________________________________
>>>>> yt-dev mailing list
>>>>> yt-dev at lists.spacepope.org
>>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>>
>>>>
>>>> _______________________________________________
>>>> yt-dev mailing list
>>>> yt-dev at lists.spacepope.org
>>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>>
>>>>
>>>
>>>
>>>  --
>>> Michael Zingale
>>> Associate Professor
>>>
>>>  Dept. of Physics & Astronomy • Stony Brook University • Stony Brook,
>>> NY 11794-3800
>>> *phone*:  631-632-8225
>>> *e-mail*: Michael.Zingale at stonybrook.edu
>>> *web*: http://www.astro.sunysb.edu/mzingale
>>>  _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>>>
>>>
>>> _______________________________________________
>>> yt-dev mailing list
>>> yt-dev at lists.spacepope.org
>>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>>
>>>
>>  _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>>
>>
>>   _______________________________________________
>> yt-dev mailing list
>> yt-dev at lists.spacepope.org
>> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>>
>  _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
>
> _______________________________________________
> yt-dev mailing list
> yt-dev at lists.spacepope.org
> http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.spacepope.org/pipermail/yt-dev-spacepope.org/attachments/20141103/b6e4c1bb/attachment.html>