In this talk, we continue to discuss how we worked on bridging openSUSE Leap and SLE gap for openSUSE Leap 42.2/SLE12 SP2 and what is planned for future version

1. Bridging openSUSE and SLE gapBridging openSUSE and SLE gap
Return of the GNOME, part deux aka the revengeReturn of the GNOME, part deux aka the revenge
Frédéric Crozat <fcrozat@suse.com>
SUSE Linux Enterprise Release Manager

2. In the previous episodeIn the previous episode
2

3. Mistakes were made
●
In SLE12 (SP0), we forked GNOME 3.10.3..
●
Even worse, we didn’t backport our features to
openSUSE:Factory !
●
We were saying “we’ll do that later...”
●
For SLE12 SP1, people were too busy bug fixing
●
“We’ll do that later...”
3

4. We started to fix those mistake
●
Goal was to sync back SLE 12 GNOME with openSUSE one
●
Could we share the same SRPM between SLE 12 SP2 and
Leap 42.2 ?
●
By SLE12 SP2 Beta1, no everything was pushed back to
openSUSE:Factory..
4

5. Did we succeed ?Did we succeed ?
5

6. We did it !
●
More than 300 packages to sync
●
A lot of discussion and interaction between SUSE desktop
teams and openSUSE GNOME team
●
Tooling was essential, to get overview of divergeance between
SLE and openSUSE packages
●
Very few patches were enabled only on SLE 12 SP2
●
Sometime, in later bug reports, we discovered Leap 42.2 was
suffering from bugs not present in SP2, because of the above.
6

7. Pain points
●
Work was done first internally and then pushed to openSUSE
●
Changelog integration
– Packages between SP should never loose FATE / CVE /
BSC
– openSUSE was very helpful in accepting some older
changelog entries to preserve this
●
Update handling for bug reported on Leap for packages
inherited from SLE
7

8. Scenes from our next episodeScenes from our next episode
8

9. Factory first
●
New guidelines in effect for development of SLE12 SP3
●
Whenever possible, development should be done on OBS
(openSUSE:Factory) and pushed back to SLE12 SP3
●
When a submission is sent to SLE12 SP3, a automated check
will ensure similar submission was done to openSUSE:Factory
●
Based on this knowledge, SLE Release Managers decide what
to do with those submit requests
●
You can see SLE12 SP3 development “live”, once it is in Beta
phase
9

10. Some numbers about SLE12 packages
●
SLE 12 SP3 (post Beta3)
– 342 “source” packages
– 235 FORK (but usually equivalent submission in OBS was
done)
– 107 are Factory packages (30%)
●
SLE 12 SP2: 1010 “source” packages
●
SLE 12 SP1: 550 “source” packages
●
SLE 12: 2971 “source” packages
10

11. SLE12 packages origin
11
SLE12 SP1 SLE12 SP2 SLE12 SP3 (devel)
0
200
400
600
800
1000
1200
Factory
FORK

12. Some numbers about Leap 42 packages
●
Leap 42.3 (post Beta3)
– 10403 “source” packages
– 1964 inherit from SLE12 (270 from SP3)
– 1992 from Factory
– 120 from Devel projects (KDE 5 LTS)
– 5972 from Leap 42.2
●
Leap 42.2:
– 8968 “source” packages
– 82 FORK
– 2478 are Factory packages !
– 1865 from SLE12 codebase (580 from SP2)
– Only 43 packages from Devel project (KDE 5 LTS)
●
Leap 42.1
– 7630 “source” packages
– 209 FORK
– 5698 from Factory
– 221 from Devel projects (GNOME 3.16 mostly)
– 1501 inherit from SLE12 codebase (256 from SP1, the rest from GA)
12

13. Leap Packages origin
13
Leap 42.1 Leap 42.2 Leap 42.3
0
2000
4000
6000
8000
10000
12000
Leap
Devel
FORK
Factory
SLE12

14. Questions / Reactions ?
●
Nothing is set in stone
●
We are improving and smoothing our processes
●
Your feedback is important !
14