Add news for bump version

[DhairyaLGandhi]

Adds some missing NEWS items and prepares for patch bump.

I don't think we are breaking any API in this version, and if we want to include some PRs to this patch, it might be good to get some feedback on what we might want to include here.

[DhairyaLGandhi]

Needs #1840

[cossio]

This is ready now?

[darsnack]

I think this is good to go, but it would be nice to get #1849 in too. It should be done assuming tests clear. Can we merge this and I can rebase+merge #1849 before releasing?

[cossio]

@darsnack What's the problem with doing #1849 in a separate patch release? Both are non-breaking so it should be okay to just do one release and then another in case #1849 takes longer.

[darsnack]

No problem, just trying to avoid two patches in quick succession. But I really thought #1849 test would pass this time...let's just go ahead and release without it.

[cossio]

two patches in quick succession

I think there is nothing wrong with this. Could even be good. Quoting [1]

TL;DR; Every Pull Request should increment the version number in the Project.toml, and then you should register the release immediately after merging. Why do this? Because people are making PRs to your repo because they want that change. Don’t make them wait for you to tag a release. Also for all the normal advantages of continuous delivery.

(I'm waiting for some of the PRs already merged :) )

[1] https://www.oxinabox.net/2019/09/28/Continuous-Delivery-For-Julia-Packages.html.

[cossio]

Can we tag a release?

[darsnack]

Yes, I am just waiting on the CI to turn green (I know there's no logical reason it shouldn't, but it helps to be paranoid when releasing something to users).

[cossio]

You mean the green checkmark on the main repo page? I think it's already green.

[darsnack]

Yeah, I just triggered the release

[cossio]

Great, thanks