Increment release number to 3.1

[fonnesbeck]

Ready for release.

[fonnesbeck]

Merged. Will tag this as the release.

[junpenglao]

I think we should keep the 3.1 branch for readthedocs, @twiecki @owlas?

[ColCarroll]

Just needs a tag, I believe (this was helpful for checking out v3.0 to benchmark).

…

On Sun, Jun 25, 2017 at 2:18 PM Junpeng Lao ***@***.***> wrote: I think we should keep the 3.1 branch for readthedoc, @twiecki <https://github.com/twiecki> @owlas <https://github.com/owlas>? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#2353 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ACMHEGa1qms8ewIIbGjiK3v90U-kBfKYks5sHqRwgaJpZM4OEn2X> .

[fonnesbeck]

It's been tagged in master, after this branch was merged. You should be able to check it out by tag number (v3.1).

@junpenglao same thing there -- we should be able to use the tag for readthedocs.

[fonnesbeck]

$ git tag
v3.0
v3.0.rc1
v3.0.rc2
v3.0.rc3
v3.0.rc3_full
v3.0.rc4
v3.0.rc5
v3.0.rc6
v3.0alpha
v3.0beta
v3.0rc2
v3.1
v3.1.rc1
v3.1.rc2
v3.1.rc3
v3.1.rc4

That said, we can probably delete RC tags. I don't see much value in keeping them around.

[junpenglao]

Oh I see.
I think we can just keep the v3.0 and v3.1 tag for readthedocs.

[owlas]

Readthedocs will automatically point the stable docs to the most recent tag v3.1.rc4, which is the most important thing.

Could also have a separate branch 3.1.x for example if you wanted to make changes later.

But I think being able to toggle between stable and v3.0 will serve most users.