Document is available here: https://etherpad.opensuse.org/p/15.3_respin_proposal_maxlin Assuming respin project name is openSUSE:Leap:15.3:Update:Respin and openSUSE:Leap:15.3:Update:Respin:ToTest Reason for this effort * We did not republish 15.2 / 15.3 Images with boothole/shim respins. 15.2 was too close to 15.3 GA * Axel Brown approached us regarding Rasppi image respin. See details in https://etherpad.opensuse.org/p/ReleaseEngineering-20210721#L22 * openSUSE Leap current doesn't have installer update channel, so our flexibility is limited compared to e.g. SLE 15 SP3 - Project setup Starting by 15.3 openSUSE:Leap:15.X:Update:Respin openSUSE:Leap:15.X:Update:Respin:ToTest openSUSE:Leap:15.X:Update:Respin:WSL * Don't rebuild update package ** Repositories <path project="openSUSE:Leap:15.3:Update" repository="standard- leap-15.3"/> <path project="openSUSE:Leap:15.3" repository="standard"/> <path project="openSUSE:Backports:SLE-15-SP3:Checks" repository="standard"/> <path project="openSUSE:Backports:SLE-15-SP3:Update" repository="standard-leap-15.3"/> <path project="openSUSE:Backports:SLE-15-SP3" repository="standard"/> <path project="SUSE:SLE-15-SP3:Update" repository="pool-leap- 15.3"/> <path project="SUSE:SLE-15-SP3:GA" repository="pool"/> <path project="SUSE:SLE-15-SP2:Update" repository="pool-leap- 15.3"/> <path project="SUSE:SLE-15-SP2:GA" repository="pool"/> <path project="SUSE:SLE-15-SP1:Update" repository="pool-leap- 15.3"/> <path project="SUSE:SLE-15-SP1:GA" repository="pool"/> <path project="SUSE:SLE-15:Update" repository="pool-leap-15.3"/> <path project="SUSE:SLE-15:GA" repository="pool"/> ** The *snapshot* repo(pool-leap-15.3) should be used in order to avoiding random product rebuilding be triggered. Maybe we should refresh pool-leap-15.3? * Make sure disk limit rule is tweaked for product build images/local * Copy project attributes from openSUSE:Leap:15.3 if needed, OSRT:Config, OSRT:ProductVersion and OSRT:ToTestManagerConfig, you might need to adjust the value. * We need a snapshot-repo of standard repository in openSUSE:Leap:15.3:Update and openSUSE:Backports:SLE-15-SP3, eg. standard-leap-15.3 - Package level * Must to have and need to rebuild + we has been asked to delete some packages from ftp-tree: 000package-groups(for pkglistgen), 000product(generated by pkglistgen per 000package-groups), 000release- packages(generated by pkglistgen per 000package-groups), installation- images, and 000update-repos? * Fixed skelcd-control-openSUSE - remember that workaround in the release package for additional update repos - Tooling * pkglistgen (+ update-repos?) * project-installcheck * TotestManager * skippkg-finder (for fix terrible uninstallable rpms in ftp) * Give the right permission on project/package for bots * tweak publish_opensuse.sh and provide a separate config for 15.3 Update:Respin (lubos) - openQA * Add config for Respin project to openqa-trigger-from-obs https://github.com/os-autoinst/openqa-trigger-from-obs * Add a new JobGroup on o3 for Respin testing, maybe "openSUSE Leap 15 Respin", we can reuse old "openSUSE Leap 15" jobgroup config (We can't re-use current group which is already used for 15.4) * Run libsolv/installcheck against asset repo in openqa, in some cases you might need to adjust 'skippkg-finder-skiplist-ignores' in OSRT:Config for skippkg-finder recalculation. openQA's asset repo isn't browseable, but it is a good repo setup, add it to zypper, refresh zypper to get repodata, you should've repodata in /var/cache/raw/zypp/REPO_NAME, run libsolv/installcheck with repodata. * Discuss scope of test-suite we probably doesn't need full scope of tests that we have for Leap 15 now, but at least offline migration should be tested from previous 15.X releases and typical install scenarios. * Should we worry about Leap -> SLE migration? I'll mention it to PM and Wei Gao, however I don't think that the effort should somehow endanger this scenario. It's expected to work from an updated Leap 15.3+ system. - Publishing * Publishing script have to work for openSUSE:Leap:15.3:Update:Respin:ToTest -> ftp-stage. Who can do this? * Some changes to replace old Leap 15.3 content to the respined one on pontifex. Who should do this? * Lubos to talk to Lars and Adrian about publishing script next Friday - Availability The published image should be simply available on get.opensuse.org as the lastest Leap 15.X image without any need to rework the page manually. Ideally our -Current symlink should always point to the latest image. - Cadence Our respin setup should be able to handle regular quaterly updates, but given the resources we have and demand, we don't believe we have to rebuild image every quarter. It would be more of a reactive rebuild (when needed), which would be time-wise synchronized with timing of a SLE Quartlerly update release. - Architectures x86_64, s390x, ppc64le, aarch64 (Armv7 out of scope) - Artifacts Initial setup DVD image ARM deployment images (rasppi ...) Net install image WSL (We'll create subproject wsl team will figure out the rest) Containers to be checked with Neal (not for this round). - Out of scope Product identification change - Prerequisites All fixes are expected to be accepted in the Leap15.3:Update, openSUSE:Backports:SLE-15-SP3:Update, SUSE:SLE-15-SPX:Update projects ... etc. This effort is only for respinning images that will contain released maintenance updates.