CLN/DOC: update version numbers
@cpcloud complete side note.....prob should add the `version added` directive wherever possible in the docs...course one would have to go back over the whatsnews/release notes and manually add...maybe add this as a good first pr project?
 indeed maybe we should be more strict about PRs using as well, going forward?
 well..its only in the main docs....I always forget about it....its a nice thing to do though
 ok, not super important so will do if i remember from now on maybe i will add a shell script to run when i write a commit message that tells me about it
 why don't you rebase and try to get this in...?
 damn i really screwed that up. i thought there would be a bunch of merge conflicts so i did `git rebase -s ours upstream/master`. horrible idea since of course after RTFM i see that that discards the patch from my branch.
 git reflog is your friend :)

On Wed, Jun 26, 2013 at 12:14 PM, Phillip Cloud notifications@github.comwrote:

> damn i really screwed that up. i thought there would be a bunch of merge
> conflicts so i did git rebase -s ours upstream/master. horrible idea
> since of course after RTFM i see that that discards the patch from my
> branch.
> 
> —
> Reply to this email directly or view it on GitHubhttps://github.com/pydata/pandas/pull/4038#issuecomment-20060178
> .
 @jtratner oh gosh i feel like such a git n00b, thanks!
 and ....we're back
 looks reasonable
