In this case we are talking about Uyuni (systemsmanagement:Uyuni), the new
upstream for SUSE Manager (replacing spacewalk).
We basically want to release each two/four/six weeks a new version, starting
with 4.0, promoting packages from systemsmanagement:Uyuni:Master (development
project) to some place.
Between one version and the other, there will be no maintenance. Each change,
whatever itis, will required a new release and version.
You could see it as Tumbleweed to some extent, but with a big difference: we
really want to have versions, as Leap or SLE, but unlike Leap or SLE, very
This is useful, for example, if users are running a version of Uyuni in
"production", we release a new version, and they want to setup a server with
the same version as "production" and then test migration.
One way I see to do this would be creating a systemmanagement:Uyuni subproject
for each version and then freeze the packages (so we would have
systemsmanagement:Uyuni:4.2 and so on...)
However I wonder if this is the correct way to do it, because to me it seems a
little bit overkill.
Other option, of course, would be just storing the zypper repositories outside
(there would be a set of repositories for each
version), but I don't like the idea.
I was reviewing how other products are working, but could not find any that
uses this approach. Basically either they have versions with maintenance
(:Update subproject), either they follow Tumbleweed approach, where the
product itself is not versioned.
So, has anyone in the list experience about how to achieve this with OBS?
Julio González Gil <jgonzalez(a)suse.com>
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard,
Graham Norton, HRB 21284 (AG Nürnberg)