From 0a9cdc5b77016587939b642289495456aca7a4b7 Mon Sep 17 00:00:00 2001 From: Nisanthan Nanthakumar Date: Tue, 23 May 2023 15:20:28 -0700 Subject: [PATCH] rfc(decision): escalating-forecasts-merged-issues --- README.md | 1 + text/0095-escalatingforecastsmergedissues.md | 35 ++++++++++++++++++++ 2 files changed, 36 insertions(+) create mode 100644 text/0095-escalatingforecastsmergedissues.md diff --git a/README.md b/README.md index 32101947..2218bbb9 100644 --- a/README.md +++ b/README.md @@ -47,3 +47,4 @@ This repository contains RFCs and DACIs. Lost? - [0086-sentry-bundler-plugins-api](text/0086-sentry-bundler-plugins-api.md): Sentry Bundler Plugins API - [0088-fix-memory-limitiations-in-session-replays-access-pattern](text/0088-fix-memory-limitiations-in-session-replays-access-pattern.md): Fix Memory Limitiations in Session Replay's Access Pattern - [0092-replay-issue-creation](text/0092-replay-issue-creation.md): Replay Issue Creation +- [0095-escalatingforecastsmergedissues](text/0095-escalatingforecastsmergedissues.md): escalating-forecasts-merged-issues diff --git a/text/0095-escalatingforecastsmergedissues.md b/text/0095-escalatingforecastsmergedissues.md new file mode 100644 index 00000000..6dd7405c --- /dev/null +++ b/text/0095-escalatingforecastsmergedissues.md @@ -0,0 +1,35 @@ +- Start Date: 2023-05-23 +- RFC Type: decision +- RFC PR: https://github.com/getsentry/rfcs/pull/95 +- RFC Status: draft + +# Summary + +One paragraph explanation of the feature or document purpose. + +# Motivation + +Why are we doing this? What use cases does it support? What is the expected outcome? + +# Background + +The reason this decision or document is required. This section might not always exist. + +# Supporting Data + +[Metrics to help support your decision (if applicable).] + +# Options Considered + +If an RFC does not know yet what the options are, it can propose multiple options. The +preferred model is to propose one option and to provide alternatives. + +# Drawbacks + +Why should we not do this? What are the drawbacks of this RFC or a particular option if +multiple options are presented. + +# Unresolved questions + +- What parts of the design do you expect to resolve through this RFC? +- What issues are out of scope for this RFC but are known?