Standing Agenda, Public Core Meeting Meeting - November 2016 #140
Comments
From previous agenda ticket, @gundalow:
Discussed during 2016-11-10:
|
ansible/ansible-modules-core#5388 MySQL Security issue Current status: jmainguy and WouterOosterveld are discussing in the ticket. Discussed during 2016-11-10:
Discussed during 2016-11-15:
Jmainguy and WouterOosterveld are now happy that the change is ready to merge. jimi-c merged and backported to stable-2.1 and stable-2.2 |
Decided that current three release sequence is sufficient and not emitting deprecation notices doesn't make much sense for the majority of use-cases. Added a workaround if the user's site wants that workflow. |
merged by mattclay |
Proposal: ansible-config Discussed (lots) during 2016-11-15:
continued discussion necessary |
Discussed during 2016-11-10:
Discussed during 2016-11-15:
|
Discuss implementation of ansible/ansible#18501 - This is to be discussed in 2016-11-22 meeting. |
#143 Discussed during 2016-11-17 Core meeting |
No Public Core Meeting on Thursday 24th November |
From discussion in networktocode. Can we have a few failure message that returns some extra state, e.g Would return something along the lines of If agreed we need to update the existing modules (and inventory scripts) as well as developing_modules.html Update Discussed 29-Nov-2016 No definite conclusion but:
|
More details about upcoming repo merge |
Inability to find modules in subdirectories of "library" has been gaining more and more attention We need to decide if we'll accept a patch or not and then give guidance in the issue or close it. |
It's now December so closing this I've carried over
MEETING CLOSED December's Agenda #147 |
#Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped.
If your IRC nick is different from your Github username, leave that as well.
See https://github.com/ansible/community/blob/master/MEETINGS.md for the schedule
Once an item has been addressed it should get
strike-though~~strike-though~~
The text was updated successfully, but these errors were encountered: