Re: Do not use west v0.6.1; upgrade to v0.6.2

Bolivar, Marti

"Youse, Charles" <charles.youse@...> writes:


Thanks for letting us know.
Of course.

Perhaps, since 'west' has been made practically essential to Zephyr,
we should investigate some kind of QA process for west releases.
We have a process in place. It failed here due to lack of coverage,
which unfortunate oversight and I'm very sorry for it, especially for
those who ran into it. However, it was lack of coverage, and not lack of
process, that was to blame.

West has a test suite that works at both API and functional levels. The
repository CI runs it on each commit (on Linux, via shippable). We also
run it on supported platforms before cutting a release. In this case,
that's Windows 10 and macOS. (This is in addition to informal testing
that people are doing on the code in the master branch, which isn't
relevant to this point since you are asking about process.)

More testers and attention to testing are always welcome, so feel free
to make any concrete suggestions for how we can improve our QA.



-----Original Message-----
From: devel@... [mailto:devel@...] On Behalf Of Bolivar, Marti
Sent: Wednesday, September 4, 2019 9:48 AM
To: users@...; devel@...
Subject: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2


West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected.

If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process:


pip3 install -U --user west

macOS and Windows:

pip3 install -U west


Join to automatically receive all group messages.