Preparing for a 1.0 release

[Aaron Meurer]

As many of you know, I am starting a new research position at the
University of South Carolina with Anthony Scopatz's new research
group, ERGS. A large part of my work will involve improving SymPy,
particularly the code generation. I will also have time to do
supporting work on SymPy.

The first thing that I would like to do is get the promised 1.0
release out. The 1.0 release already has some major changes slated,
including splitting out of mpmath as a hard external dependency,
various changes to the old and new assumptions systems toward unifying
them (including various backwards incompatible changes to the
definitions of various assumptions), a new solveset module that will
eventually supersede the current solve module.

Because this will be a 1.0 release, and because there are already so
many major changes, I'd like to push any other changes that are
slated, especially breaking changes. Once 1.0 is out, the goal is to
have releases happen much more often, with less fanfare.

I will be able to dedicate a large amount of time for this, but I need
your help in identifying issues that should be solved for the release.
Please comment on the release issue
(https://github.com/sympy/sympy/issues/9891) and add issues to the
release milestone (https://github.com/sympy/sympy/milestones/1.0). If
something isn't in that milestone, I will assume that it isn't
blocking the release.

The most important things for the release are any changes that break
compatibility, and critical bug fixes. Also any changes to API that is
new since 0.7.6 should be considered especially important, so that we
can avoid breaking stable API at all.

My current, conservative goal is to start a release branch
(effectively freezing it from noncritical changes) in a month's time
(mid-November).

Aaron Meurer

[Björn Dahlgren]

On Friday, 16 October 2015 22:19:50 UTC+2, Aaron Meurer wrote:

As many of you know, I am starting a new research position at the
University of South Carolina with Anthony Scopatz's new research
group, ERGS.

That sounds exciting, I wish you the best of luck. That also got me thinking:
what about assigning a DOI for the v1.0 release?
https://guides.github.com/activities/citable-code/

[Aaron Meurer]

I enabled sympy/sympy on zenodo.org. I guess it should happen
automatically when I make the release.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sympy+un...@googlegroups.com.
> To post to this group, send email to sy...@googlegroups.com.
> Visit this group at http://groups.google.com/group/sympy.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/sympy/88faf01c-7f09-4e1f-b3c6-843b8c6dc314%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.