(debian-policy.info)State E Seconded

---

Next: State F Accepted Prev: State D Wording proposed Up: Current Process

---

Enter node , (file) or (file)node

20.3.5 State E: Seconded
------------------------

The proposal is signed off on by N Debian Developers.  To start with,
we’re going with N=3, meaning that if three Debian Developers agree, not
just with the proposal but with the conclusion that it reflects
consensus and addresses the original issue – it is considered eligible
for inclusion in the next version of Policy.  Since Policy is partly a
technical project governance method, one must be a Debian Developer to
formally second, although review and discussion is welcome from anyone.
Once this tag has been applied, the bug is waiting for a Policy team
member to apply the patch to the package repository.

TAG: seconded(1)

What needs to happen next: A Policy maintainer does the final review and
confirmation, and then applies the patch for the next Policy release.

This tag is not used very much because normally a Policy maintainer
applies the patch and moves the proposal to the next state once enough
seconds are reached.

   ---------- Footnotes ----------

   (1) 
https://bugs.debian.org/cgi-bin/pkgreport.cgi?src=debian-policy&pend-exc=done&tag=seconded