[yt-dev] Code freeze?

[Matthew Turk]

Sounds good, that'll be great to have in.

On Thu, Jul 17, 2014 at 4:33 PM, John ZuHone <jzuhone at gmail.com> wrote:
> Tomorrow I'd like to submit one final PR with the fixes for Windows.
>
> On Jul 17, 2014, at 5:31 PM, Nathan Goldbaum <nathan12343 at gmail.com> wrote:
>
> One more thought.  What about matplotlib 1.4?  I was planning on updating
> the install script for some of our python dependencies when matplotlib 1.4
> shipped.
>
> I'd feel much more comfortable if we could include that in the install
> script as part of the yt-3 release due to the issue with ndarray subclasses
> in matplotlib 1.3.1.  According to the matplotlib-devel mailing list,
> they're planning on releasing on July 26th (well, really, "two weeks from
> today" in an e-mail on July 12), but no telling if anything will actually be
> released that day.
>
> -Nathan
>
>
> On Thu, Jul 17, 2014 at 2:25 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>>
>> On Thu, Jul 17, 2014 at 4:22 PM, Cameron Hummels <chummels at gmail.com>
>> wrote:
>> > The issue I've been going back-and-forth on making new particle filters
>> > generate deposit fields which show up in the derived_field_list is
>> > something
>> > that I've put off working on the last couple of days, but I think it's a
>> > bug
>> > that shoudl be fixed prior to release.  Other than that, it seems like
>> > just
>> > the failing cookbook fixes are the remaining code fixes, I think.
>>
>> I think just appending them, like I suggested in my previous email,
>> should fix it.  Tomorrow during the doc sprint we can see if that
>> fixes it.
>>
>> >
>> >
>> > On Thu, Jul 17, 2014 at 2:20 PM, Nathan Goldbaum <nathan12343 at gmail.com>
>> > wrote:
>> >>
>> >>
>> >>
>> >>
>> >> On Thu, Jul 17, 2014 at 2:14 PM, Matthew Turk <matthewturk at gmail.com>
>> >> wrote:
>> >>>
>> >>> Hi everyone,
>> >>>
>> >>> Are there any outstanding, code-not-documentation issues other than
>> >>> existing pull requests that we need to get in before 3.0 goes out?
>> >>>
>> >>
>> >> +1
>> >>
>> >>>
>> >>> If not, I'd like to propose a code freeze on the yt-3.0 branch in
>> >>> anticipation of the release, which I would like to shoot for happening
>> >>> by the end of July.
>> >>>
>> >>> Looking over Trello, the only thing that sticks out at me is boundary
>> >>> conditions, which I think needs to wait for 3.1.
>> >>
>> >>
>> >> What should we do with the remaining failing cookbook recipes?  Some of
>> >> them require code changes to fix them.
>> >>
>> >>>
>> >>>
>> >>> -Matt
>> >>> _______________________________________________
>> >>> 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
>
>
> _______________________________________________
> 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
>