> I'm really sad that a change with the potential to affact a very large user > group was made without proper documentation. I know that developers have the > curse of knowledge but when the behaviour changes the documentation has to be > changed, too. Well, an issue is open for that. Let's see when it could be > solved.
We knew it would affect a good chunk of users, its always a balancing act, what is the right thing to do? how many people will this inconvenience? is there a less intrusive solution? Again, I think aside from the 'future' inconvenience of having to 'opt in' to this feature, most of the problem was a misunderstanding on the behaviour going away permanently. > I hope you could keep your promise: me too, just to confirm, no one has made the case to do otherwise, most of the problem was confusion due to a bug (deprecation always showed, now fixed) and my poor wording of warnings and docs (which is still being worked on). -- ---------- Brian Coca -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CACVha7dJ20m7%3DxjOstOfB3jh4U6MB5Kn6zfiy3ktfVv6yGHMWA%40mail.gmail.com.
