| === blackboxsw changed the topic of #cloud-init to: 21.2 (May 6) | file a bug: https://bugs.launchpad.net/cloud-init/+filebug | pull-requests: https://git.io/JeVed | meeting minutes: https://goo.gl/mrHdaj | next office hours: June 15 17:15 UTC | ||
| blackboxsw | community-notice: updated cloud-init drop in office hours meeting to +2 hrs from now | 15:15 |
|---|---|---|
| blackboxsw | falcojr: what do you think about the upstream default branch renaming master -> main. The email and discourse post have been out for 12 days with no responses (and I stated we'd make the change in 2 weeks). Should we wait 2 more days? | 15:55 |
| falcojr | yeah, I was looking at that yesterday. Doing it on Thursday sounds good | 15:58 |
| blackboxsw | ok thursday it is. | 15:59 |
| blackboxsw | #startmeeting cloud-init bi-weekly office-hours | 17:17 |
| meetingology | Meeting started at 17:17:44 UTC. The chair is blackboxsw. Information about MeetBot at https://wiki.ubuntu.com/meetingology | 17:17 |
| meetingology | Available commands: action, commands, idea, info, link, nick | 17:17 |
| blackboxsw | community-notice: Hi cloud-initers, welcome to another office hours meeting. cloud-init committers will be around for the next hour to field any discussions. answer questions or put some eyes on PR reviews or bugs that spark your interest. | 17:20 |
| blackboxsw | We host this meeting to unblock, or unstick anybody toying around with cloud-init, as well as to update thecloud-init devs on recent changes in cloud-init upstream | 17:21 |
| blackboxsw | #chair falcojr | 17:21 |
| meetingology | Current chairs: blackboxsw, falcojr | 17:21 |
| blackboxsw | We just published a little discourse post describing that cloud-init upstream version 21.2 has now cleared SRU validation for Ubuntu Bionic(16.04) Focal (20.04) Groovy (20.10) and Hirsute (21.04) https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730 | 17:25 |
| blackboxsw | #link https://discourse.ubuntu.com/t/cloud-init-status-06-15-2021/22730 | 17:25 |
| blackboxsw | in that SRU, were some ssh_key handling improvement, Azure SSH key processing, Azure userdata updated ingested from IMDS and new support for Vultr cloud platform. | 17:26 |
| blackboxsw | Thanks all for those contributions! | 17:27 |
| blackboxsw | one other interesting thing to note: 4 days ago I was banned from FreeNode. falcojr did this happen to you too? "Connection closed unexpectedly: You are banned from this server- [#1480] Contact support@freenode.net (2021/6/11 05.18):" | 17:30 |
| falcojr | blackboxsw: no, that's weird. I know they completely reset everything over there though. | 17:31 |
| blackboxsw | hrm maybe they tracked irc nicks that were advertizing moving to Libera.chat is the only thing I can think. will check it out | 17:32 |
| falcojr | at this point probably just best to cut ties completely | 17:33 |
| blackboxsw | yes agreed | 17:35 |
| blackboxsw | community-notice: reminder rename upstream/master -> upstream/main in 2 days. All active PRs will automatically be retargetted. For your local clones for cloud-init it should mean only the following: | 17:37 |
| blackboxsw | #link https://docs.github.com/en/github/administering-a-repository/managing-branches-in-your-repository/renaming-a-branch#updating-a-local-clone-after-a-branch-name-changes | 17:37 |
| blackboxsw | an email will be sent out to cloud-init@lists.launchpad.net | 17:40 |
| blackboxsw | with detailed instructions. | 17:40 |
| blackboxsw | #endmeeting | 19:47 |
| meetingology | Meeting ended at 19:47:12 UTC. Minutes at https://new.ubottu.com/meetingology/logs/cloud-init/2021/cloud-init.2021-06-15-17.17.moin.txt | 19:47 |
| blackboxsw | minutes published to https://cloud-init.github.io/ | 19:54 |
| blackboxsw | Next office hours: Tue June 29 UTC 17:15 | 19:57 |
| === blackboxsw changed the topic of #cloud-init to: 21.2 (May 6) | file a bug: https://bugs.launchpad.net/cloud-init/+filebug | pull-requests: https://git.io/JeVed | meeting minutes: https://goo.gl/mrHdaj | next office hours: June 29 17:15 UTC | ||
| blackboxsw | falcojr: during squash merge of cloud-init PRs should we be trying to redact the "SC-##" jira ticket references from commit summary? | 20:19 |
| blackboxsw | just wondering about usefulness/noise | 20:20 |
| blackboxsw | same for d/changelog etc. | 20:20 |
| falcojr | blackboxsw: yeah, I was thinking about that too. I merged one with it, but now I'm leaning towards no | 20:28 |
| blackboxsw | same here, we're avoiding that metadata in ua-tools commit messages and d/changelogs too | 20:28 |
| falcojr | if the jira was public, I'd keep it, but since it's not, if there's anything meaningful in the ticket that isn't captured somewhere public, that probably means we should capture it somewhere public | 20:28 |
| falcojr | (for ua, I'd definitely keep it since you don't have that problem there 😄 ) | 20:29 |
| blackboxsw | I've sync'd github cloud-init -> launchpad via our jenkins job to ensure ubuntu/bionic is updated before daily builds. watching https://code.launchpad.net/~cloud-init-dev/+recipe/cloud-init-daily-bionic to make sure we don't have failures | 20:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!