On 4/14/20 6:47 PM, Lubos Kocman wrote:
Hello openSUSE!
let me share a proposal on how could the new submission workflow for the "Jump" could look like. Just to make sure, Jump is the openSUSE Leap prototype build on top of SLE Binaries and Backports.
FYI: Tasks for current Jump effort are tracked here: https://progress.opensuse.org/projects/jump_152/
**Let's define 4 separate package origins:**
(1) **SUSE:SLE-15* Code stream in OBS** * Synced 1:1 from IBS with few packages skipped, 00products, 000release-packages, packages related to infrastructure, live patching, ... less than 50) *Roughly 4000 packages
So here are my thoughts ...
Updating the base system
There is currently no well-defined process for updating (1) aside from the Factory First rule. Not many SLE packages are in sync with the version from Factory, so that rule just by itself is not sufficient.
This is 1/3 of the openSUSE Leap distribution. Changes are usually handled via bugs in openSUSE product. Release Manager transforms Submit Requests or Bugs during review into SUSE Linux Enterprise feature requests. I usually try to handle this while Bugzilla triage, which is setting priority to bugs with priority set to P5 (None).
A feature gets approved, or bug gets resolved. Change is implemented in IBS, synced to OBS, Jump gets the new build. This takes quite some time. And lowers the turnover rate of Rel-eng.
I think it would be good to try and involve package maintainers at a really early stage, especially in cases where there is a good working relationship but even in more general cases. For example last week someone from the community submitted something into leap that I already had pending in SLE, where a quick email first could have saved themselves and a bunch of others such as reviewers a bit of time. I'm not sure of the best way to word this but if bug reports generally created first as long as the SUSE maintainer gets cc'd so they can add input if they have it its probably ok. Cheers -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B