Skip to content

Commit 4038a50

Browse files
committed
transitions : fill the section with contents from the ubuntu maintainer handbook
1 parent 90209b5 commit 4038a50

File tree

1 file changed

+20
-1
lines changed

1 file changed

+20
-1
lines changed
Lines changed: 20 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,2 +1,21 @@
11
(transitions-process)=
2-
# How transitions work
2+
3+
# Library Transitions
4+
5+
A library transition is the process that happens when a library gets updated to a new
6+
version that includes API/ABI changes and requires rebuilding and re-testing all
7+
the reverse dependencies. A library transition can be more or less complex depending
8+
on the API/ABI breaking change and the number of reverse dependencies, especially
9+
when some of them fail to build with the new package version.
10+
11+
Very complex transitions require a concerted, organized effort, and that's what we'll
12+
primarily focus on in this document. Simpler transitions often go through automatically,
13+
or sometimes with a bit of manual assistance.
14+
15+
To keep track of all recent, planned or ongoing transitions, there is the Launchpad project
16+
[Ubuntu Transition Tracker](https://launchpad.net/ubuntu-transition-trackeer) managed
17+
by the [Ubuntu Transition Trackers](https://launchpad.net/ubuntu-transition-tracker) team.
18+
19+
There is a page [NBS](https://ubuntu-archive-team.ubuntu.com/nbs.html) that lists all binary
20+
packages in the archive (and its reverse dependencies) that are not built from any source
21+
package. These packages existence in the list might result from an ongoing transition.

0 commit comments

Comments
 (0)