I agree, but for now Manjaro would need people to get involved in the process of creating such automation, let just hope some people will join the discussion to help the team.
Ah, so this is more about a
workflow proposal rather than a (contract?) for quality assurance … Probably the title might need rephrasing.
I love when people send me links to wikipedia. It must be a thing this days … in reference to ISO 9000 and ISO/IEC 17025 in the context where:
ISO/IEC 9126 - for software development or software engineering indeed is meant to:
was replaced by ISO/IEC 25010:2011
Anyway, in Romanian the word
assurance can be used and interpreted as a pompous thing, patronizing when in a non contractual circumstance. In something “official” is fine and you become bound by it by signing a contract.
Having some qa-automation would be helpful and especially manjaro-architect would benefit from it. If someone has time to do a poc for this, it would be greatly appreciated.
I think I will rename the topic Manjaro quality assurance (QA) so it is clear that it is a technical term and not an assurance for which the users can sue us.
I hope my comments didn’t come as derogatory in any way to what the OP intended to convey. While wiki is a nice resource of information, explanations, definitions, etc. i don’t agree with everything from there, and not all the conventions work for me
Due to life circumstances, I’m not going to be in a position to pursue this for the foreseeable future. Apologies.