Mercurial > farol > farol
comparison farol/templates/document/edit_revision.j2 @ 43:c79082d0d44d
Add global descriptions about some containers
| author | Benoît Allard <benoit.allard@greenbone.net> |
|---|---|
| date | Mon, 06 Oct 2014 15:58:25 +0200 |
| parents | 0c726d873c7a |
| children | e0830bcab004 |
comparison
equal
deleted
inserted
replaced
| 42:3b56ea034f2f | 43:c79082d0d44d |
|---|---|
| 26 {% extends "base.j2" %} | 26 {% extends "base.j2" %} |
| 27 {% from "macros.j2" import textinput, textarea, examples %} | 27 {% from "macros.j2" import textinput, textarea, examples %} |
| 28 {% block title %}Edit Revision{% endblock %} | 28 {% block title %}Edit Revision{% endblock %} |
| 29 | 29 |
| 30 {% block content %} | 30 {% block content %} |
| 31 <p><strong>Revision</strong> contains all the elements required to track the evolution of a CVRF document. Each change to a CVRF document should be accompanied by <strong>Number</strong>, <strong>Date</strong>, and <strong>Description</strong> elements.</p> | |
| 31 <form role="form" method="POST"> | 32 <form role="form" method="POST"> |
| 32 {% call textinput("number", "Number", "a.b.c.d", number, required=True) %} | 33 {% call textinput("number", "Number", "a.b.c.d", number, required=True) %} |
| 33 <p><strong>Number</strong> should contain the numeric version of the document. Like the <strong>Version</strong> element above, it is a numeric tokenized field of the format “nn” with up to four fields “nn.nn.nn.nn”. It is recommended that this be a monotonically increasing value. Minor revisions should be used for less-significant changes (for example, <samp>1.0.0.0</samp> to <samp>1.0.0.1</samp>). Major, actionable changes should lead to a major increase of the version number (for example, <samp>1.0</samp> to <samp>2.0</samp>).</p> | 34 <p><strong>Number</strong> should contain the numeric version of the document. Like the <strong>Version</strong> element above, it is a numeric tokenized field of the format “nn” with up to four fields “nn.nn.nn.nn”. It is recommended that this be a monotonically increasing value. Minor revisions should be used for less-significant changes (for example, <samp>1.0.0.0</samp> to <samp>1.0.0.1</samp>). Major, actionable changes should lead to a major increase of the version number (for example, <samp>1.0</samp> to <samp>2.0</samp>).</p> |
| 34 <p>Examples of such changes include:</p> | 35 <p>Examples of such changes include:</p> |
| 35 <ul> | 36 <ul> |