May 2021 - kata-dev - lists.katacontainers.io

Weekly Kata Herders
by Hunt, James O 17 May '21

17 May '21

Hi All, This week's Kata PR and issue herders are: - bergwolf (https://github.com/bergwolf) - Chelsea (https://github.com/cmaf) # Statistics ## Issues Issues opened last week: 28 Issues closed last week: 139 (Thanks Fabiano! ;) Open issues: 301 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 49 PRs closed last week: 65 Open PRs: 62 Open PRs (excluding dnm+wip): 42 # Get involved If you'd like to help get the open PRs merged and open issues resolved (or get involved in other ways with Kata), take a look at the contributing guide [2] and the rota process [3]. Any problems, just ask us [4]. Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/master/Rota-Process.md [4] - https://github.com/kata-cZhihong Yuontainers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Proposed release cadence
by Fabiano Fidêncio 13 May '21

13 May '21

Community, During Today's architecture committee meeting we discussed whether we should do feature or time based releases, and we kinda agreed that time based releases may be the way to go. We're releasing 2.1.0 this Friday, May 15th 2021, and I'd like to ask about the cadence we want to follow ... and whether we could stop maintaining the stable-2.0 branch at the moment we release 2.1.0. Can we consider doing a minor release every 8 weeks? If so, we could have: * 2.2.0-alpha0 -> Jun 11th * 2.2.0-rc0 -> Jun 25th * 2.2.0 -> Jul 9th * Stop maintaining stable-2.1 branch * 2.3.0-alpha0 -> Aug 6th * 2.3.0-rc0 -> Aug 20th * 2.3.0 -> Sep 3rd * Stop maintaining stable-2.2 branch * 2.4.0-alpha0 -> Oct 1st * 2.4.0-rc0 -> Oct 15th * 2.4.0 -> Oct 29th * Stop maintaining stable-2.3 branch ... Obviously, if we need to get a 3.x we can obviously re-evaluate the schedule, and also re-evaluate whether or not to maintain the 2.x releases. Ideas? Best Regards, -- Fabiano Fidêncio

3 2

Mass closing issues on 1.x repos
by Fabiano Fidêncio 12 May '21

12 May '21

James, This was discussed as part of the architecture committee meeting Today, May 11th, 2021, and we think that with the kata-containers 1.x reaching its EOL, we should mass-close the issues present in the 1.x repos. If I remember correctly, the last time it was done a script of yours was used to do so. Would it be possible to adapt such script to close the issue **with a comment**, saying that 1.x reached its EOL and that if the issue is still pertinent the owner should contact us to transfer the issue to the `kata-containers/kata-containers` repo? If so, would you have cycles to work on this? :-) Best Regards, -- Fabiano Fidêncio

2 1

Updated invitation with note: Kata Containers Perf Isolation Use Case Meeting @ Every 2 weeks from 11pm to 11:45pm on Wednesday 5 times (SGT) (kata-dev@lists.katacontainers.io)
by bergwolf＠gmail.com 11 May '21

11 May '21

This event has been changed with this note: "As just being discussed, let's extend the perf isolation use case meeting to 45 mins from next time and on." Title: Kata Containers Perf Isolation Use Case Meeting As discussed, let's split off and use this time slot to talk about the performance isolation use case.Zoom link (passcode: kata)https://zoom.us/j/98038141932gdoc link:https://docs.google.com/document/d/15Hc6DkJxLKev_MNKdN3OZWSpZxH3ch5TJ-… (changed) When: Every 2 weeks from 11pm to 11:45pm on Wednesday 5 times Singapore Standard Time (changed) Calendar: kata-dev(a)lists.katacontainers.io Who: * bergwolf(a)gmail.com - organizer * kata-dev(a)lists.katacontainers.io * Fabiano Fidêncio * Karl Heubaum * Liam Merwick * Boris Ostrovsky * Gupta, Sandeep * Wang, Arron * eric.g.ernst(a)gmail.com * Wang,Liang(ACG CCN) * aadam(a)redhat.com * azaalouk(a)redhat.com * Boeuf, Sebastien Event details: https://calendar.google.com/calendar/event?action=VIEW&eid=NDgyNmFzbXBqbjAz… Invitation from Google Calendar: https://calendar.google.com/calendar/ You are receiving this courtesy email at the account kata-dev(a)lists.katacontainers.io because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://calendar.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

