1.0 release process started

[Aaron Meurer]

I have started the SymPy 1.0 release process. There is now a branch
1.0 in the SymPy repo. You may continue to merge changes into master
normally. A release candidate will be coming soon.

You may continue to make pull requests to master and merge them normally.

If you have a critical change that you feel needs to go in 1.0, please
LET ME KNOW by commenting on
https://github.com/sympy/sympy/pull/10632. Such changes will need to
be made against the 1.0 branch. Please do not merge any changes into
that branch without letting me know, as I will be working on that
branch to fix up some final things for the release.

Hopefully there shouldn't be any major changes needed, as everything
in the 1.0 milestone on GitHub has been fixed.

Aaron Meurer

[Aaron Meurer]

Also feel free to edit the release notes
https://github.com/sympy/sympy/wiki/Release-Notes-for-1.0. I'm sure
some things are missing.

Aaron Meurer

[Ondřej Čertík]

On Fri, Feb 19, 2016 at 10:29 AM, Aaron Meurer <asme...@gmail.com> wrote:
> Also feel free to edit the release notes
> https://github.com/sympy/sympy/wiki/Release-Notes-for-1.0. I'm sure
> some things are missing.

What do you mean by:

"The new solveset function is a planned replacement for solve. While
solve is not yet deprecated,"

it looks like the sentence is not finished.

What is the plan with solve? We should deprecate solve, and then
rename solve_set to solve.

Ondrej

>
> Aaron Meurer
>
> On Fri, Feb 19, 2016 at 11:27 AM, Aaron Meurer <asme...@gmail.com> wrote:
>> I have started the SymPy 1.0 release process. There is now a branch
>> 1.0 in the SymPy repo. You may continue to merge changes into master
>> normally. A release candidate will be coming soon.
>>
>> You may continue to make pull requests to master and merge them normally.
>>
>> If you have a critical change that you feel needs to go in 1.0, please
>> LET ME KNOW by commenting on
>> https://github.com/sympy/sympy/pull/10632. Such changes will need to
>> be made against the 1.0 branch. Please do not merge any changes into
>> that branch without letting me know, as I will be working on that
>> branch to fix up some final things for the release.
>>
>> Hopefully there shouldn't be any major changes needed, as everything
>> in the 1.0 milestone on GitHub has been fixed.
>>
>> 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 https://groups.google.com/group/sympy.
> To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CAKgW%3D6%2BqCwAEKDU%3DQHt0Yf7Ee43i1%3D2CwfFD3g2VBebCfSN9rw%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

[Aaron Meurer]

On Fri, Feb 19, 2016 at 2:25 PM, Ondřej Čertík <ondrej...@gmail.com> wrote:
> On Fri, Feb 19, 2016 at 10:29 AM, Aaron Meurer <asme...@gmail.com> wrote:
>> Also feel free to edit the release notes
>> https://github.com/sympy/sympy/wiki/Release-Notes-for-1.0. I'm sure
>> some things are missing.
>
> What do you mean by:
>
> "The new solveset function is a planned replacement for solve. While
> solve is not yet deprecated,"
>
> it looks like the sentence is not finished.
>
> What is the plan with solve? We should deprecate solve, and then
> rename solve_set to solve.

Ah, good catch. I guess I got distracted and forgot to finish the sentence.

solveset() is not yet ready to completely replace solve() (there are
still many equations that solve() can solve but solveset() can't).
However, when it is ready, we will recommend it, and probably
deprecate solve(). We can't deprecate something that isn't ready to be
replaced yet, though, which is why solve() is not yet deprecated (see
https://github.com/sympy/sympy/wiki/Deprecating-policy). The two
functions have different interfaces, which is why renaming one to the
other would be a breaking change.

Here is what the documentation says
https://github.com/sympy/sympy/pull/10131/files.

I'll update the release notes.

Aaron Meurer

> To view this discussion on the web visit https://groups.google.com/d/msgid/sympy/CADDwiVDfFnumK_iBa2mu8_we_WxanrrRtXGRshdue3XTQF%2BsWA%40mail.gmail.com.

[Aaron Meurer]

Also, the front matter of
http://docs.sympy.org/dev/modules/solvers/solveset.html has a much
more in-depth description of solve() vs. solveset().

Aaron Meurer