DOC: clean up 0.14.1 whatsnew file
- removed the sections with no entries
- removed whitespace
- moved some entries from API-changes to Enhancements/Big fixes when it was not really a backwards incompatible change or if it was not clear what the relevant change was for users (and for the offsets normalize issue I rewrote it)

Highlights should still be written to include here and in the release.rst

something wrong with the rendering here: http://pandas-docs.github.io/pandas-docs-travis/cookbook.html#aliasing-axis-names (it cuts off for some reason)....can you take a look? thxs
 I think I fixed it with https://github.com/pydata/pandas/commit/9d71aaedd08f5fad15795b04a8c997bfee67f896 (just a temp fix, should look more into it as it is probably a bug in the ipython directive)
 interesting, so function definitions not handled properly....ok!
 Hmm, not as such, eg http://pandas-docs.github.io/pandas-docs-travis/enhancingperf.html#pure-python it renders OK, so it should still be a slightly different issue. But in any case, my hack should let it render OK.
 @jreback Should there be som 'highlights'? (also for in the release message)
- New Documentation section on :ref:`Options and Settings <options>`
- select_dtypes function
- Support for dateutil timezones
- lots of bug fixes
 sure that would be gr8!
 Other things you think of?
 maybe perf improv
sem
comment parsing (to skip lines)
 updated
 Done.
 Just wait a moment for the doc build to see if it looks OK, then should be good to go!
 just ping when u r satisfied 
 looking good
 pls upload docs when you can! ping and i'll change the html file (or you can if you u want).
 seems the offsets (normalize) is in BOTH API and enhancements sections in whatsnew? (its slightly different), did you mean that?
 yep, I did that on purpose (because in the enhancement section it is just about the normalize keyword, while in the API it is about the changed behaviour for some offsets). Is it confusing? I can always change it.
 I would take out the section in Enhancements and leave the API section.
 The entry that is now in Enhancements is the original message, but while cleaning up the whatsnew docs, I first moved it from API changes to Enhancements because it said nothing about an API change but just the introduction of a keyword, but when I looked at the connected issue, I saw there was actually an API change, so added another entry in API changes to explain the actual change .. 
So I wouldn't delete one of the two (as they are saying different things), but maybe it is less confusing that I merge both in one entry
 ok 2....its just that on a quick read they look very similar
 restart the web server to reflect the new docs after you upload

`python upload.py` from `~/www` dir
 What do you mean exactly? For the website, or for the docs?
 I think if you change the docs, need to restart the web server, it should reflect immediately I think
 If I tried it in my browser, it was directly changed (just refreshed the page)
 really? did you push a new commit anyhow?
 Looking at the upload.py script, and it seems similar command as in doc/make.py

So I just build the docs locally and then upload them, all with the make.py script (eg the `upload_stable` option etc). And that seems to work for me (also last time with 0.14 I did not do anything else), as it is directly reflected on the website.
 it pushes it to the actual server
it will ask for the pw an say it's uploaded
I think it's some kind of setuid script
 well, but I suppose doc/make.py does the same thing (it is a similar rsync command to push it to `/usr/share/nginx/pandas`)
 Did you notice a problem with the website/docs?
 they look fine, jus not 100% what you changed
