From 544de32c1753e8c5ce63753a6ce585e6ce921562 Mon Sep 17 00:00:00 2001 From: Anatoli Babenia Date: Tue, 23 Jun 2020 10:35:21 +0300 Subject: [PATCH 1/3] FAQ.md Link reactions to sorted PRs and issues --- docs/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index 180bc97de3a..ce8b8e64b50 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -17,7 +17,7 @@ Unfortunately, due to the volume of issues and new pull requests we receive, we ### How do you decide what gets merged for each release? -The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue/PR description as these can be easily discovered. Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. +The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://github.com/terraform-providers/terraform-provider-aws/issues?q=is%3Aopen+sort%3Areactions-%2B1-desc) to the original issue/PR description as these can be easily discovered. Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. We publish a [roadmap](../ROADMAP.md) every quarter which describes major themes or specific product areas of focus. From 5495f60b4cf6a98d7b8c0101b6ed0a8e5900a97e Mon Sep 17 00:00:00 2001 From: Anatoli Babenia Date: Tue, 14 Jul 2020 11:47:00 +0300 Subject: [PATCH 2/3] FAQ.md Accept suggestion to keep old link as well Co-authored-by: Brian Flad --- docs/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index ce8b8e64b50..cd48018b078 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -17,7 +17,7 @@ Unfortunately, due to the volume of issues and new pull requests we receive, we ### How do you decide what gets merged for each release? -The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://github.com/terraform-providers/terraform-provider-aws/issues?q=is%3Aopen+sort%3Areactions-%2B1-desc) to the original issue/PR description as these can be easily discovered. Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. +The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue/PR description as these can be [easily discovered](../issues?q=is%3Aopen+sort%3Areactions-%2B1-desc). Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. We publish a [roadmap](../ROADMAP.md) every quarter which describes major themes or specific product areas of focus. From 4d40329fe10f5d27ad45290985ec79e71974f130 Mon Sep 17 00:00:00 2001 From: Anatoli Babenia Date: Tue, 14 Jul 2020 11:51:18 +0300 Subject: [PATCH 3/3] FAQ.md Relative link to issues didn't work --- docs/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/FAQ.md b/docs/FAQ.md index cd48018b078..cbba76e1dbb 100644 --- a/docs/FAQ.md +++ b/docs/FAQ.md @@ -17,7 +17,7 @@ Unfortunately, due to the volume of issues and new pull requests we receive, we ### How do you decide what gets merged for each release? -The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue/PR description as these can be [easily discovered](../issues?q=is%3Aopen+sort%3Areactions-%2B1-desc). Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. +The number one factor we look at when deciding what issues to look at are your 👍 [reactions](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue/PR description as these can be [easily discovered](https://github.com/terraform-providers/terraform-provider-aws/issues?q=is%3Aopen+sort%3Areactions-%2B1-desc). Comments that further explain desired use cases or poor user experience are also heavily factored. The items with the most support are always on our radar, and we commit to keep the community updated on their status and potential timelines. We publish a [roadmap](../ROADMAP.md) every quarter which describes major themes or specific product areas of focus.