All CtLG Meeting notes can be found here: https://etherpad.opensuse.org/p/ClosingTheLeapGap-meeting Attendees: lkocman, Gustavo, Stephan, Marina, Stefan, Rado, Scott, Wolfgang Topics to discuss: Any thoughts from the last meeting, when we agreed to mirror requests, Partner features -> ECO ... (previous round https://etherpad.opensuse.org/p/ClosingTheLeapGap-maintenance-20200604) Diagram of the proposed workflow as discussed with Autobuild by lkocman: https://github.com/openSUSE/CommunitySLEFeatureRequests/blob/master/images/s... ^ This is still actual no changes were done aside from minor fixes raised on the call My thoughts on OBS-63 and missing pieces to have correct reporting back. Would my proposal work for the maintenance team as well? See the link bellow https://jira.suse.com/browse/OBS-63?focusedCommentId=1002443&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-1002443 Stephan Barth: Partners or customers might test incoming SLE changes via Package Hub, and we might want to keep this in mind while designing the workflow. lkocman: The idea is that non-SLE Leap packages will be built in openSUSE:Backports (referenced as Packagehub), therefore any testing of these could be considered also as partner testing of openSUSE Leap. Stefan Weiberg: SHAP team is testing Salt formulas and providing them in Package Hub first, and then after initial testing publish them in SLE. Therefore Package Hub is considered to be a tech preview. The workflow is usually submitting a new package to Package Hub, do testing, and then remove it from Package Hub and ship it in the PRODUCT. In the case of SHAP, it would be always submission for all supported releases, not just the latest Service Pack. Gustavo: We don't see any problem with these, but at this point, it's not viewed as a problem. Wolfgang: Package Hub is currently seen as an extension, and package changes signature. The user has to allow vendor change during the migration. Lubos will add this to https://jira.suse.com/browse/PM-1733 Lubos: the current request for openSUSE Partner setup https://jira.suse.com/browse/JIRA-722 is expecting that the partner project will be publicly visible (or at least to all persons having active JIRA account). So at least people would be able to raise concerns on the transition from Leap (PackageHub) to SLE. These features would be visible to partners. Lukas Ocilka: https://github.com/yast/yast-migration/blob/fcc38fa4190e74e702b6ae8ff4272f4d... Submission including comments https://github.com/yast/yast-migration/pull/48/files The following code already allows vendor changes from openSUSE -> SLE this only in case of Yast Migration. Product upgrades should most likely have similar handling. Action items: Lubos to create a wrap-up of what we came up with send it around to stakeholders for review and then post it to opensuse-factory@ for further feedback.