|
Size: 982
Comment: typo
|
← Revision 3 as of 2024-01-21 11:49:29 ⇥
Size: 983
Comment: typo
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 5: | Line 5: |
| You probably got send to this page by a warning from an upload hook (dupload or dput or dput-ng or similar). The hook is warning you that the source package that you intend to upload is involved in a [[https://release.debian.org/transitions/|transition]]). When changes in a package cause the need for changes in other packages, we call this a 'transition'. The most common example is a library transition. Transitions are managed by the Release Team. To avoid unnecessary delays (e.g. waiting for the aging of an upload that's not necessary for the transition to finish) and frustration to the people involved, it's better to hold of uploads to unstable until the transition is finished. Obviously, uploads that solve issues caused by the transition are very welcome. | You probably got send to this page by a warning from an upload hook (dupload or dput or dput-ng or similar). The hook is warning you that the source package that you intend to upload is involved in a [[https://release.debian.org/transitions/|transition]]). When changes in a package cause the need for changes in other packages, we call this a 'transition'. The most common example is a library transition. Transitions are managed by the Release Team. To avoid unnecessary delays (e.g. waiting for the aging of an upload that's not necessary for the transition to finish) and frustration to the people involved, it's better to hold off uploads to unstable until the transition is finished. Obviously, uploads that solve issues caused by the transition are very welcome. |
This is the landing page for upload hooks that warn for transitions.
What is this all about?
You probably got send to this page by a warning from an upload hook (dupload or dput or dput-ng or similar). The hook is warning you that the source package that you intend to upload is involved in a transition). When changes in a package cause the need for changes in other packages, we call this a 'transition'. The most common example is a library transition. Transitions are managed by the Release Team. To avoid unnecessary delays (e.g. waiting for the aging of an upload that's not necessary for the transition to finish) and frustration to the people involved, it's better to hold off uploads to unstable until the transition is finished. Obviously, uploads that solve issues caused by the transition are very welcome.
For info, the instructions for maintainers that start a transition can be found here: ../Transitions.