<div dir="ltr">I'm planning on finishing up the remaining docs issues that are assigned to me tonight: <div><br></div><div><div class="gmail_extra"><a href="https://bitbucket.org/yt_analysis/yt/issue/710/yt-hub-docs-need-some-updating">https://bitbucket.org/yt_analysis/yt/issue/710/yt-hub-docs-need-some-updating</a></div>
<div class="gmail_extra"><a href="https://bitbucket.org/yt_analysis/yt/issue/554/document-cosmology-units">https://bitbucket.org/yt_analysis/yt/issue/554/document-cosmology-units</a></div><div class="gmail_extra"><a href="https://bitbucket.org/yt_analysis/yt/issue/711/expand-upon-unit-handling">https://bitbucket.org/yt_analysis/yt/issue/711/expand-upon-unit-handling</a></div>
<div class="gmail_extra"><br></div><div class="gmail_extra">Don't think I'll be able to make a hangout AM Eastern time, but of the four docs issues that are currently anassigned, I think only the following issue is worth worrying about:</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"><a href="https://bitbucket.org/yt_analysis/yt/issue/632/need-to-document-derived_field">https://bitbucket.org/yt_analysis/yt/issue/632/need-to-document-derived_field</a><br>
</div><div class="gmail_extra"><br></div><div class="gmail_extra">Hope that's helpful for you guys :)</div><div class="gmail_extra"><br></div><div class="gmail_extra">-Nathan</div><div class="gmail_extra"><br><div class="gmail_quote">
On Thu, Nov 21, 2013 at 4:04 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:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Hi Britton,<br>
<div class="im"><br>
On Thu, Nov 21, 2013 at 9:09 AM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>> wrote:<br>
> I am +2 on Kacper sending the announcement.<br>
><br>
> We also still have 51 open issues tagged for version 2.6. Of those, only 11<br>
> are listed as blockers and are all documentation related. I am assigned two<br>
> of those and both can be done by tomorrow.<br>
><br>
> Of the 40 non-blocker issues, 20 are not even assigned. Maybe we should go<br>
> through those and figure out where they stand for the release. I think some<br>
> may need to be dealt with. Should we try to have a quick hangout to figure<br>
> that out?<br>
<br>
</div>I agree. I'd prefer that we focus on the blockers for a 2.6 release,<br>
and then we can either assign, move, or close the remaining ones for a<br>
later time. Would that work?<br>
<br>
I could also do a hangout tomorrow morning (east coast us time) to<br>
work through a few.<br>
<br>
-Matt<br>
<div class=""><div class="h5"><br>
><br>
> Britton<br>
><br>
><br>
> On Thu, Nov 21, 2013 at 1:35 PM, Matthew Turk <<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>> wrote:<br>
>><br>
>> Hi all,<br>
>><br>
>> Do we think a release tomorrow is still feasible? I think there are<br>
>> remaining pull requests for the code base (and I owe some tests for<br>
>> the profile plotter) and there are three outstanding doc PRs, too.<br>
>><br>
>> Additionally, when the release goes out, what does everybody think of<br>
>> asking Kacper to send the announcement?<br>
>><br>
>> -Matt<br>
>><br>
>> -Matt<br>
>><br>
>> On Mon, Nov 11, 2013 at 3:24 PM, John ZuHone <<a href="mailto:jzuhone@gmail.com">jzuhone@gmail.com</a>> wrote:<br>
>> > Sorry--let me be more clear--next week's Friday.<br>
>> ><br>
>> > On Nov 11, 2013, at 2:50 PM, Cameron Hummels <<a href="mailto:chummels@gmail.com">chummels@gmail.com</a>> wrote:<br>
>> ><br>
>> > Perhaps a compromise on the release date is to release 2.6 by mid-week<br>
>> > next<br>
>> > week? Or even Friday of next week? That way job apps can still<br>
>> > reference<br>
>> > the material which will be the main release, and will be put out before<br>
>> > Thanksgiving (most job apps are viewed after Thanksgiving, even ones due<br>
>> > prior to it), and it gives us a chance to get some due diligence on all<br>
>> > of<br>
>> > the blockers for 2.6. I agree that we should shoot for having<br>
>> > functional<br>
>> > code (and docs) above having something out there in the wild quickly.<br>
>> ><br>
>> > I agree with the sentiment that we can and should continue to tweek the<br>
>> > docs<br>
>> > (and bugs in the code) on the 2.x branch even after 2.6 release.<br>
>> ><br>
>> > The main things I see as blockers on 2.6 are the doc issues I've listed<br>
>> > as<br>
>> > "blockers". I'm going to go back through them right now, and make sure<br>
>> > they're all assigned to someone, and that the responsible person knows<br>
>> > that<br>
>> > these isses are blockers and should be done in the next 1-2 weeks.<br>
>> ><br>
>> ><br>
>> > On Mon, Nov 11, 2013 at 12:34 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com">brittonsmith@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Waiting on the PR is totally fine with me. Let's get that stuff right<br>
>> >> before we release it. I will definitely keep working the docs for it<br>
>> >> and<br>
>> >> have those ready for when the Profile/PhasePlot PR is ready.<br>
>> >><br>
>> >> That stuff aside, maybe here is where everyone should report in with<br>
>> >> what<br>
>> >> they'd like/need to get done before the 2.6 release and when they would<br>
>> >> like<br>
>> >> that release to take place. For me, other than any additional tweaks I<br>
>> >> might have to make to the Profile/Phase PR, my remaining assignments<br>
>> >> are all<br>
>> >> in the docs and I should be able to get them all done this week.<br>
>> >><br>
>> >> Finally, I would like to add a proposal that we allow for some<br>
>> >> additional<br>
>> >> doc tweaking after the official 2.6 release. We should definitely<br>
>> >> finish<br>
>> >> all of the blocker issues that have been laid out before releasing, but<br>
>> >> there will surely be small things that can be improved on that we might<br>
>> >> happen across at some later date. As this release or one soon after<br>
>> >> will be<br>
>> >> the final 2.x release, I would like to leave it as close to a finished<br>
>> >> product as possible.<br>
>> >><br>
>> >> Britton<br>
>> >><br>
>> >><br>
>> >> On Mon, Nov 11, 2013 at 6:57 PM, Nathan Goldbaum<br>
>> >> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> My main concern is that I’m not happy with the current state of<br>
>> >>> ProfilePlot and PhasePlot going out as they exist in the open PR.<br>
>> >>> That’s<br>
>> >>> not a dig on Britton - he did a great job - I just think we can do<br>
>> >>> better<br>
>> >>> and provide something that’s fully functional and tested.<br>
>> >>><br>
>> >>> That said, I don’t think that can happen by Friday. As I’ve said<br>
>> >>> elsewhere I’m happy to look at ProfilePlot and PhasePlot this weekend.<br>
>> >>><br>
>> >>> Britton, please don’t let this stop you from updating the docs for<br>
>> >>> ProfilePlot and PhasePlot. If anything breaks in your docs (I expect<br>
>> >>> it<br>
>> >>> won’t) I will update the docs myself.<br>
>> >>><br>
>> >>> -Nathan<br>
>> >>><br>
>> >>> On November 11, 2013 at 10:53:37 AM, Matthew Turk<br>
>> >>> (<a href="mailto:matthewturk@gmail.com">matthewturk@gmail.com</a>)<br>
>> >>> wrote:<br>
>> >>><br>
>> >>> Hi Nathan,<br>
>> >>><br>
>> >>> Well, so, I have to take the fall for this one. Last week, there was<br>
>> >>> some discussion about what needed to happen for a release, and I<br>
>> >>> misunderstood everything, evidently! I thought that the main issue<br>
>> >>> was the profile/phase plot code and the remaining doc tickets. So<br>
>> >>> this weekend, Britton issued the updated PR (which addressed the<br>
>> >>> comments you brought up in your original comments on the PR) and was<br>
>> >>> doing some docs updates.<br>
>> >>><br>
>> >>> This morning, I took a look at what was going on, and wrote to Cameron<br>
>> >>> asking him to decide which bugs for the docs were blockers and which<br>
>> >>> were not, and if we could try to aim for having everything in a<br>
>> >>> workable state by Friday, so the release could go out. (Only a few<br>
>> >>> weeks overdue -- and most of those weeks were due to *me* dragging my<br>
>> >>> heels!)<br>
>> >>><br>
>> >>> My main concern here is: people are putting out job apps, and some of<br>
>> >>> those job apps reference code that's in the yt 2.6 code base. I think<br>
>> >>> a good way to "do right by contributors" is to make sure that,<br>
>> >>> especially in a vulnerable time in a career, the project tries to<br>
>> >>> support them in whatever way it can. I've done a poor job of<br>
>> >>> implementing that, as releases have languished and gone on, and I was<br>
>> >>> just trying to right the ship, as it were. Ultimately, though, I do<br>
>> >>> think we should not release something we're not really happy with,<br>
>> >>> although I'd like to try to avoid having perfect be the enemy of good<br>
>> >>> enough. Maybe a good compromise would be to figure out what is still<br>
>> >>> necessary, come up with a reasonable timescale, and discuss it openly.<br>
>> >>> I screwed that up, and I'm sorry.<br>
>> >>><br>
>> >>> Anyway, I know there's been a lot of talk about 2.6 being the last<br>
>> >>> major 2.X release. Maybe that's put some pressure on this release<br>
>> >>> that's not warranted, and I will take the blame for that, too. I<br>
>> >>> anticipate we'll be fixing little things, tweaking docs, and on and<br>
>> >>> on, for some time to come. Just because I would like to encourage<br>
>> >>> people to try out 3.0 doesn't mean everybody has to stop using what<br>
>> >>> works. I expect much of our existing userbase won't change for a<br>
>> >>> while.<br>
>> >>><br>
>> >>> -Matt<br>
>> >>><br>
>> >>> On Mon, Nov 11, 2013 at 12:42 PM, Nathan Goldbaum<br>
>> >>> <<a href="mailto:nathan12343@gmail.com">nathan12343@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>> > Hi all,<br>
>> >>> ><br>
>> >>> > Cameron just pinged me about a docs issue with a Sizemore about the<br>
>> >>> > 2.6<br>
>> >>> > release happening on Friday. Can we hold off on that for another<br>
>> >>> > week<br>
>> >>> > or<br>
>> >>> > two? I'd like to be able to work on ProfilePlot and PhasePlot this<br>
>> >>> > weekend.<br>
>> >>> ><br>
>> >>> > Natha<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>
>> >>> 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>
>> > --<br>
>> > Cameron Hummels<br>
>> > Postdoctoral Researcher<br>
>> > Steward Observatory<br>
>> > University of Arizona<br>
>> > <a href="http://chummels.org" target="_blank">http://chummels.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>
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></div></div></div>