openSUSE Maintenance
fixing bugs after release
Marcus Meissner
Marcus was born in 1973. He studied computer science in Erlangen, Germany and finished with Diploma. He worked for Caldera from 1999 until the closure of Caldera Linux Business in 2002. He is working for SUSE since 2002, and in the security team since 2004. He has lead the team until begin of 2013 and is now the security project manager. He also is part of the openSUSE Maintenance team and works on a lot of openSUSE packages. In his spare time he is a gphoto (digital camera access library) and Wine developer.
While openSUSE has a rolling release, which is constantly integrating new versions and bugfixes, we also have releases where the main codebase is frozen and we release bugfix and security updates via online updates.
This process has been established for a while and is coordinated by the openSUSE Maintenance Team.
Also, last year a new release came with new and changed update origins, openSUSE Leap 42.1. This release inherits some parts of its updates from SUSE Linux Enterprise 12, which might be confusing at times.
This talk will offer a refresher on the maintenance processes and also some details you as packager needs to observe, also especially in regards to Leap.
- Date:
- 2016 June 23 - 16:30
- Duration:
- 30 min
- Room:
- Galerie
- Conference:
- openSUSE Conference 2016
- Language:
- Track:
- openSUSE
- Difficulty:
- Medium
- invis-Server
- Start Time:
- 2016 June 23 16:00
- Room:
- Seminarraum 1
- 20.000 Leagues Under SUSE Studio
- Start Time:
- 2016 June 23 16:30
- Room:
- Seminarraum 2
- Deliver personalization, remain legally compliant, AND respect privacy with open source!
- Start Time:
- 2016 June 23 16:30
- Room:
- Saal