Open jctanner opened 6 years ago
Sounds sensible and useful:
Q: Are you thinking a single label that applies if either controller or remote is $operatingsystem? Q: Would we just look for certain strings in the Issue/PR body Q: Can we infer OS from Python paths (for Ansible Controller being run on !Linux)
ansible --version
ansible 2.8.0.dev0 (BOTMETA-plugins fbd1e6d7f9) last updated 2018/09/11 19:21:56 (GMT +100)
config file = /etc/ansible/ansible.cfg
configured module search path = [u'/home/johnb/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
ansible python module location = /home/johnb/git/ansible-inc/ansible-workspace-5/lib/ansible
executable location = /home/johnb/git/ansible-inc/ansible-workspace-5/bin/ansible
python version = 2.7.12 (default, Dec 4 2017, 14:50:18) [GCC 5.4.0 20160609]
BSD:
python version = 3.6.6 (default, Aug 7 2018, 12:18:31) [GCC 4.2.1 Compatible FreeBSD Clang 4.0.0 (tags/RELEASE_400/final 297347)]
Discussed with Tanner, this is low priority
probably make a bot recognize known tags with +tag / -tag pattern from contributors (collaborators) as well (not only from admins) and mark issue accordingly ?
thanks
I'd like to have labels applied to issues for the uncommon operating systems, such as aix, hpux, solaris, etc. This will allow me and other managers to quickly determine how much work is in the backlog for any given OS and what the cost of support might be.