On 06/17/14 20:13, Drew Northup wrote:
> On Monday, June 16, 2014 9:14:17 PM UTC-4, Michael DeHaan wrote:
>
>     Rather than pick up code complexity for an alias feature, since
>     this may confuse module developers - for this we're going to just
>     rename them at some point with a future release.
>
>     I'm not positive it's time just yet.   But soon.
>
>
> Looking at http://semver.org/ (the Semantic Versioning manifesto), I'd
> say you're perfectly justified in waiting until 2.x to remove things.
>
> It isn't quite so clear that "duplicating" things is out and out bad,
> but it would make far more sense to introduce a "refactored" version
> of OpenStack modules (I'd prefer a unified block personally, instead
> of one for each service) as a minor point revision instead of just
> doing so randomly. Alas, that leaves behind the old, messy (and
> deprecated) piles of API calls until the next major release. It does
> however give the opportunity to warn people that they are using
> deprecated modules.
>
> SO, if everybody out there would just give Michael and his crew some
> space (and join the developer community), they are going to have the
> best chance of managing this in a sane manner. As I've just shown,
> this isn't a cut-and-dry "only one way is right" situation. Each
> community needs to figure out what is right for itself.
>

I think by bringing this old thread back to life, Monty wanted us not to
think about the particular case with openstack modules (decisions for
this have already been taken after all), but make us think about the
general need of having a deprecation warning mechanism and aliasing for
modules. On one hand, code complexity could possibly confuse some module
developers as Michael said. On the other hand, new users could be
mislead by deprecated names. In my opinion, the second is worse because
it affects more people. That said, I don't think the need for such a
feature comes up often enough to give it a higher priority.


>
>     On Mon, Jun 16, 2014 at 2:49 AM, 'Petros Moisiadis' via Ansible
>     Project <[email protected] <javascript:>> wrote:
>
>         On 06/15/2014 10:42 PM, Monty Taylor wrote:
>         > ...
>         > SO - and please tell me if I'm  on crack here - would you be
>         open to
>         > adding a general ansible feature  similar to aliases but for
>         module
>         > names? That way we could more  gracefully handle renames
>         that come up
>         > allowing people a transition  period.
>         > ...
>
>         I had not followed the thread at that time, but reading it now, I
>         wondered why nobody had not suggested that, until I saw your
>         proposal.
>         Keeping backwards compatibility is good and is a must. Keeping
>         backwards
>         compatibility and also not forcing to use or misleading users with
>         deprecated names or terms (or technologies) is even better. A
>         deprecation warning is a good addition for both old and new users.
>
>         --
>         You received this message because you are subscribed to the
>         Google Groups "Ansible Project" group.
>         To unsubscribe from this group and stop receiving emails from
>         it, send an email to [email protected]
>         <javascript:>.
>         To post to this group, send email to
>         [email protected] <javascript:>.
>         To view this discussion on the web visit
>         
> https://groups.google.com/d/msgid/ansible-project/539EA19D.1070606%40yahoo.gr
>         
> <https://groups.google.com/d/msgid/ansible-project/539EA19D.1070606%40yahoo.gr>.
>         For more options, visit https://groups.google.com/d/optout
>         <https://groups.google.com/d/optout>.
>
>
> -- 
> You received this message because you are subscribed to the Google
> Groups "Ansible Project" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [email protected]
> <mailto:[email protected]>.
> To post to this group, send email to [email protected]
> <mailto:[email protected]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/ansible-project/7bd6c470-b2d5-4f53-87d0-c988cd93cf3c%40googlegroups.com
> <https://groups.google.com/d/msgid/ansible-project/7bd6c470-b2d5-4f53-87d0-c988cd93cf3c%40googlegroups.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/ansible-project/53A084AC.6090709%40yahoo.gr.
For more options, visit https://groups.google.com/d/optout.

Reply via email to