Hello Frank,
On 09/02/2021 10:12, Frank Kühndel wrote:
[...]
No objections but I am missing something. We do not used a certain
frozen RTEMS version for the pre-qualification, do we?
we definitely don't use a frozen RTEMS version for the pre-qualification.
This brings about the problem that very change in RTEMS which is part of
the pre-qualified source code must trigger the needed changes in the
pre-qualification data set - here in the specification items:
spec/rtems/basedefs/req/string-0.yml
spec/rtems/basedefs/req/xstring-0.yml
I know, everyone wants to program and push his/her code into RTEMS as
fast as possible without dealing with documentation, specification items
or other depending stuff. ... and I am among the first doing so ...
Yet, if the pre-qualification data set is not continuously kept up to
date, the whole documentation is outdated even before the
pre-qualification project ends. Is this topic somehow addressed? ... and
who is responsible to adapt the above two files?
We are responsible to monitor the RTEMS development during the
pre-qualification activity and adjust the specification, etc. I would
have sent you an e-mail that a specification update is necessary. The
basedefs is an area with a higher probability of changes.
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.hu...@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
