VisualMelon

@objorke I can confirm that I am `VisualMelon` on NuGet and MyGet. If you could ping me if/when you make any changes, I'll check they haven't gone to someone else...

I think I've accepted them all; shout if I've missed any.

Are there any scripts lying around for publishing everything, or is it necessary to manually upload them one at a time? Also, do we need to create new packages for...

Made a draft of a release document: https://gist.github.com/VisualMelon/e3b8eaceb91e2cd5430ee5687fc95649 This really doesn't feel like a point release, now that I've enumerate all the breaking changes. `Legends` alone is a big change...

> will there be packaging issues with nuget trying to pull OxyPlot.Core 2.1 as a dependency for OxyPlot.WPF 2.0? I think there will indeed. That is a serious problem which...

@Jonarw Re-reading that document again in less of a state of panic, I think you are right: it probably won't be an automatic break-all-the-code problem so long as we keep...

> Should we consider using 'Floating versions' (see above link for explanation) in future releases to avoid this kind of issue in the future? I'm not sure what you mean:...

@Jonarw @objorke today might as well be preview1 day. Any last-minute blocking concerns? Things to do: - [x] Create branch `release/v2.1.0-Preview1` - [x] update format changelog - [x] Finalise the...

Provisional update to the change log: https://github.com/VisualMelon/oxyplot/tree/release/v2.1.0-Preview1 I propose we merge the changes in `develop`, and create a new branch `release/v2.1.0-Preview1`. Fixes for 2.1 will be pushed to both branches,...

@Jonarw thanks. I guess I should stop fretting about the branches so much; we can always change them later. I'll probably do it tomorrow now when I'm more awake (also,...