Update release plan and add citation information

Author: knolleary

about/index.md

@@ -4,7 +4,7 @@ title: About
 ---
 
 Node-RED is a flow-based programming tool, originally developed by [IBM's Emerging Technology Services](https://emerging-technology.co.uk)
-team and now a part of the [JS Foundation](https://js.foundation).
+team and now a part of the [OpenJS Foundation](https://openjsf.org/).
 
 ### Flow-based Programming
 
@@ -43,6 +43,9 @@ It was open-sourced in September 2013 and has been developed in the open ever
 since, culminating in it being one of the founding projects of the JS Foundation
 in October 2016.
 
+In 2019, the Node.js Foundation merged with the JS Foundation to form the
+[OpenJS Foundation](https://openjsf.org/).
+
 <div class="doc-callout">
 <b>Why is it called Node-RED?</b> The name was a light-hearted play on words
 sounding like 'Code Red'. It stuck and was a great improvement on whatever it was
@@ -65,3 +68,13 @@ For some more of the history and highlights:
 <div style="text-align: center">
     <iframe width="560" height="315" src="https://www.youtube.com/embed/Bbg1017amZs" frameborder="0" allowfullscreen></iframe>
 </div>
+
+
+### Citing Node-RED
+
+If you need to cite the project in a paper, please use the following information:
+
+-----|----
+**Name** | `Node-RED`
+**Author** | `OpenJS Foundation & Contributors`
+**URL** |  If you are citing the project in general, use the project website URL - `https://nodered.org`. <br/>If you are citing a particular version, use either the website, or find the [release page on GitHub](https://github.com/node-red/node-red/releases) for the version you are citing.

about/releases/index.md

@@ -4,29 +4,29 @@ title: Release Plan
 slug: releases
 ---
 
-_Updated: 2020-07-01_
+_Updated: 2021-10-21_
 
 This plan is a guide for how the project plans to schedule upcoming releases, taking
 into account the release schedule of the underlying Node.js runtime.
 
 ![](release-plan.png)
 
 
-The active Node-RED stream (1.x) will get a new minor version release (for example, 1.1 ->  1.2)
-every three months. Maintenance releases (for example 1.1.0 -> 1.1.1) will continue
+The active Node-RED stream (2.x) will get a new minor version release (for example, 2.1 ->  2.2)
+every three months. Maintenance releases (for example 2.1.0 -> 2.1.1) will continue
 to happen as and when they are needed.
 
-At the end of April 2021, when Node 10.x reaches its end-of-life, we will publish
-Node-RED 2.x that will *drop* support for both Node 8.x and Node 10.x.
+At the end of April 2022, when Node 12.x reaches its end-of-life, we will publish
+Node-RED 3.x that will *drop* support for Node 12.
 
-The 1.x stream will then enter maintenance mode. It will only receive bug fixes
-and security updates. New features could get back-ported from 2.x if there was
+The 2.x stream will then enter maintenance mode. It will only receive bug fixes
+and security updates. New features could get back-ported from 3.x if there was
 a very good reason to do so as well as people available to do the work.
 
-The 2.x stream will continue in active development with a minor release every
-three months or so until April 2022 when Node 12.x reaches its end-of-life. We
-then publish Node-RED 3.x and the cycle continues. The 1.x stream will reach its
-end-of-life soon after the 3.x release. The exact timing of that will be something
+The 3.x stream will continue in active development with a minor release every
+three months or so until April 2023 when Node 14.x reaches its end-of-life. We
+then publish Node-RED 4.x and the cycle continues. The 2.x stream will reach its
+end-of-life soon after the 4.x release. The exact timing of that will be something
 we will need to discuss further.
 
 This proposal means: