Well, there is definitely enough in master now to warrant a release. Looking through the log, I see (among other things):
- Tons of bug fixes - My entire Google Summer of Code Project (the ode module, and also a bunch of bug fixes) - Work on piecewise functions and intervals - Wicks/Second Quant work - Queries Module - Probably a bunch of stuff I missed - Did I mention the bug fixes? So I guess it depends on how close we are with the Polys and the assumptions. If we are not that far, we should just wait, because doing a release is a lot of work. On the other hand, those are much more major and will likely break more things when they are put in. At any rate, I think we should try to get Chris's test runner to work before any release, because the critical issue 1641 where the doctests do not work. I also want to know Ondrej's opinion too :) By the way, what do you mean by the simplified expand? Aaron Meurer On Dec 1, 2009, at 4:00 PM, Vinzent Steinberg wrote: > Well, 0.7 would be a great opportunity to break the API compability > (removing old assumptions, new polys, simplified expand etc.), so I > thought we could make a 0.6 release before, because there are already > enough changes accumulated. What do you think? > > 2009/12/1 Aaron S. Meurer <asmeu...@gmail.com>: >> Are there going to be separate 0.6.6 and 0.7 releases? I thought that we >> were going to just jump right up to 0.7. >> >> Aaron Meurer >> On Dec 1, 2009, at 3:29 PM, Vinzent Steinberg wrote: >> >>> 2009/12/1 Ondrej Certik <ond...@certik.cz>: >>>> We have to get the new polys in finally. I will have time to write >>>> some documentation for it --- Mateusz, could you please rebase it to >>>> the latest master? I'll then do my best. I think it fixes lots of >>>> problems. >>>> >>>> Ondrej >>> >>> Chris did already rebase it on his polys2 branch I think. >>> >>> Getting it in for 0.6.6 or 0.7? >>> >>> Vinzent >>> >>> -- >>> >>> You received this message because you are subscribed to the Google Groups >>> "sympy-patches" group. >>> To post to this group, send email to sympy-patc...@googlegroups.com. >>> To unsubscribe from this group, send email to >>> sympy-patches+unsubscr...@googlegroups.com. >>> For more options, visit this group at >>> http://groups.google.com/group/sympy-patches?hl=en. >>> >>> >> >> -- >> >> You received this message because you are subscribed to the Google Groups >> "sympy-patches" group. >> To post to this group, send email to sympy-patc...@googlegroups.com. >> To unsubscribe from this group, send email to >> sympy-patches+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/sympy-patches?hl=en. >> >> >> > > -- > > You received this message because you are subscribed to the Google Groups > "sympy-patches" group. > To post to this group, send email to sympy-patc...@googlegroups.com. > To unsubscribe from this group, send email to > sympy-patches+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sympy-patches?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sympy-patches" group. To post to this group, send email to sympy-patc...@googlegroups.com. To unsubscribe from this group, send email to sympy-patches+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sympy-patches?hl=en.
