openSUSE Release Engineering Meeting 04.08.2021
All meeting minutes can be found here: https://etherpad.opensuse.org/p/ReleaseEngineering-meeting Meeting is hosted here https://meet.opensuse.org/ReleaseEngineeringMeeting ## Participants bittin, AdaLovelace,guillaumeg, lkocman, deneb_alpha, DimStar, dirk ## Leap Considering self-update repos for yast in 15.4 https://code.opensuse.org/leap/features/issue/26 python 3.8 - considering for SLE TODO: 15.3 - SElinux won't boot without selinux policy https://bugzilla.suse.com/show_bug.cgi?id=1187326 I have to look into this seems SLE disabled feature in skelcd-control files. We will most likely have to supply the policy, but that will only work with enabled updates. (Release notes entry needed). SP3 selinux-policy seems to have a working fix for SLE, so we could most likely reuse it. TODO check this. Advertise https://code.opensuse.org/leap/features this on factory as a place to raise RFEs or larger efforts for the release. 15.3 Quarterly update setup is still in TODO Looking for review of https://github.com/openSUSE/openSUSE-release-process Leap 15.4 roadmap will be published this week. ## openSUSE Tumbleweed dleuenberger on FTO - from August 9 - 20 * TW is rolling, but mostly unspectacular changes. * glibc 2.34 staged * systemd 249 will be coming after the systemd maintainer is back from vacation ## Richard (Kubic/TW MicroOS) FTO k8s versions updated to 1.19.13, 1.20.9, 1.21.3 Working on adding k3s-install to Kubic, a curated version of the Rancher k3s installation script that negates the need to curl random shell scripts from the internet. ## Max FTO this afternoon * 'local' repository seem to be mis-configurated for openSUSE:Leap:15.4 Adrian should be able to fix this. We'll talk to him. * Enabled all needing bots for Leap:15.4 and Backports:SLE-15-SP4 * Filed 15.3 retro tickets, will go thru them in the retro meeting https://github.com/openSUSE/openSUSE-release-process/issues?q=is%3Aissue+is%... Lubos will try to gather people for Monday morning 1h meeting 9am-ish if we can get for example yast, zypper team representatives. Otherwise we'd delay it for few weeks until DimStar and lkocman are both available. ## Guillaume - Arm Will be on FTO - from 9th to 27th of August. Tumbleweed: * installation-images:* are broken for Arm since last update. A fix is in system:install:head/installation-images and will be forwarded to Factory. * Fix for btrfs support in u-boot is on the way to Factory: https://build.opensuse.org/request/show/909899 Leap 15.3: * Armv7: Is good enough to release officialy. The maintenance setup is problematic, so we may not freeze and need to keep a rolling release model. Any opinion? WSL: Stalled: WIP to have WSL on aarch64 on https://build.opensuse.org/project/show/home:Guillaume_G:WSL todo: lkocman to write a blog post how We have a WSL feature for 15 SP4 to have all SUSE/openSUSE images installed from outside of the store "adopt the new behavior". Therefore we wouldn't have to build the WSL-DistroLauncher image any more. ## Sarah - s390x * Problems with Tumbleweed releases because of kernel bug in several packages ( cross-epiphany-gcc11-bootstrap and gcc): https://bugzilla.opensuse.org/show_bug.cgi?id=1188896 * Updated wiki: https://en.opensuse.org/ZSystems * Offer to receive long-term (not only 120 days) VMs in the LinuxONE Community Cloud (pre-installed SLES), which can be upgraded to openSUSE (there is an unofficial documentation for this on wiki). Register today, if interested to receive one: https://doodle.com/poll/wqyrphvp78um825b * bi-weekly training sessions tor topics as mainframes, containerization, packaging: First session today: https://lists.opensuse.org/archives/list/zsystems@lists.opensuse.org/message... * First training session was last Wednesday about LinuxONE Community Cloud, small overview about mainframes, upgrades and container building ## Doug FTO - from August 2 - 14 (will be availalbe for sprint, Summit and Nest. hopefully I have good internet ;-) * openSUSE.Asia Summit (August 6th- 8th) * Gave team an overview on tools and capablities of venueless * Fedora Nest/Flock booth complete * Collaboration panel discussion * Regular Meeting * finetuned software.o.o. proposal - https://etherpad.opensuse.org/p/weeklymeeting20210724 * Date: Every Saturday from 17:00 to 19:00 UTC (per the survey) (7- 9pm CEST) Location: https://meet.opensuse.org/meeting Etherpad: https://etherpad.opensuse.org/p/weeklymeeting * Likely there will be another 11:00 UTC meeting on Saturdays. Will send out email after I have the info. * will likely work on or discuss process for membership given connect.o.o will deactive * heroes plan to deactivate connect.o.o. ## Dirk No update Regular things, nothing important to report ## Gerald Not available Happy. And thank you to everyone who worked on that for a "boring" UsrMerge upgrade of my notebook. ## Wolfgang (Package Hub), Scott Bahling Not available openSUSE:Backports:SLE-15-SP4, builds for x86_64 are looking good (thanks to Max) other archs like s390x still have many failed and unresolvables discussion about gap https://software.opensuse.org/package/gap (fails to build on s390x), shall we keep it in Backports (it was removed from Factory long time ago) lkocman: https://code.opensuse.org/leap/features/issue/24 ## Maintenance team (Marina or Marcus) Marina: the rpm version update for 15.3 is ready to be released. We are just waiting for SUMA team before releasing it. This release could trigger a lot of rebuilds ;) Ongoing interactions between maintenance and PackageHub teams. Quite some good ideas on improvements. Info: Marina FTO on weeks 33 and 34. Q for maintenance team: https://code.opensuse.org/leap/features/issue/26 would this result into increased load on maint team? Marina: The first thing on my mind is a load for QA Team (Heiko). +Most likely a one time setup for maint. team. ## Adrian - CtLG or openSUSE Step Not present All covered in comments above. Adrian: I had to fix issues in product builder so we won't end up in situation where srpm is missing. We've had this issue by glibc (this would otherwise violate GPL). This would be another reason to rebuild ftp trees. How do we reference to CODE 15. 15.3 was the result of our survey.
participants (1)
-
Lubos Kocman