Concerning SW upgrade needs, do we need to keep DB version to allow these two versions can still communicate? Sent from my iPhone
On Sep 16, 2019, at 22:46, Dominig ar Foll (Intel Open Source) <dominig.arfoll@fridu.net> wrote:
Hello,
One of the comment/worry that have seen on the instant message was about the potential regression risk related to the move to systemD. I would like to share the exchange as it relevant for all the community concerned by that topic.
Question: I am afraid that changing this will impact flocks functionality or big regression testing is required.
Response: Adding security and multiOS support will require some retest for sure. But if we add a plugin we could keep different DBs for different OSes. One calling for init.d scripts for legacy support while for multiOS a new DB would call for systemD. With that model, we would minimise risk, as only minimalistic regression test would be required until the DB content is changed for a given OS.
-- Dominig ar Foll Senior Software Architect Intel Open Source Technology Centre
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss