On Fri, Dec 11, 2020, 8:41 AM Frank Kuehndel < frank.kuehn...@embedded-brains.de> wrote:
> From: Frank Kühndel <frank.kuehn...@embedded-brains.de> > > --- > eng/req/req-for-req.rst | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) > > diff --git a/eng/req/req-for-req.rst b/eng/req/req-for-req.rst > index 9225e95..dcc4c11 100644 > --- a/eng/req/req-for-req.rst > +++ b/eng/req/req-for-req.rst > @@ -308,6 +308,27 @@ spec:/classic/task/create-err-invname > > ... > > +If requirements or the YAML files which contain them are to be numbered, > +the numbering shall start with 0. For example: + > +.. code-block:: none > + > + weak-alias-0.yml > + weak-alias-1.yml > + > +Smaller numbers shall be prefixed with 0 to the same count of digits > +as the largest number. For example: > When one goes from 99 to 100 requirements and didn't anticipate having that many, does this mean all the files will have to be renamed? Should we start with a minimum of three or four digits? What would drive the number of requirements in a set? How large of a functional area will a single numbered set contain? I'm just wondering if it is simpler to just have 001 as a minimum. + > +.. code-block:: none > + > + alias-00.yml > + alias-01.yml > + alias-02.yml > + ... > + alias-09.yml > + alias-10.yml > + alias-11.yml > + > Conflict Free Requirements > -------------------------- > > -- > 2.26.2 > > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
