Updated Home (markdown)

Home.md

@@ -35,28 +35,22 @@ This corresponds to the reference development environment and environments for w
 
 You will find `flatpak` and `snap` folders in the source tree. They have been contributed and kept in case someone finds it useful. However Flatpak and Snap are not supported and even not recommended.
 
-<h2>Continuous Integration and Delivery</h2>
-
-For every release on master branch the resulting artifacts are uploaded to the [releases section](https://github.com/f4exb/sdrangel/releases).
+<h2>Continuous Integration</h2>
 
 <h3>Linux and Docker</h3>
 
 This is done using [Appveyor](https://www.appveyor.com/) and is driven by the [.appveyor.yml](https://github.com/f4exb/sdrangel/blob/master/.appveyor.yml) file. The builds are run at the owner premises.
 
-The Linux build yields a .deb file and is done in a docker container based on a Ubuntu 20.04 image provided by Appveyor. The Qt version in use is 5.12.8.
-
 The Docker image is built using [this Dockerfile](https://github.com/f4exb/sdrangel-docker/blob/master/sdrangel/Dockerfile).
 
-You can check [SDRangel project](https://ci.appveyor.com/project/f4exb/sdrangel) in Appveyor where all builds and artifacts may be consulted.
+You can check [SDRangel project](https://ci.appveyor.com/project/f4exb/sdrangel) in Appveyor.
 
 <h3>Windows</h3>
 
 This is done via the Actions Github feature and based on [this file](https://github.com/f4exb/sdrangel/blob/master/.github/workflows/sdrangel.yml) The build is based on MSVC 2019 and Qt 5.15.2
 
-You can check [this section](https://github.com/f4exb/sdrangel/actions/workflows/sdrangel.yml) for the latest builds.
-
 <h2>Repository branches</h2>
 
-  - master: this is the default branch and is the most up to date that will eventually make the next release. This is the branch used to produce release artifacts.
+  - master: this is the default branch and is the most up to date that will eventually make the next release.
   - next_release: this branch may appear temporarily when a lot of feature branches need to be merged together before being merged to master for the next release. This avoids polluting the master branch with versions that are not mature enough or may break.
   - feature-nnn: feature branches are current developments related to issue nnn when these developments are made publicly available before being merged to master or next_release