new release todo

[Ondřej Čertík]

Hi,

Tests seem to be working in master in Travis:

http://travis-ci.org/#!/sympy/sympy/builds

as well as my computer. What has to be done to make the release?
Are there any PR's that should go in?

Unless there is somebody else interested, I will go ahead with this release.
It should be 0.7.2, right? Here is my plan:

* I'll release rc1
* we'll have source tarball, win32.exe, the documentation
* I'll follow (possibly update) the
https://github.com/sympy/sympy/wiki/New-Release
* from the source tarball, one can run the bin/use2to3 script to get
Python 3.x support,
but it takes a long time. So I plan to also release python 3.x source
tarball and python 3.x
win32.exe.

That way people that want to have one source tarball for all Python's
will just use the regular
tarball (that can do python 2.x immediately and then they need to run
a script to get 3.x support).
People that just want 3.x support can just grab the 3.x tarball (or
.exe on windows).

Ondrej

[Tom Bachmann]

I think there may be some 3.3 problems with hash randomization still.
For example 1462. Also, when running use2to3, there is a problem in some
docstring, which I think 1463 is trying to address.

Probably aaron and smichr know more.

[krastano...@gmail.com]

> I think there may be some 3.3 problems with hash randomization still. For
> example 1462. Also, when running use2to3, there is a problem in some
> docstring, which I think 1463 is trying to address.

My test-runner has randomizations turned on as suggested by Aaron, so
if something is failing in it that means it will fail in 3.3 or when
ran with `python -R`

Additionally, the new plotting module is still rough around the edges.

Finally, the gsoc work of some of us (at least the diffgeom module and
the categories module) is only partially done/merged (however all this
can just be excluded from setup.py).

[Aaron Meurer]

And there is a problem with building the docs, which should be fixed.

I would do it like it says
https://github.com/sympy/sympy/wiki/new-release. Create a new branch
0.7.2 in the official repo. Then, all release blocking PRs should go
as pull requests to that branch. Development on master can continue
as usual. Also, I was thinking that you should create a pull request
to merge 0.7.2 into master right away, so that we can run the bot
tests on it (but don't merge it until the release is finished).

I'll help out too. Basically everything that you need to do is on that
wiki page. Just let me know what you plan to do yourself, and what
you want me to do. The hardest part at this point is actually the
stuff at the bottom, after you've released, because there are a dozen
websites and packages to update, so any help there is the most
appreciated.

Also, go through the 0.7.2 blocker issues and make sure that either
they are fixed or can be reasonably postponed.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To post to this group, send email to sy...@googlegroups.com.
> To unsubscribe from this group, send email to
> sympy+un...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/sympy?hl=en.
>

[Bharath M R]

Additionally, the new plotting module is still rough around the edges.

How many days we have for the 0.7.2 release? I really don't know how

the releases work.

I am looking to change the api of plot.

There are some problems with the old plotting module(pyglet). I remember

Chris mentioning that it throws an error in [1]. So the plotting module changes

will block the release.

[1]https://github.com/sympy/sympy/pull/673 near the end.

I am not able to link comments. 

[Sergiu Ivanov]

On Tue, Aug 7, 2012 at 8:55 PM, Bharath M R <catchmr...@gmail.com> wrote:
>
> [1]https://github.com/sympy/sympy/pull/673 near the end.
> I am not able to link comments.

This is a bit off-topic, but I think it might be useful.

To link to a comment, use the timestamp in the top-right corner. For example:

https://github.com/sympy/sympy/pull/673#issuecomment-6246100

As for the release, I think the categories modules can already be
included after the diagram drawing pull request [0] has been merged.
I am equally supportive of the idea of omitting this module in the
coming release and keeping it for the yet next release.

Sergiu

[0] https://github.com/sympy/sympy/pull/1430

[Ondřej Čertík]

On Tue, Aug 7, 2012 at 10:55 AM, Bharath M R <catchmr...@gmail.com> wrote:
>
>
>> Additionally, the new plotting module is still rough around the edges.
>
>
> How many days we have for the 0.7.2 release? I really don't know how
> the releases work.

Since I'll be doing it, it's up to me how I do it.

>
> I am looking to change the api of plot.
> There are some problems with the old plotting module(pyglet). I remember
> Chris mentioning that it throws an error in [1]. So the plotting module
> changes
> will block the release.
>
> [1]https://github.com/sympy/sympy/pull/673 near the end.
> I am not able to link comments.

How much time do you think you need to get this fixed?
Is this the error that you are talking about:

http://code.google.com/p/sympy/issues/detail?id=3351

Let's get it fixed before the release.

Ondrej

[Aaron Meurer]

On Tue, Aug 7, 2012 at 11:55 AM, Bharath M R <catchmr...@gmail.com> wrote:
>
>
>> Additionally, the new plotting module is still rough around the edges.
>
>
> How many days we have for the 0.7.2 release? I really don't know how
> the releases work.

The way it works is that when we're ready to start doing it, we create
a branch called 0.7.2 off of master, and all release stuff happens in
that branch. Development in master continues as normal, but any new
stuff there will go in the next release. Changes that should go in
the release (which should only be release blockers) can be merged into
the 0.7.2 branch. So the question you care about is not when the
release will happen, but when the release branch will be made.

Aaron Meurer

>
> I am looking to change the api of plot.
> There are some problems with the old plotting module(pyglet). I remember
> Chris mentioning that it throws an error in [1]. So the plotting module
> changes
> will block the release.
>
> [1]https://github.com/sympy/sympy/pull/673 near the end.
> I am not able to link comments.
>

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/sympy/-/bdzS86n-4hQJ.

[Bharath M R]

How much time do you think you need to get this fixed?
Is this the error that you are talking about:

http://code.google.com/p/sympy/issues/detail?id=3351

Yes. I haven't used the old plotting module, so I don't know

how it works. I will try digging into the code and fixing it. 

[Bharath M R]

The way it works is that when we're ready to start doing it, we create
a branch called 0.7.2 off of master, and all release stuff happens in
that branch.  Development in master continues as normal, but any new
stuff there will go in the next release.  Changes that should go in
the release (which should only be release blockers) can be merged into
the 0.7.2 branch.  So the question you care about is not when the
release will happen, but when the release branch will be made.

Are we including the new plotting module, with a warning saying that it can be changed,

or we are not including it at all? The new API changes might take some time before it

gets merged right?

Thanks, 

Bharath M R 

[Aaron Meurer]

I wouldn't worry about that too much. It's not a release blocker.

Aaron Meurer

> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/sympy/-/TX1c4OM29L8J.

[Aaron Meurer]

I guess if it's too much work we can do that. Is it a lot of work?

Aaron Meurer

>
> Thanks,
> Bharath M R

>
> --
> You received this message because you are subscribed to the Google Groups
> "sympy" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/sympy/-/pNXBnO0B98EJ.