Hi everyone, ***There is a new v1.5.1 patch/hotfix release on GitHub. This very minor patch release was necessary due to one of the cross-built-from-source prerequisites (inode64) becoming inaccessible. This caused the source installation to fail. It was previously downloaded from a URL that is now invalid. This release caches the necessary download in our git repo to avoid this problem. This change does not affect RPM installations at all, but enables installation from source (git clone + build) to work again. There was a problem with creating an SD card from the source release which was also fixed. Since neither of these changes affect any compiled code, the builtin release tag remains 1.5.0 (the tag that is embedded into the compiled binaries). This experience has motivated us to cache all such source downloads in the future to avoid invalid URLs requiring us to issue patch releases. This release is of no use to those who install from RPMs. For those that install from source, and have already done so, the only change is to a script that creates bootable SD images in a built source tree.  If you are not doing this, this patch release can be ignored. See github.com/opencpi/opencpi/releases ***OpenCPI is being moved to GitLab Release 1.6 is nearing completion, and as part of this new release, OpenCPI will be moved to GitLab. The reasons for this include GitLab's integrated CI support, as well as the ease of setting up private instances of the whole "package" of repositories, bug-trackers, and CI. The existing GitHub account will remain, and any further release 1.5 hot fixes will be applied there. A reference/message stating that future developments and releases will be on GitLab, will be placed on GitHub. Starting with the GitLab-based release 1.6, the development of OpenCPI will be completely open, with the core developers using the public repo and the associated bug/issue database/system will be similarly open. Previously, with the GitHub releases, the day-to-day development and bug tracking and CI were all done on a private system, which was sync'd to the public repo (roughly) weekly (source repo, not issues).  The bug/issue database used by core developers was private and never made public. Release 1.6 will not have many improvements since most of the effort has gone into the transition from GitHub to GitLab, and into standing up a new continuous test and integration process on GitLab. The most significant changes to OpenCPI for release 1.6 have to do with FPGA clock domain management to enable HDL workers to use multiple clocks, and in particular, to have separate "control" and "data" clocks.  More details will be supplied with the release, which will be before the end of the calendar year. Cheers, Jim