Script 'mail_helper' called by obssrc
Hello community,
here is the log from the commit of package openSUSE-release-tools for
openSUSE:Factory checked in at 2021-09-07 21:21:32
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/openSUSE-release-tools (Old)
and /work/SRC/openSUSE:Factory/.openSUSE-release-tools.new.1899 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "openSUSE-release-tools"
Tue Sep 7 21:21:32 2021 rev:321 rq:917213 version:20210906.2f7e2499
Changes:
--------
---
/work/SRC/openSUSE:Factory/openSUSE-release-tools/openSUSE-release-tools.changes
2021-09-06 15:58:21.605290635 +0200
+++
/work/SRC/openSUSE:Factory/.openSUSE-release-tools.new.1899/openSUSE-release-tools.changes
2021-09-07 21:22:13.749361542 +0200
@@ -1,0 +2,10 @@
+Mon Sep 06 12:21:29 UTC 2021 - [email protected]
+
+- Update to version 20210906.2f7e2499:
+ * Improve text
+ * Add line breaks
+ * Improve text
+ * Document ADI projects
+ * Add documentation
+
+-------------------------------------------------------------------
Old:
----
openSUSE-release-tools-20210906.63613a92.obscpio
New:
----
openSUSE-release-tools-20210906.2f7e2499.obscpio
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Other differences:
------------------
++++++ openSUSE-release-tools.spec ++++++
--- /var/tmp/diff_new_pack.DA7OR2/_old 2021-09-07 21:22:14.337362253 +0200
+++ /var/tmp/diff_new_pack.DA7OR2/_new 2021-09-07 21:22:14.337362253 +0200
@@ -20,7 +20,7 @@
%define source_dir openSUSE-release-tools
%define announcer_filename factory-package-news
Name: openSUSE-release-tools
-Version: 20210906.63613a92
+Version: 20210906.2f7e2499
Release: 0
Summary: Tools to aid in staging and release work for openSUSE/SUSE
License: GPL-2.0-or-later AND MIT
++++++ _servicedata ++++++
--- /var/tmp/diff_new_pack.DA7OR2/_old 2021-09-07 21:22:14.373362296 +0200
+++ /var/tmp/diff_new_pack.DA7OR2/_new 2021-09-07 21:22:14.373362296 +0200
@@ -1,6 +1,6 @@
<servicedata>
<service name="tar_scm">
<param
name="url">https://github.com/openSUSE/openSUSE-release-tools.git</param>
- <param
name="changesrevision">eda1221f8f8af034f530324dc4056d08b8263163</param>
+ <param
name="changesrevision">2f7e2499485d70cb6f764fa7f1c54022873f94c8</param>
</service>
</servicedata>
++++++ openSUSE-release-tools-20210906.63613a92.obscpio ->
openSUSE-release-tools-20210906.2f7e2499.obscpio ++++++
diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn'
'--exclude=.svnignore'
old/openSUSE-release-tools-20210906.63613a92/docs/processes.md
new/openSUSE-release-tools-20210906.2f7e2499/docs/processes.md
--- old/openSUSE-release-tools-20210906.63613a92/docs/processes.md
2021-09-06 10:28:14.000000000 +0200
+++ new/openSUSE-release-tools-20210906.2f7e2499/docs/processes.md
2021-09-06 14:20:07.000000000 +0200
@@ -42,6 +42,54 @@
explaining how the different reviews are created and processed by OBS and by
the involved bots and
release tools.
+### Rings and Staging Projects
+
+As said before, Factory contains a huge amount of packages. The project
receives a lot of new
+request all the time. These requests have to be reviewed, adjusted and tested
before being accepted.
+Reviewing all these packages one by one would be almost impossible. Moreover,
some changes in a
+package could conflict with other packages. Rings and Staging Projects help to
deal with these
+problems, making the review and testing processes more efficient.
+
+[A ring](https://www.youtube.com/watch?v=K-wTVGqKFR8) is an OBS sub-project
that links to certain
+set of packages from the parent project. The goal of a ring is to group
essential packages in order
+to build a smaller testable image. The core of Factory is divided into
+[two rings (0-Bootstrap,
1-MinimalX)](https://build.opensuse.org/project/subprojects/openSUSE:Factory:Rings).
+The ring 0 contains packages that form the most basic, minimalist system that
can compile itself. On
+top of that Ring 1 adds what is in the default installation of the two primary
Desktops. All other
+packages are not part of a ring.
+
+[A Staging
Project](https://github.com/openSUSE/open-build-service/wiki/Staging-Workflow)
is a copy
+of the original project, and it serves as a playground for testing a set of
requests. In Factory,
+[Staging
Projects](https://build.opensuse.org/project/subprojects/openSUSE:Factory:Staging)
are
+named with a letter (e.g.,
[Staging:A](https://build.opensuse.org/project/show/openSUSE:Factory:Staging:A),
+[Staging:B](https://build.opensuse.org/project/show/openSUSE:Factory:Staging:A),
etc). When a submit
+request is done to a package that belongs to any of the rings, the request is
automatically put in a
+backlog for the Staging Manager (person in charge of Staging Projects) to
review and to assign it to
+a specific Staging Project. The Staging Manager selects some of the requests
he/she considers they
+belong together and assigns the corresponding packages to the same Staging
Project. For example, it
+might be possible that other packages fail due to a submit request. In that
case, those packages are
+added to the same staging project, so they are built against each other. Once
the Staging Project
+gets built and tested, all the requests can be accepted and the changes merged
into the target
+project.
+
+The Staging Manager can create as many Staging Projects as needed and can
assign different
+selections of requests to each of them. It is still tedious solving the
conflicts that appear
+between different Staging Projects, but being able to test a lot of packages
in parallel is much
+more efficient than doing the same package by package.
+
+An ISO installation image is generated for each Staging Project regularly, and
this image is tested
+on openQA in order to verify those packages would not break the current
Factory. Similarly, a
+testing image is generated from each ring. The whole Factory would be tested
only if the openQA
+tests for the ring images success, see
+[staging-report
bot](https://github.com/openSUSE/openSUSE-release-tools/blob/master/staging-report.py).
+
+There is another kind of Staging Projects: ADI Projects (ADI is an acronym of
*Ad Interim*). These
+are temporary projects created for submit requests of packages that do not
belong to any ring. The
+main differences with a regular staging project are: a) only packages
contained on the ADI Project
+are built (inherited packages are not rebuilt) and b) only *buildability* is
checked (no openQA
+tests). In Factory, ADI Projects are named with *:adi:NUMBER* instead of a
letter (e.g.,
+openSUSE:Factory:Staging:adi:12).
+
## SUSE Linux Enterprise Development
The SUSE Linux Enterprise distribution is built in a SUSE-internal instance of
OBS usually referred
++++++ openSUSE-release-tools.obsinfo ++++++
--- /var/tmp/diff_new_pack.DA7OR2/_old 2021-09-07 21:22:14.973363021 +0200
+++ /var/tmp/diff_new_pack.DA7OR2/_new 2021-09-07 21:22:14.973363021 +0200
@@ -1,5 +1,5 @@
name: openSUSE-release-tools
-version: 20210906.63613a92
-mtime: 1630916894
-commit: 63613a92302682308f8fd968ace960f7703dc5ff
+version: 20210906.2f7e2499
+mtime: 1630930807
+commit: 2f7e2499485d70cb6f764fa7f1c54022873f94c8
