QA_Plan_Version_0.9.5.4.pdf

[KlausRuedigerHase]

I am missing the link to the Eclipse QA system, Eclipse Development Process, and Eclipse Governance. It was one of the essential ideas of this project to utilize as much as possible from what is availble in the OSS industry. Since we early on decided to look into the Eclipse process and even concidered to become an Eclipse project, join another or form an own Eclipse Industial Working group later during the course of the project, we could safe quite a lot of effort for setting up a QA system by utilizing available Eclipse resources. Since the Eclipse Ecosystem was not designed with CENELEC like safety applications in mind, we definately have to enrich the Eclips QA system with elements that are required to accommodate the objectives as defined in CENELEC, in particular EN50128.
This should be mentioned on page 7 inside the introduction but also later more intensively been considered. There is otherwise only a reference on page 12. Otherwhise is does not becomes very clear to newcomers that Eclipse is supposed to be the foundation for our QA system.
We might ask Eclipse members in our group or even representatives of the Eclipse Foundation for additional support.
KRH

[KlausRuedigerHase]

We should always try to link our issues to milestones by which they are expected to be closed.

[BerndHekele]

Dear Klaus-Rüdiger,
we discussed your point today in the telco.
We will take more care to follow this advice.
Concrete,

• I will document this strategy on page 7 with the next contribution.
• we will look for solutions in Ecliise before provding own processes for outstanding topics

We will double-check against the eclipse way for the rest of the procedures.

[MarcBehrens]

QA Review 2013-10-08: Information from Eclipse governance documents needs to be taken into account.

@JonasHelming