Merge pull request #3266 from Divyaasm/roadmap

Update the Projects roadmap link

Author: kolchfa-aws

_data/top_nav.yml

@@ -21,7 +21,7 @@ items:
       - label: Releases
         url: /releases.html
       - label: Roadmap
-        url: https://github.com/orgs/opensearch-project/projects/1
+        url: https://github.com/orgs/opensearch-project/projects/220
       - label: FAQ
         url: /faq/
   - label: Community

_faqs/01-19-how-do-I-contribute-and-get-on-public-roadmap.markdown

@@ -3,7 +3,7 @@ question: How do I contribute functionality and get it on the public roadmap?
 category: General
 ---
 
-If you want to add something to OpenSearch that is not in the [public roadmap](https://github.com/orgs/opensearch-project/projects/1), that’s a perfect opportunity to contribute! There are a couple of things you can do. 
+If you want to add something to OpenSearch that is not in the [public roadmap](https://github.com/orgs/opensearch-project/projects/220), that’s a perfect opportunity to contribute! There are a couple of things you can do. 
 
 You can create a [feature request](https://github.com/opensearch-project/.github/blob/main/.github/ISSUE_TEMPLATE/FEATURE_REQUEST_TEMPLATE.md) in the relevant GitHub repo for the feature and socialize the request. People are always looking for in-demand features to build. A maintainer or someone else in the community may pick this feature up and work on it. As progress is made the maintainers of the repo will help get the feature onto the roadmap. 
 

_posts/2021-05-26-opensearch-roadmap-announcement.markdown

@@ -8,7 +8,7 @@ categories: update
 redirect_from: "/blog/update/2021/05/opensearch-roadmap-announcement/"
 ---
 
-I wanted to share that a new public roadmap was published to the OpenSearch [project’s GitHub](https://github.com/orgs/opensearch-project/projects/1). The roadmap shows the next several months of planned features and releases. Going forward, this roadmap will show what the maintainers and contributors of the various components of the project intend to work on and when that work aims to launch.
+I wanted to share that a new public roadmap was published to the OpenSearch [project’s GitHub](https://github.com/orgs/opensearch-project/projects/220). The roadmap shows the next several months of planned features and releases. Going forward, this roadmap will show what the maintainers and contributors of the various components of the project intend to work on and when that work aims to launch.
 
 ![OpenSearch roadmap slide on GitHub from 5/25/2021](/assets/media/blog-images/2021-05-26-opensearch-roadmap-announcement/opensearch-roadmap.png){: .img-fluid}
 

_posts/2021-06-07-opensearch-release-candidate-announcement.markdown

@@ -75,6 +75,6 @@ If I have missed anyone on this list, please reach out and I will very gratefull
 
 **What’s next?**
 
-Let's work together to test for bugs and identify feature gaps while working towards a GA release. The goal is to release the GA version of 1.0.0 on July 12, 2021 (check out the public [roadmap](https://github.com/orgs/opensearch-project/projects/1)). Stay tuned to the [forums](https://discuss.opendistrocommunity.dev/), [GitHub](https://github.com/opensearch-project), the community [meeting](https://www.meetup.com/Open-Distro-for-Elasticsearch-Meetup-Group), and our [blog](https://opensearch.org/blog/) for the latest updates and announcements. 
+Let's work together to test for bugs and identify feature gaps while working towards a GA release. The goal is to release the GA version of 1.0.0 on July 12, 2021 (check out the public [roadmap](https://github.com/orgs/opensearch-project/projects/220)). Stay tuned to the [forums](https://discuss.opendistrocommunity.dev/), [GitHub](https://github.com/opensearch-project), the community [meeting](https://www.meetup.com/Open-Distro-for-Elasticsearch-Meetup-Group), and our [blog](https://opensearch.org/blog/) for the latest updates and announcements. 
 
-In the meantime, join us building OpenSearch (if you haven't already)! Feel free to take a look around at what the community has been up to, check out the public [roadmap](https://github.com/orgs/opensearch-project/projects/1), and then head over to look at the open issues. Or you could jump right in and start opening issues or contributing. For more details see [here](https://github.com/opensearch-project/OpenSearch/blob/1.x/CONTRIBUTING.md).
+In the meantime, join us building OpenSearch (if you haven't already)! Feel free to take a look around at what the community has been up to, check out the public [roadmap](https://github.com/orgs/opensearch-project/projects/220), and then head over to look at the open issues. Or you could jump right in and start opening issues or contributing. For more details see [here](https://github.com/opensearch-project/OpenSearch/blob/1.x/CONTRIBUTING.md).

_posts/2021-07-12-opensearch-general-availability-announcement.markdown

@@ -55,9 +55,9 @@ Now that OpenSearch has added test automation, built infrastructure, made update
 * OpenSearch will support cross cluster replication to allow you to deploy for higher availability. 
 * To help you better understand your data, ML features such as FAISS library integrations and root cause analysis support will be added. 
 
-...among many others on the [roadmap](https://github.com/orgs/opensearch-project/projects/1). 
+...among many others on the [roadmap](https://github.com/orgs/opensearch-project/projects/220). 
 
-The next major milestone is OpenSearch 1.1, which is expected to release on August 30. In addition to more artifact coverage (e.g. RPM X64, DEB X64, DEB ARM64), OpenSearch 1.1 will include improvements to anomaly detection (ex. [universal flow](https://github.com/opendistro-for-elasticsearch/anomaly-detection/issues/380)), [indexing pressure protection](https://github.com/opensearch-project/OpenSearch/issues/478), and [notification support](https://github.com/opensearch-project/notifications/issues/181) among others. Check out the [public roadmap](https://github.com/orgs/opensearch-project/projects/1) for more details.
+The next major milestone is OpenSearch 1.1, which is expected to release on August 30. In addition to more artifact coverage (e.g. RPM X64, DEB X64, DEB ARM64), OpenSearch 1.1 will include improvements to anomaly detection (ex. [universal flow](https://github.com/opendistro-for-elasticsearch/anomaly-detection/issues/380)), [indexing pressure protection](https://github.com/opensearch-project/OpenSearch/issues/478), and [notification support](https://github.com/opensearch-project/notifications/issues/181) among others. Check out the [public roadmap](https://github.com/orgs/opensearch-project/projects/220) for more details.
 
 ### **How can you help?**
 

_posts/2021-08-27-what-is-semver.markdown

@@ -62,6 +62,6 @@ One consequence of SemVer is that OpenSearch may end up with a much higher versi
 
 As a user, this means that OpenSearch will be released predictably and you can judge if a release is an upgrade path for your situation just by glancing at the version number compared to yours. For the developers of OpenSearch it gives clear instruction on what constitutes a major, minor, and patch version.
 
-Now that you’re armed with this knowledge, it’s a great time to take a look at the [roadmap](https://github.com/orgs/opensearch-project/projects/1) and see what is in store for the OpenSearch project!
+Now that you’re armed with this knowledge, it’s a great time to take a look at the [roadmap](https://github.com/orgs/opensearch-project/projects/220) and see what is in store for the OpenSearch project!
 
 

_posts/2021-10-05-Launch-Announcement-1-1.markdown

@@ -35,7 +35,7 @@ With the launch of 1.1.0, OpenSearch is already racing forward. There are a numb
 * OpenSearch’s k-NN plugin will add support for the updated [FAISS](https://github.com/facebookresearch/faiss) algorithm that improves performance.
 * Anomaly detection will add visibility to which signals contributed to specific anomalies. 
 
-See additional active features on the [project roadmap](https://github.com/orgs/opensearch-project/projects/1).
+See additional active features on the [project roadmap](https://github.com/orgs/opensearch-project/projects/220).
 
 **How can you contribute?**
 

_posts/2021-11-22-launch-announcement-1-2-0.markdown

@@ -33,7 +33,7 @@ With 1.2.0 launched, OpenSearch 1.3.0 is already in development! There are a num
 * [Drag and drop visualization creation](https://github.com/opensearch-project/OpenSearch-Dashboards/issues/379) 
 * A new [application analytics view](https://github.com/opensearch-project/trace-analytics/issues/131)
 
-If you are curious, feel free to take a look at the [project roadmap](https://github.com/orgs/opensearch-project/projects/1) where you can find out the planned features and fixes with linked issues where you can provide feedback. 
+If you are curious, feel free to take a look at the [project roadmap](https://github.com/orgs/opensearch-project/projects/220) where you can find out the planned features and fixes with linked issues where you can provide feedback. 
 
 ## How can you contribute?
 

_posts/2022-02-15-a-quick-opensearch-primer.md

@@ -72,7 +72,7 @@ Hopefully some of the uncertainty about what OpenSearch is and what it does has
 
 ### A closing thought.
 
-**Anyone can help. Really.** This project wouldn’t be where it is today without the community. One of the project’s principles of development is to be “Open source like we mean it.” The participation of anyone willing will always be welcome. Assistance and contributions of any kind are helpful whether you’re a blogger, coder, tech writer, graphic designer, thought leader or jack of all trades. Not all contributions are code!  If you’ve enjoyed this, become part of the community! Check out the [project page on GitHub](https://github.com/opensearch-project), and the [public roadmap](https://github.com/orgs/opensearch-project/projects/1). Also, join the [community meetings](https://opensearch.org/events/). Last but not least, get involved in discussions and chat with other community members in the [OpenSearch Forums](https://discuss.opendistrocommunity.dev/). **All** are welcome and come as you are. 
+**Anyone can help. Really.** This project wouldn’t be where it is today without the community. One of the project’s principles of development is to be “Open source like we mean it.” The participation of anyone willing will always be welcome. Assistance and contributions of any kind are helpful whether you’re a blogger, coder, tech writer, graphic designer, thought leader or jack of all trades. Not all contributions are code!  If you’ve enjoyed this, become part of the community! Check out the [project page on GitHub](https://github.com/opensearch-project), and the [public roadmap](https://github.com/orgs/opensearch-project/projects/220). Also, join the [community meetings](https://opensearch.org/events/). Last but not least, get involved in discussions and chat with other community members in the [OpenSearch Forums](https://discuss.opendistrocommunity.dev/). **All** are welcome and come as you are. 
 
 
 

_posts/2022-03-17-launch-announcement-1-3-0.markdown

@@ -81,7 +81,7 @@ You can keep informed about upcoming distributions on the [distribution roadmap]
 
 ## RPM & Debian Distributions
 
-As of yesterday (March 16), the team identified the [roadmap](https://github.com/orgs/opensearch-project/projects/1) for 1.3.0 included references to RPM and Debian distributions. In late January, the distribution efforts started to be [tracked on a separate board](https://github.com/orgs/opensearch-project/projects/13) as distributions were decoupled from version releases. In this transition, the cards for RPM and Debian distributions were never removed from the 1.3.0 roadmap. The team regrets this error and have put measures into place to ensure that the roadmap will be more accurate moving forward.
+As of yesterday (March 16), the team identified the [roadmap](https://github.com/orgs/opensearch-project/projects/220) for 1.3.0 included references to RPM and Debian distributions. In late January, the distribution efforts started to be [tracked on a separate board](https://github.com/orgs/opensearch-project/projects/13) as distributions were decoupled from version releases. In this transition, the cards for RPM and Debian distributions were never removed from the 1.3.0 roadmap. The team regrets this error and have put measures into place to ensure that the roadmap will be more accurate moving forward.
 
 ## What’s Next?
 
@@ -97,7 +97,7 @@ In addition, OpenSearch 2.0.0 is already in development! The primary driver for
 * **Lucene 9.0.0**: Lucene 9.0.0 includes several new features and performance improvements ([Lucene 9.0.0 Documentation](https://lucene.apache.org/core/9_0_0/index.html)) that OpenSearch would like to make available to users, including K-NN support, Vectors, Big Endian, faster numeric indexing, faster sorting, concurrent merge scheduler, and prototype Java Jigsaw module support. Starting to use Lucene 9.0.0 as soon as possible is a priority. It will take a few releases to leverage the full value of it, but adding it with 2.0.0. is so exciting and has loads of potential for OpenSearch.
 * **Node.js Upgrade**: OpenSearch Dashboards needs to upgrade the Node.js version from the current version, 10.24.1, which is no longer in support to a newer version. The target version of node for the upgrade will be v14.18.1. Node v14 which will be in LTS until 2023.
 
-In addition to the above features, this release will replace non-inclusive terminology (e.g., master, blacklist, etc.) throughout OpenSearch with inclusive ones (e.g., leader, primary, allowlist). If you are curious, feel free to take a look at the [project roadmap](https://github.com/orgs/opensearch-project/projects/1) where you can find out the planned features and fixes with linked issues where you can provide feedback. Additionally, please take a look at the [proposed 2022 release schedule](https://opensearch.org/blog/partners/2022/02/roadmap-proposal/).
+In addition to the above features, this release will replace non-inclusive terminology (e.g., master, blacklist, etc.) throughout OpenSearch with inclusive ones (e.g., leader, primary, allowlist). If you are curious, feel free to take a look at the [project roadmap](https://github.com/orgs/opensearch-project/projects/220) where you can find out the planned features and fixes with linked issues where you can provide feedback. Additionally, please take a look at the [proposed 2022 release schedule](https://opensearch.org/blog/partners/2022/02/roadmap-proposal/).
 
 ## How can you contribute?
 

_posts/2022-07-07-opensearch-2-1-is-available-now.md

@@ -38,7 +38,7 @@ Other notable upgrades in the 2.1 release include multi-terms aggregation, user
 
 **Increased zoom levels** offer OpenSearch Dashboards users deeper visualizations when viewing maps. You will be able to zoom in to maps at up to 14x on existing raster tiles, up from 10x. [This upgrade](https://github.com/opensearch-project/maps/issues/4) is now available across all versions of OpenSearch Dashboards, and because changes are enabled on the backend from the maps server, no cluster upgrade is required.
 
-In closing, we want to extend our heartfelt thanks to the OpenSearch community for your feedback on—and contributions to—features that can make a big impact on OpenSearch builders. Stay tuned for more exciting developments on the [roadmap](https://github.com/orgs/opensearch-project/projects/1) from the 2.x release line, starting in August 2022 with OpenSearch 2.2. This release will include significant updates for security analytics, real-time observability tools, anomaly detection, memory management, and more. As always, we invite you to make your voice heard as part of the OpenSearch community through our [community meetings](https://www.meetup.com/OpenSearch/), [forum discussions](https://forum.opensearch.org/), and [GitHub repository](https://github.com/opensearch-project).
+In closing, we want to extend our heartfelt thanks to the OpenSearch community for your feedback on—and contributions to—features that can make a big impact on OpenSearch builders. Stay tuned for more exciting developments on the [roadmap](https://github.com/orgs/opensearch-project/projects/220) from the 2.x release line, starting in August 2022 with OpenSearch 2.2. This release will include significant updates for security analytics, real-time observability tools, anomaly detection, memory management, and more. As always, we invite you to make your voice heard as part of the OpenSearch community through our [community meetings](https://www.meetup.com/OpenSearch/), [forum discussions](https://forum.opensearch.org/), and [GitHub repository](https://github.com/opensearch-project).
 
 ### Get started
 

_posts/2022-07-12-year-one-the-opensearch-project.md

@@ -39,7 +39,7 @@ In May, we released our next major version, [OpenSearch 2.0](https://opensearch.
 
 ## What’s next for the OpenSearch Project?
 
-What I find perhaps most exciting is how the pace of innovation behind the project continues to accelerate. Our [project roadmap](https://github.com/orgs/opensearch-project/projects/1) is public, so anyone can follow along, contribute or provide feedback, and you’re able to see the comprehensive slate of high-impact features and enhancements we plan to release throughout the year on the 2.x line and into 2023 with the release of OpenSearch 3.0. This includes significant new capabilities we’ll be rolling out next month with OpenSearch 2.2, like upgrades for security analytics, real-time observability tools, anomaly detection, memory management, and more. 
+What I find perhaps most exciting is how the pace of innovation behind the project continues to accelerate. Our [project roadmap](https://github.com/orgs/opensearch-project/projects/220) is public, so anyone can follow along, contribute or provide feedback, and you’re able to see the comprehensive slate of high-impact features and enhancements we plan to release throughout the year on the 2.x line and into 2023 with the release of OpenSearch 3.0. This includes significant new capabilities we’ll be rolling out next month with OpenSearch 2.2, like upgrades for security analytics, real-time observability tools, anomaly detection, memory management, and more. 
 
 An open-source project’s roadmap reflects its priorities, and in the case of OpenSearch, those priorities reflect the feedback registered by our growing community of users, contributors, and partners. A thorough review of the roadmap and the [discussions across our forum](https://forum.opensearch.org/) reveals the biggest priorities for the project in 2022 and beyond:
 

_posts/2022-08-11-opensearch-2-2-is-now-available.md

@@ -41,4 +41,4 @@ Other updates in OpenSearch 2.2 include the following.
 
 ### Get started
 
-OpenSearch 2.2 is ready for [download here](https://opensearch.org/downloads.html)! Take a look at the latest [documentation](https://opensearch.org/docs/latest) and [release notes](https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.2.0.md), and keep an eye on the [OpenSearch Project roadmap](https://github.com/orgs/opensearch-project/projects/1) for exciting features and enhancements coming in version 2.3!
+OpenSearch 2.2 is ready for [download here](https://opensearch.org/downloads.html)! Take a look at the latest [documentation](https://opensearch.org/docs/latest) and [release notes](https://github.com/opensearch-project/opensearch-build/blob/main/release-notes/opensearch-release-notes-2.2.0.md), and keep an eye on the [OpenSearch Project roadmap](https://github.com/orgs/opensearch-project/projects/220) for exciting features and enhancements coming in version 2.3!