-
Notifications
You must be signed in to change notification settings - Fork 144
Public Ansible Project Meeting Agenda - Mar 2019 #450
Comments
Carry overs:
|
|
|
|
Using a workaround for the time being, going to revisit after freeze after I've done some performance testing |
|
|
Meeting ended Tue Mar 5 20:12:26 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
|
|
|
|
Meeting ended Tue Mar 19 20:03:41 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
|
|
Meeting ended Thu Mar 21 15:37:12 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Ansible 2.8.0 delayAs some of you may have noticed, Ansible-2.8.0-alpha1 has been The new schedule there will be: 2019-03-28 Alpha 1 Core freeze As always the |
|
IRC:
|
Meeting ended Tue Mar 26 19:54:57 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Meeting ended Thu Mar 28 16:06:15 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
Agree where Plugin metadata should come from |
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/README.md for the schedule
Once an item has been addressed it should get strike-through.
(Migrated from a previous agenda)
The text was updated successfully, but these errors were encountered: