Torsten Tejlmand Rasmussen

> Is it normal to do a clean cmake build every time you change something in CMakeLists.txt? no, if you do a change in a CMake file and re-run the...

Haven't looked at all those changes, but based on the description: > The problem is the Zephyr port of MCUBoot does not allow me to configure and build an MCUBoot...

> * e.g. SDK 0.15.2 and 0.16.0 may be used interchangeably while 0.14.2 and 0.15.0 may not. Which is perfectly legal for semantic versioning, and one reason why Zephyr SDK...

> @tejlmand Did you read the proposal? I did, and to a large extent I agree to the path forward in order to define when to have a first major...

> According to Semantic Versioning 2.0.0, "Major version zero (0.y.z) is for initial development." Zephyr SDK is well beyond the "initial development" phase and we are currently using it in...

Extra comment: > major incompatible change(s) > minor incompatible change(s) how can an incompatible change be major or minor, if it's incompatible then it's incompatible, so I suggest removing major...

> because we have been seeing various user experience-related problems related to this, as described in this issue, and we do need a solution, which this issue proposes. and I...

> Does an architecture-specific (e.g. only affecting the SPARC architecture) incompatible GCC change really warrant a MAJOR bump? Yes, cause it has a major impact on users of sparc arch....

> change the name of an obscure architecture-specific GCC flag such as -mtp-regno to -mtp-regnum, is that correct? is gcc blindly removing it, or is gcc properly deprecating the old...

> This PR needs documentation of the new scheme, a migration guide, i.e. describe how to move a board/soc from v1 to v2 Correct, and that is also listed in...