From 7a7f0509f8cb9d2b19aee6edd88b691664295e7a Mon Sep 17 00:00:00 2001
From: Lluis Gifre Renom <lluis.gifre@cttc.es>
Date: Mon, 24 Oct 2022 15:07:11 +0000
Subject: [PATCH] Update new-feature.md

---
 .gitlab/issue_templates/new-feature.md | 40 --------------------------
 1 file changed, 40 deletions(-)

diff --git a/.gitlab/issue_templates/new-feature.md b/.gitlab/issue_templates/new-feature.md
index ec0877164..06ea401cf 100644
--- a/.gitlab/issue_templates/new-feature.md
+++ b/.gitlab/issue_templates/new-feature.md
@@ -18,43 +18,3 @@ You can reference external content (example, demo paper) listed in section "Refe
 
 1. [Reference name](https://reference-url)
 2. Author1, Author2, Author3, et. al., “My demo using feature,” in Conference-Name Demo Track, 20XX.
-
-# Feature Design (for New-Features)
-
-## Clarifications to Expected Behavior Changes
-
-Existing component logic and workflows between components that need to be altered to realize this feature.
-Remember to justify these changes.
-...
-
-## References
-
-List of relevant references for this feature.
-...
-
-## Assumptions
-
-Enumerate the assumptions for this feature, e.g., fix XXX is implemented and merged, specific configurations, specific
-components deployed.
-...
-
-## Impacted Components
-
-List of impacted components: Context, Device, Service, PathComp, Slice, Monitoring, Automation, Policy, Compute, etc.
-Just an enumeration, elaboration of impacts is done below.
-
-## Component1 Impact
-
-Describe impact (changes) on component1.
-...
-
-## Component2 Impact
-
-Describe impact (changes) on component2.
-...
-
-## Testing
-
-Describe test sets (unitary and integration) to be carried out.
-This section can include/reference external experiments, demo papers, etc.
-...
-- 
GitLab