Skip to content
This repository has been archived by the owner on May 24, 2024. It is now read-only.

[terra-application-v3][spike] Evaluate existing ApplicationConceptContext to ensure viability within v3 scope #252

Open
tbiethman opened this issue Jul 27, 2021 · 0 comments

Comments

@tbiethman
Copy link
Contributor

tbiethman commented Jul 27, 2021

Story

Description

As a developer, I want to ensure the ApplicationConceptContext's defined API provides value to consumers

Motivation

So that we can decide to release it or remove it from the initial v2.0v3.0 scope.

Definition of Done

We'll know we're done when we have decided whether to release, change, or remove the ApplicationConceptContext.

@tbiethman tbiethman changed the title [terra-application-v2][spike] Evaluate existing ApplicationConceptContext to ensure viability with v2 scope [terra-application-v2][spike] Evaluate existing ApplicationConceptContext to ensure viability within v2 scope Jul 27, 2021
@ryanthemanuel ryanthemanuel added this to the Backlog milestone Jul 29, 2021
@neilpfeiffer neilpfeiffer changed the title [terra-application-v2][spike] Evaluate existing ApplicationConceptContext to ensure viability within v2 scope [terra-application-v3][spike] Evaluate existing ApplicationConceptContext to ensure viability within v2 scope May 21, 2022
@neilpfeiffer neilpfeiffer changed the title [terra-application-v3][spike] Evaluate existing ApplicationConceptContext to ensure viability within v2 scope [terra-application-v3][spike] Evaluate existing ApplicationConceptContext to ensure viability within v3 scope May 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants