Discuss approach to branch strategy for this epic

[heidimok]

Context

This is part of EPIC: MI Workflow Redesign #270

While the MI Workflow Redesign is taken place, curators needs a place to manually try out changes partway through without disrupting the production or staging version of the MI.

Action

• Talk to Carson about how to split work so that test server has the new implementation
• Let the team know what the approach will be for sharing development progress

[heidimok]

Suggested approach after talking with John and Ed Aug 22:

• Could feature flag. Django feature flagging library or just setting a cookie if curator's want to test it out.
• We would aim to close out each story one by one after it's tested.
• We won't need a separate branch. Will continue pushing to dev. The further we diverge from dev, the longer it'll take to bring it back.
• Will keep things less confusing for team and Carson as well.

[heidimok]

Closing this as the final decision was made to use the dev environment as the sandbox environment for the new workflow.

http://admgdev.nasa-impact.net/