Tagging 0.13

@jreback , good to go?

[jreback]

yep
pls confirm build clean on windows/sparc (not sure when that builds)

[jreback]

I think you are prob better writing the announcement, if that's ok?

I had updated the whatsnew top section, so can use some of that.

thxs

All green, tagged and pushed.

Let's hold off on merges that would not fit into a 0.13.1 for a couple of weeks
after the ANN goes out, in case a showstopper is reported. Otherwise, we're in 0.14 now.

I'll send out an ANN after the binaries are up.

[jreback]

@y-p awesome!

can you setup the new version? e.g. so it shows say 0.14-dev?

I am not sure how to do that....

also I should add the 0.14 whatsnew?

[jreback]

@y-p added whatsnew template (but didn't link it in yet so docs will build for 0.13 correctly), and wont' show up on dev till its switched over (so won't be confusing like last time)

Good thinking about the docs.

Re versions, that's what it's like now: comment. The version string is constructed using number
commits since latest git tag, which makes dev versions lex ordered. Up until 0.13.0rc1, you saw 0.12.0-700-foo etc'

Is it bad enough to warrent another change in versioning scheme?

[jreback]

hmm; right now mine shows this....shouldn't this be 0.14-dev-...?

In [1]: pd.__version__
Out[1]: '0.13.0rc1-149-g5b69a0c'

user1@localhost ~/src/pandas (git)-[master] % git describe
v0.13.0-1-gaf9c025

read: "The first commit following the v0.13.0 release"

Did you git pull --tags ?

[jreback]

yep...not updating ...I see it in git tag...

[jreback]

does this get updated automatically?

[goat-jreback-~/pandas] more pandas/version.py
version = '0.13.0rc1-149-g5b69a0c'
short_version = '0.13.0'

pandas/version.py is updated only when running setup.py. Did you do setup.py develop?

But there is a bug there:

user1@localhost ~/src/pandas (git)-[master] % cat pandas/version.py         
version = '0.13.0-1-gaf9c025'
short_version = '0.14.0'

I'll open an issue and deal with it soon.
#5799

[jreback]

gr8...I don't do develop