Prepare 1.0

[kadamwhite]

Our new APIs have been working well in client projects running off of prerelease branches; I propose we tag 1.0 to enable the plugin to move forward predictably.

Note

This deliberately doesn't remove the deprecated methods, in order to permit projects to update to 1.0 for both APIs if needed. I'm open to feedback on whether that's a bad idea and we should drop the deprecated methods now.

[goldenapples]

Oh, if we do this, we might want to follow up on humanmade/altis-cms#941, which just relaxed the version dependency to 0.8.0.

[kadamwhite]

@goldenapples Is your recommendation to leave the deprecated methods in, and then to make sure Altis is using 1.0 for maximum flexibility, then?

[kadamwhite]

From @goldenapples

I was just saying - we've finally gotten a bump to the version constraints in Altis. If we're planning on deprecating any functionality in a 1.0 version, it might be good to see which of that functionality Altis depends on first.
But if the version bump doesn't involve deprecating anything and we're just saying that v1.0 is going to be stable, then we should follow up the release with another version bump in altis-cms.

We'll go with option 2, leaving the APIs in for now :)