2 1

Migration to Kata 2.0, and support timeline for 1.x
by Eric Ernst 11 May '21

11 May '21

Hey kata folk -- With 2.0 out now, we are focusing continued development and improvements on the 2.0 code base. As a result, in a prior architecture committee meeting discussion, we made the decision on a 6 month window (from release of 1.12) before stopping regular support of the 1.x (1.11 and 1.12 currently) branches. Based on this, here's a first heads up! We plan to deprecate support for 1.x on May 12th 2021. Thanks! Eric

2 2

Proposed GitHub projects
by Christophe de Dinechin 11 May '21

11 May '21

Hi, Following the discussions in the architecture committee meeting: - I removed the 1.11 project - I added a release 2.2 project, but did not populate it yet. Feel free to add features which you think belong to 2.2 https://github.com/orgs/kata-containers/projects/26 - I also added a Confidential Containers project. We discussed with Samuel about keeping track of what remains to be done, and I think this is one case where a "project" helps. https://github.com/orgs/kata-containers/projects/27 - Finally, a tentatively named "What's going on" project, which at least in my view, would be the "hot stuff of the week", or a kind of "help wanted" board. This is the one where there is a lot of debate regarding whether it's useful or not, and how it should be organized. https://github.com/orgs/kata-containers/projects/25 Let me know what you think. -- Cheers, Christophe de Dinechin (IRC c3d)

2 3

Weekly Kata Herders
by Hunt, James O 10 May '21

10 May '21

Hi All, This week's Kata PR and issue herders are: - Christophe (https://github.com/c3d) - Gaby (https://github.com/GabyCT) - Jongwu (https://github.com/jongwu) - Snir (https://github.com/snir911) # Statistics ## Issues Issues opened last week: 34 Issues closed last week: 44 Open issues: 408 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 57 PRs closed last week: 114 Open PRs: 78 Open PRs (excluding dnm+wip): 53 # Get involved If you'd like to help get the open PRs merged and open issues resolved (or get involved in other ways with Kata), take a look at the contributing guide [2] and the rota process [3]. Any problems, just ask us [4]. Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/master/Rota-Process.md [4] - https://github.com/kata-cZhihong Yuontainers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0

Weekly Kata Herders
by Hunt, James O 04 May '21

04 May '21

Hi All, This week's Kata PR and issue herders are: - Julio (https://github.com/devimc) - me (https://github.com/jodh-intel) - Ricardo (https://github.com/raravena80) - Pavel (https://github.com/pmores) # Statistics ## Issues Issues opened last week: 52 Issues closed last week: 64 Open issues: 415 Issue backlog project board: https://github.com/orgs/kata-containers/projects/23 ## PRs PRs opened last week: 54 PRs closed last week: 77 Open PRs: 111 Open PRs (excluding dnm+wip): 94 # Get involved If you'd like to help get the open PRs merged and open issues resolved (or get involved in other ways with Kata), take a look at the contributing guide [2] and the rota process [3]. Any problems, just ask us [4]. Cheers, James [1] - https://github.com/kata-containers/community/wiki/Review-Team-Rota [2] - https://github.com/kata-containers/community/blob/master/CONTRIBUTING.md [3] - https://github.com/kata-containers/community/blob/master/Rota-Process.md [4] - https://github.com/kata-cZhihong Yuontainers/community/blob/master/README.md#join-us --- https://katacontainers.io/ | https://github.com/kata-containers Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. --------------------------------------------------------------------- Intel Corporation (UK) Limited Registered No. 1134945 (England) Registered Office: Pipers Way, Swindon SN3 1RJ VAT No: 860 2173 47 This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.

1 0