Open Stack

Thanks for reaching out.

For what it's worth, you can think of these roles as internal APIs
that we're removed that we replaced by other ones.  They were never
meant to be directly consumed by our users, they only exist to be able
to "refactor" our code

On Mon, Apr 6, 2020 at 9:37 AM Jeremy Stanley <fungi at yuggoth.org> wrote:
>
> On 2020-04-06 13:05:22 +0100 (+0100), Sean Mooney wrote:
> [...]
> > im not sure if this applies to roles but for most "features" in
> > openstack we deprecate at least one cycle before removal
> [...]
>
> This is a governance tag projects can choose to assert:
>
> https://governance.openstack.org/tc/reference/tags/assert_follows-standard-deprecation.html
>
> It's service specific and talks about API features, though I suppose
> the concepts there could be adapted to things like orchestration and
> deployment tooling. Also note that OpenStackAnsible doesn't assert
> this tag on any deliverables so are free to disregard the guidance
> therein. That said, it's for sure a bit of an error in terminology
> to say you're "deprecating" something and removing it in the span of
> the same release. That's not deprecating, it's just plain removing.
> --
> Jeremy Stanley



-- 
Mohammed Naser — vexxhost
-----------------------------------------------------
D. 514-316-8872
D. 800-910-1726 ext. 200
E. mnaser at vexxhost.com
W. https://vexxhost.com