19:00:02 #startmeeting Ansible Molecule Working Group 19:00:02 Meeting started Wed Apr 3 19:00:02 2019 UTC. 19:00:02 This meeting is logged and archived in a public location. 19:00:02 The chair is gundalow. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:02 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:02 The meeting name has been set to 'ansible_molecule_working_group' 19:00:09 #chair decentral1se themroc zbr 19:00:09 Current chairs: decentral1se gundalow themroc zbr 19:00:17 Hi everybody! 19:00:21 who else is around? 19:00:27 hullo hullo folks 19:00:36 hi 19:02:13 #info Agenda https://github.com/ansible/community/issues/427 19:02:32 #info https://github.com/ansible/community/issues/427#issuecomment-475899977 19:02:37 that was my last "things in my head" 19:02:43 for the agenda 19:02:59 maybe a bit "meta" if there are other discussions 19:03:22 #topic Prioritise session for 2.21 (kick off the rest to 2.22) 19:03:28 ello 19:03:28 Sound like a good place to start 19:03:35 #chair smyers 19:03:35 Current chairs: decentral1se gundalow smyers themroc zbr 19:03:37 heyo 19:04:04 #info 2.21 Plan so far https://github.com/ansible/molecule/projects/4 19:04:16 yep: how to slim this down and keep focus 19:05:17 also, let's keep in mind anything we merge now will be in 2.20 since there will be a packaging re-release 19:05:26 so we need to hold off 19:05:48 so a 2.20.1 ? 19:06:29 not sure really, waiting for webknjaz 19:06:32 +1 for that semver .z release :) 19:07:45 ok, can we punt out of this release 19:07:47 https://github.com/ansible/molecule/pull/1701 19:08:03 https://github.com/ansible/molecule/issues/1744 19:08:25 https://github.com/ansible/molecule/issues/1721 19:08:39 (To-Do column) 19:08:53 1701: maybe just close this PR if we reached the consensus that it is eventually not desirable? 19:09:40 I am so sorry to be the one who does PR just to have a place for debate and consensus convergence :/ 19:09:46 [molecule] decentral1se closed issue #1752: improve testing experience for developers - https://git.io/fjI5t 19:10:17 I'd be fine with that since it seems to be blocked 19:10:23 I've pushed a few times to see someone take it up 19:11:58 I might also drop https://github.com/ansible/molecule/pull/1491 as per comment from zbr 19:12:00 themroc, I think that strategy worked in the tox testenv PR you put up (#1887) 19:12:06 but I digress :) 19:13:05 [molecule] themr0c closed pull request #1701: [ON HOLD] 1699 lint at 160 - https://git.io/fjI5m 19:13:40 :) 19:14:21 ok cool 19:15:14 https://github.com/ansible/molecule/pull/1899 should bring some performance improvements, but i have to do some rework on it as i broke some functional tests 19:15:25 which was not the intent 19:16:01 I've pushed off all I've marked so far ... shout if you disagree 19:16:20 themroc: I think we should make that one work 19:16:27 let's keep it. will offer solid improvements 19:17:00 (it has to be proven first) 19:17:22 well, telling from the first experiments ... 19:17:29 OK, I've pushed off everything I can see 19:20:23 anything more on that? 19:22:56 https://github.com/ansible/molecule/issues/1834 -> how is the RTD setup done? 19:23:29 yeah no idea, gundalow? 19:24:06 smyers: #1903 got merged btw 19:24:58 Yeah, I updated the depends PR to basically say I'll fix it after this meeting :) 19:27:54 lovely job 19:29:21 themroc: decentral1se I have RTD powers, looking 19:29:45 As we don't have branches I'm not sure what the solition is there 19:30:32 thanks 19:30:34 ah right ... 19:30:39 https://docs.readthedocs.io/en/stable/versions.html We also create a stable version, if your project has any tagged releases. stable will be automatically kept up to date to point at your highest version. If you want a custom stable version, create either a tag or branch in your project with that name. 19:30:52 I gotta jump, take it easy folks 19:30:55 ack 19:31:25 might be a matter of telling rtd to default to stable instead of latest if the stable docs tag is working right 19:31:47 smyers, +1 19:31:53 https://molecule.readthedocs.io/en/2.20/ exists 19:31:54 Which...maybe it does? https://molecule.readthedocs.io/en/stable/configuration.html 19:32:06 I can take a look at that 19:32:35 When a user hits the root URL for your documentation, for example http://pip.readthedocs.io/, they will be redirected to the Default version. This defaults to latest, but could also point to your latest released version. 19:34:59 nod, I'll have a play 19:38:39 gundalow: in Admin > Advanced Settings > Default version 19:39:10 you can choose between latest and stable 19:41:25 https://docs.readthedocs.io/en/stable/config-file/v2.html#migrating-from-the-web-interface states that this is a setting not supported via the config file 19:42:22 themroc: set to `stable` 19:42:28 \o/ 19:43:04 Is that right/ 19:43:43 I need to ditch now 19:44:35 https://molecule.readthedocs.io redirects to stable now 19:44:38 so that's fixed 19:45:52 ah, so stable = `99e03ea1`, which is the SHA of 2.20. So that looks good 19:46:00 themroc: smyers Nice work :) 19:47:34 Comment added on issue 19:47:39 ok, going to close now 19:47:40 gundalow, + " Show version warning" ? 19:47:45 themroc: oh 19:48:30 themroc: that's currently enabled 19:49:00 ah yes https://molecule.readthedocs.io/en/2.19/configuration.html 19:49:28 i was wondering how you switch between versions, that's an acceptable answer 19:49:46 " You are not reading the most recent version of this documentation. 2.20 is the latest version available." 19:50:55 seems perfect 19:52:49 Ace, thanks all 19:52:53 #endmeetin 19:52:54 #endmeeting