Remove references to old release process in README.

Author: aarongreig

README.md

@@ -1,6 +1,6 @@
 # Unified Runtime
 
-[![Build and test](https://github.com/oneapi-src/unified-runtime/actions/workflows/cmake.yml/badge.svg)](https://github.com/oneapi-src/unified-runtime/actions/workflows/cmake.yml)
+[![Pre-commit](https://github.com/intel/llvm/actions/workflows/ur-precommit.yml/badge.svg)](https://github.com/intel/llvm/actions/workflows/ur-precommit.yml)
 [![Nightly](https://github.com/oneapi-src/unified-runtime/actions/workflows/nightly.yml/badge.svg)](https://github.com/oneapi-src/unified-runtime/actions/workflows/nightly.yml)
 [![Deploy documentation to Pages](https://github.com/oneapi-src/unified-runtime/actions/workflows/docs.yml/badge.svg)](https://github.com/oneapi-src/unified-runtime/actions/workflows/docs.yml)
 [![Compute Benchmarks Nightly](https://github.com/oneapi-src/unified-runtime/actions/workflows/benchmarks-nightly.yml/badge.svg)](https://github.com/oneapi-src/unified-runtime/actions/workflows/benchmarks-nightly.yml)
@@ -60,14 +60,6 @@ add_executable(example example.cpp)
 target_link_libraries(example PUBLIC unified-runtime::headers)
 ```
 
-### Weekly tags
-
-Each Friday at 23:00 UTC time a [prerelease
-tag](https://github.com/oneapi-src/unified-runtime/releases) is created which
-takes the form `weekly-YYYY-MM-DD`. These tags should be used by downstream
-projects which intend to track development closely but maintain a fixed point in
-history to avoid pulling potentially breaking changes from the `main` branch.
-
 ## Third-Party tools
 
 The recommended method to install the third-party tools is using a Python
@@ -207,26 +199,3 @@ Code is generated using included [Python scripts](/scripts/README.md).
 
 Documentation is generated from source code using Sphinx -
 see [scripts dir](/scripts/README.md) for details.
-
-## Release Process
-
-Unified Runtime releases are aligned with oneAPI releases. Once all changes
-planned for a release have been accepted, the release process is defined as:
-
-1. Create a new release branch based on the [main][main-branch] branch taking
-   the form `v<major>.<minor>.x` where `x` is a placeholder for the patch
-   version. This branch will always contain the latest patch version for a given
-   release.
-2. Create a PR to increment the CMake project version on the [main][main-branch]
-   and merge before accepting any other changes.
-3. Create a new tag based on the latest commit on the release branch taking the
-   form `v<major>.<minor>.<patch>`.
-4. Create a [new GitHub release][new-github-release] using the tag created in
-   the previous step.
-   * Prior to version 1.0, check the *Set as a pre-release* tick box.
-5. Update downstream projects to utilize the release tag. If any issues arise
-   from integration, apply any necessary hot fixes to `v<major>.<minor>.x`
-   branch and go back to step 3.
-
-[main-branch]: https://github.com/oneapi-src/unified-runtime/tree/main
-[new-github-release]: https://github.com/oneapi-src/unified-runtime/releases/new

scripts/core/CONTRIB.rst

@@ -102,7 +102,7 @@ regenerate the source.
 Generating Source
 =================
 
-The specification and many other components in the Unified Runtime repository
+The specification and many other components in the Unified Runtime project
 are generated from a set of YAML_ files which are used as inputs to a Mako_
 based templating system. The YAML file syntax is defined in `YAML syntax`_. To
 generate the outputs of the Mako templates a build directory must be
@@ -182,7 +182,7 @@ targeting ``intel/llvm:sycl``.
 Please ensure you include the ``[UR]`` tag in the title of your pull request.
 
 When making changes to the specification you *must* commit all changes to files
-in the repository as a result of `Generating Source`_.
+in the project as a result of `Generating Source`_.
 
 Before your pull request is merged it *must* pass all jobs in the GitHub
 Actions workflow and *must* be reviewed by all reviewer teams tagged as