[yt-dev] Release 2.5?

[Matthew Turk]

Hi Sam,

On Tue, Oct 9, 2012 at 2:30 PM, Sam Skillman <samskillman at gmail.com> wrote:
> If the release timeframe is end of year, I will put in the alpha channel
> rendering, enabling a lot of cool things.  It is already functional in one
> of my forks, but it needs to be cleaned up.

What if we said instead that we'd release as soon as unit testing is
ready and 3.0 is ready for daily use for patch-based AMR, and then if
you have time before that point to get the alpha channel in good, but
otherwise toss it into 3.0?

-Matt

>
> Sam
>
>
> On Tue, Oct 9, 2012 at 3:28 PM, Matthew Turk <matthewturk at gmail.com> wrote:
>>
>> Hi Jeff,
>>
>> On Tue, Oct 9, 2012 at 2:19 PM, j s oishi <jsoishi at gmail.com> wrote:
>> > Hi,
>> >
>> > Since testing is something that is so high priority for this, and
>> > otherwise 2.5 is just a stepping stone to 3.0 (which a *lot* of people
>> > are already diving into), maybe we should *only* include testing,
>> > unless there are some already done things we could toss in?
>> >
>> > j
>>
>> Come to mention it, I *really* like this idea.  Perhaps we should
>> identify a threshold for building out the non-core infrastructure
>> fixes (i.e., having "pip install yt" work, having a good set of
>> testing, etc etc) and then any other fixes or improvements that happen
>> along the way are just icing on the cake?  I think having better
>> testing should definitely be the focus, particularly as we transition
>> the codebase.
>>
>> -Matt
>>
>> >
>> > On Tue, Oct 9, 2012 at 5:14 PM, Matthew Turk <matthewturk at gmail.com>
>> > wrote:
>> >> Hi all,
>> >>
>> >> We should probably try to get a 2.5 release together by the end of the
>> >> year.  It would be really helpful if you are working on something, to
>> >> fill it out and target both milestone 2.5 and version 2.5 as an issue.
>> >>  That way we can identify goals and push to stable.  Testing should
>> >> perhaps be a huge focus of this release.  But, once it's done, I think
>> >> we can try to transition to 3.0 for development.
>> >>
>> >> Here's the current list, which may need curation a bit as some seem to
>> >> be completed or in progress:
>> >>
>> >>
>> >> https://bitbucket.org/yt_analysis/yt/issues?status=new&status=open&milestone=2.5
>> >>
>> >> If you want to subdivide something, create a new milestone and target
>> >> *that*, but with *version* 2.5.
>> >>
>> >> -Matt
>> >>
>> >> PS The new bitbucket redesign is quite nice!
>> >> _______________________________________________
>> >> 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
>