Prepare for Release 2.11.0

- Added release notes and freeze file
- Bumped the dependency versions
- Updated the README with the new Release number
- Updated project roadmap and archive

Signed-off-by: Rose Judge <rjudge@vmware.com>

.github/workflows/pull_request.yml

@@ -8,7 +8,7 @@ jobs:
       - uses: actions/checkout@v1 #equivlent to running git fetch and git checkout latest
       - uses: actions/setup-python@v1 # setup python3 environment
         with:
-          python-version: '3.7'
+          python-version: '3.8'
       - name: Setup
         run: |
           sudo apt-get install -y attr
@@ -25,7 +25,7 @@ jobs:
       - uses: actions/checkout@v1
       - uses: actions/setup-python@v1
         with:
-          python-version: '3.7'
+          python-version: '3.8'
       - name: Setup 
         run: |
           sudo apt-get install -y attr
@@ -39,7 +39,7 @@ jobs:
       - uses: actions/checkout@v1
       - uses: actions/setup-python@v1
         with:
-          python-version: '3.7'
+          python-version: '3.8'
       - name: Setup 
         run: |
           sudo apt-get install -y attr
@@ -55,7 +55,7 @@ jobs:
       - uses: actions/checkout@v1
       - uses: actions/setup-python@v1
         with:
-          python-version: '3.7'
+          python-version: '3.8'
       - name: Setup
         run: |
           sudo apt-get update && sudo apt-get install -y attr openjdk-8-jdk-headless maven
@@ -74,7 +74,7 @@ jobs:
       - uses: actions/checkout@v1
       - uses: actions/setup-python@v1
         with:
-          python-version: '3.7'
+          python-version: '3.8'
       - name: Setup
         run: |
           sudo apt-get install -y attr

README.md

@@ -394,17 +394,16 @@ $ python tests/<test file>.py
 ```
 
 ## Project Status<a name="project-status"/>
-Release 2.10.1 is out! See the [release notes](docs/releases/v2_10_1.md) for more information.
+Release 2.11.0 is out! See the [release notes](docs/releases/v2_11_0.md) for more information.
 
-We try to keep the [project roadmap](./docs/project-roadmap.md) as up to date as possible. We are currently working on Release 2.11.0.
+We try to keep the [project roadmap](./docs/project-roadmap.md) as up to date as possible.
 
 ## Recent Past Releases
-Be advised: version 2.4.0 and below contain a high-severity security vulnerability (CVE-2021-28363). Please update to version 2.5.0 or later.
+* [v2.10.1](docs/releases/v2_10_1.md)
 * [v2.9.1](docs/releases/v2_9_1.md)
 * [v2.8.0](docs/releases/v2_8_0.md)
 * [v2.7.0](docs/releases/v2_7_0.md)
 * [v2.6.1](docs/releases/v2_6_1.md)
-* [v2.5.0](docs/releases/v2_5_0.md)
 
 ## Documentation
 Architecture, function blocks, code descriptions and the project roadmap are located in the docs folder. Contributions to the documentation are welcome! See the [contributing guide](/CONTRIBUTING.md) to find out how to submit changes.

docs/project-roadmap-archive.md

@@ -1,5 +1,10 @@
+## 2022-12-16
+### 2022
+- [Create an API to run Tern as a service in Kubernetes](https://github.com/tern-tools/tern/issues/1112): This work has been tabled due to lack of maintainer resources.
+- Improve test report validation
+
 ## 2021-12-15
-###2021
+### 2021
 Our goal is to meet these requirements by the end of the year.
 - We will continue investigating how we can run Tern without root privileges.
 - We want to transition away from using the Docker Python library to pull container images from Dockerhub. For motivation and context, see the Kubernetes [announcement](https://kubernetes.io/blog/2020/12/02/dont-panic-kubernetes-and-docker/) and past [discussion](https://github.com/tern-tools/meetings/blob/main/minutes/04-13-2021.md) on the topic from Tern's community meeting.

docs/project-roadmap.md

@@ -1,14 +1,8 @@
 # Project Road Map
 
-## 2022
-- [Create an API to run Tern as a service in Kubernetes](https://github.com/tern-tools/tern/issues/1112)
-- Improve test report validation
-- The usual bug fixing/technical debt cleanup
+Tern is an open source project with limited resources. In 2023 we will primarily focus on bug fixing and step back from active feature development.
 
-
-We will also continue to work on the following:
-- We will continue to support the SPDX format for container images. To that end, we will make changes to update the format of the document as the [spec](https://spdx.github.io/spdx-spec/) evolves.
-- As usual, we will continue to work on our technical debt and bug fixes.
+We will continue to support the SPDX format for container images. To that end, we will make changes to update the format of the document as the [spec](https://spdx.github.io/spdx-spec/) evolves.
 
 This timetable is based on time, resources and feedback from you and will change accordingly.