<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Nathan and Britton,<div class=""><br class=""></div><div class="">I think the work of separating the astrophysical analysis modules is relevant here. There are issues in the main yt repo that’s related to those analysis modules, for example issues related to halo analysis. Once the analysis module separation is finished, I guess the related issues would also be transferred to the new repo at <a href="https://github.com/yt-project/yt_astro_analysis" class="">https://github.com/yt-project/yt_astro_analysis</a>. If this will happen before the 3.4 release, those issues should not be blockers.</div><div class=""><br class=""></div><div class="">Bili</div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On May 3, 2017, at 5:32 PM, Britton Smith <<a href="mailto:brittonsmith@gmail.com" class="">brittonsmith@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Nathan,<div class=""><br class=""></div><div class="">Thank you for taking the time to look through all the issues. I agree with designating all "new feature", "help wanted", and "wish" labels for 3.5. I also think all "enhancements" should be marked 3.5 as well. I think we should try to limit blockers to breakages or reversions so as to reduce the number of 3.4 issues to as low as possible.</div><div class=""><br class=""></div><div class="">I am definitely +1 on that hangout and will try to participate.</div><div class=""><br class=""></div><div class="">Britton</div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Wed, May 3, 2017 at 5:17 PM, Nathan Goldbaum <span dir="ltr" class=""><<a href="mailto:nathan12343@gmail.com" target="_blank" class="">nathan12343@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Hi all,<div class=""><br class=""></div><div class="">Now that we're fully on github I took the opportunity today to triage our issue list. There were a number of issues that I could close immediately either because they are fixed already, were classified incorrectly as open when we imported them from bitbucket, or because there wasn't sufficient information to reproduce or understand the reported issue.</div><div class=""><br class=""></div><div class="">That leaves us with 97 open issues. Now we need to decide which of those 97 issues should be blockers for a 3.4 release. Currently almost all of the open issues are in a new 3.4 "milestone" we can track:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/yt-project/yt/milestone/14" target="_blank" class="">https://github.com/yt-project/<wbr class="">yt/milestone/14</a><br class=""></div><div class=""><br class=""></div><div class="">I've also created a bunch of labels. We can probably bikeshed about what they should be named and if we have too many:</div><div class=""><br class=""></div><div class=""><a href="https://github.com/yt-project/yt/labels" target="_blank" class="">https://github.com/yt-project/<wbr class="">yt/labels</a><br class=""></div><div class=""><br class=""></div><div class="">I'd like to propose that we move all the issues I've marked "new feature", "help wanted", and "wish" labels to a new 3.5 milestone. In addition, I think many of the issues marked "enhancement" can also be moved.</div><div class=""><br class=""></div><div class="">I think it would be worthwhile to schedule a hangout sometime in the next couple weeks to determine which issues should block a 3.4 release. Let me know if you are interested in that so we can figure out a date and time.</div><span class="m_-3106076152504387067HOEnZb"><font color="#888888" class=""><div class=""><br class=""></div><div class="">-Nathan</div></font></span></div>
<br class="">______________________________<wbr class="">_________________<br class="">
yt-dev mailing list<br class="">
<a href="mailto:yt-dev@lists.spacepope.org" target="_blank" class="">yt-dev@lists.spacepope.org</a><br class="">
<a href="http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org" rel="noreferrer" target="_blank" class="">http://lists.spacepope.org/lis<wbr class="">tinfo.cgi/yt-dev-spacepope.org</a><br class="">
<br class=""></blockquote></div><br class=""></div></div>
_______________________________________________<br class="">yt-dev mailing list<br class=""><a href="mailto:yt-dev@lists.spacepope.org" class="">yt-dev@lists.spacepope.org</a><br class="">http://lists.spacepope.org/listinfo.cgi/yt-dev-spacepope.org<br class=""></div></blockquote></div><br class=""></div></body></html>