Project

General

Profile

action #70957

Maintenance setup for Jump

Added by lkocman about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
2020-09-04
Due date:
% Done:

0%

Estimated time:

Description

We have to work on the initial setup for Jump or rather Leap 15.2.1

History

#1 Updated by lkocman about 1 year ago

3 sets of update channels. 1 for SLE updates, 1 for Backports updates and 1 for Jump updates.
These would have to be available during migration/installation.

Max: can we have 1 overlay channel for all of them? Seems like we don't need them.
How would it look for Leap 15.2.1 and how would it look for 15.3? Can it be the same?

#2 Updated by lkocman about 1 year ago

We need to have a confirmed maintenance plan just like in https://confluence.suse.com/display/leap/Interlock

#3 Updated by msmeissn about 1 year ago

what is the repo layout.

I adjusted the meta prj and attributes of openSUSE:Jump:15.2:Update to most degree now for test updates.

#4 Updated by msmeissn about 1 year ago

  • openSUSE:Jump:15.2:Update is setup better now, I will queue a test update for it.

But we need to know the rest of the repos

#5 Updated by michel_mno about 1 year ago

This issue is marked as blocker for "openQA Jump 15.2 Images" https://openqa.opensuse.org/group_overview/76
So also blocker of https://progress.opensuse.org/issues/71902 "Jump15.2 test fails in podman_image"

Also available in: Atom PDF