Document that empty field values are only allowed in debian/control.

[debian/debian-policy.git] / Process.org

diff --git a/Process.org b/Process.org
index 7cb0544fb4ccae5373a500da8bcfe146a09ac6fb..75d3c2c965c2ea8b584fea811e8bee84f43b8167 100644 (file)
--- a/Process.org
+++ b/Process.org
@@ -1,4 +1,4 @@
--*- mode: org; fill-column: 78 -*-
+# -*- mode: org; fill-column: 78 -*-

 #+STARTUP: showall
 #+STARTUP: lognotedone lognotestate
 #+OPTIONS: H:4 toc:2
 #+STARTUP: showall
 #+STARTUP: lognotedone lognotestate
 #+OPTIONS: H:4 toc:2


@@ -8,28 +8,7 @@
 #+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:t d:nil tags:not-in-toc
 #+LINK_HOME: http://wiki.debian.org/Teams/Policy
 #+LINK_UP: http://www.debian.org/
 #+OPTIONS:   H:3 num:nil toc:nil \n:nil @:t ::t |:t ^:t -:t f:t *:t TeX:t LaTeX:nil skip:t d:nil tags:not-in-toc
 #+LINK_HOME: http://wiki.debian.org/Teams/Policy
 #+LINK_UP: http://www.debian.org/

-
-\usepackage{landscape}
-
-\setlength{\oddsidemargin}{0in}                % default=0in
-\setlength{\textwidth}{9in}            % default=9in
-
-\setlength{\columnsep}{0.5in}          % default=10pt
-\setlength{\columnseprule}{1pt}                % default=0pt (no line)
-
-\setlength{\textheight}{5.85in}                % default=5.15in
-\setlength{\topmargin}{-0.15in}                % default=0.20in
-\setlength{\headsep}{0.25in}           % default=0.35in
-
-\setlength{\parskip}{1.2ex}
-\setlength{\parindent}{0mm}
-\pagestyle{empty}
-
-\setlength{\headheight}{0pt}
-\setlength{\headsep}{0pt}
-\setlength{\footskip}{5pt}
-\setlength{\textheight}{9.0in}
-\setlength{\textwidth}{6.5in}
+#+LATEX_HEADER: \input{README-header.tex}

 
 To introduce a change in the current DebianPolicy, the change proposal
 has to go through a certain process.
 
 To introduce a change in the current DebianPolicy, the change proposal
 has to go through a certain process.


@@ -98,7 +77,7 @@ What needs to happen next: Reach a conclusion and consensus in the
 discussion and make a final proposal for what should be changed (if
 anything), moving to the proposal tag.
 
 discussion and make a final proposal for what should be changed (if
 anything), moving to the proposal tag.
 

-** State D: Proposal
+** State C: Proposal

 
 A final proposal has emerged from the discussion, and there is a rough
 consensus on how to proceed to resolve the issue. 
 
 A final proposal has emerged from the discussion, and there is a rough
 consensus on how to proceed to resolve the issue. 


@@ -110,7 +89,7 @@ wording of the change. Often this is done in conjunction with the
 proposal, in which case one may skip this step and move directly to
 patch tag.
 
 proposal, in which case one may skip this step and move directly to
 patch tag.
 

-** State E: Wording proposed
+** State D: Wording proposed

 
 A patch against the Policy document reflecting the consensus has been
 created and is waiting for formal seconds. The standard patch tag is
 
 A patch against the Policy document reflecting the consensus has been
 created and is waiting for formal seconds. The standard patch tag is


@@ -123,7 +102,7 @@ seconded. Any Debian developer who agrees with the change and the
 conclusion of rough consensus from the discussion should say so in the
 bug log by seconding the proposal.
 
 conclusion of rough consensus from the discussion should say so in the
 bug log by seconding the proposal.
 

-** State F: Seconded
+** 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,
 
 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,


@@ -145,7 +124,7 @@ 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.
 
 applies the patch and moves the proposal to the next state once enough
 seconds are reached.
 

-** State G: Accepted
+** State F: Accepted

 
 Change accepted, will be in next upload. The standard pending tag is
 used for this state since it matches the regular meaning of
 
 Change accepted, will be in next upload. The standard pending tag is
 used for this state since it matches the regular meaning of


@@ -156,7 +135,7 @@ What needs to happen next: The bug is now in the waiting queue for the
 next Policy release, and there's nothing left to do except for upload
 a new version of Policy.
 
 next Policy release, and there's nothing left to do except for upload
 a new version of Policy.
 

-** State H: Reject
+** State G: Reject

 
 Rejected proposals. The standard wontfix is used for this
 state. Normally, bugs in this state will not remain open; instead, a
 
 Rejected proposals. The standard wontfix is used for this
 state. Normally, bugs in this state will not remain open; instead, a