Mailinglist Archive: opensuse-packaging (171 mails)

< Previous Next >
[opensuse-packaging] New maintenance work-flow for openSUSE on Thursday (15th March)
  • From: Adrian Schröter <adrian@xxxxxxx>
  • Date: Mon, 12 Mar 2012 13:51:50 +0100
  • Message-id: <21831102.NaXuUpl0xH@scherben>

In the name of Maintenance, Security and OBS team:

After long time designing and development of the new build system
maintenance model, we (Security, Maintenance and OBS team) will
do the switch on

Thursday, 15th March

What does this mean for plain openSUSE users?

- No actions required. The same repos will provide at
the same place the same content.

- patch naming will change from "packagename-<globalversion>" to

What does this mean for openSUSE developers?

Short version:

- OBS and Bugzilla are the only tools for coordinating openSUSE updates.
SUSE internal SWAMP is no longer used for openSUSE.

- osc 0.134 is required.
=> A maintenance update will provide it.

- With osc 0.134 "osc submitrequest" against update projects will
actually not create submit requests anymore. Instead maintenance
requests are used now. osc automatically detects that but you can
also create maintenance requests manually using "osc

- openSUSE:X.y:Update:Test is no longer used for package submissions.
Submit against *:Update or use "osc maintenancerequest" instead

- Running updates with open bugs assigned to the packager
appear in patchinfos on the "my work" page. And on CLI:
=> osc my [work]

- Every update _must_ have at _least_ one bnc# reference in the changelog which
explains why an update is needed. If the change needs more explanation,
the description from the maintenance request is used for the customer
readable patch description.

If anything is unclear, ask via bugzilla by NEEDINFO'ing
Other comments, or CC'ed comments to individual persons will not be handled.

- If you plan to stage changes to packages, it is heavily recommended to
a devel project for your 11.4 and 12.1 updates and set it in the
via the "osc changedevelrequest" command. This ensures, similiar to how it
works for openSUSE Factory, that you can collaborate on updates and test
changes prior submission for update.

Different scenarios and workflow examples can be found in the OBS
reference maintenance chapter:

Boring background details:

- Updates get prepared in subprojects of openSUSE:Maintenance
("Incident Projects") and released from there.

- Updates are now built against :Update instead of :Update:Test.
Therefore not yet released updates don't influence each other
anymore. That also means that updates that depend on each other
need to be put into a common incident project.

Adrian Schroeter
SUSE Linux Products GmbH
email: adrian@xxxxxxx
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >
This Thread
  • No further messages