Update FEDS NRT without interrupting API

How do we want to implement changes in FEDs without interrupting the API?

changed due date to May 01, 2023

By Tempest McCabe on 2023-04-04T19:33:58 (imported from GitLab)

changed milestone to %API Hardening for public facing Veda-dashboard

@greg

By Tempest McCabe on 2023-04-04T19:34:31 (imported from GitLab)

Specifically, the issue is that we need to do more development on the FEDS algorithm (ex: tweak the filtering, expand to new regions, mess with the mechanisms of the algorithm, etc.). Right now we don't have a communal workflow for 1) Developing new features, or 2) merging new features into the "main".

Could we have a "develop "branch and a "stable" branch, and make a plan for "releases" where we merge develop into the stable branch?

There is also a related issue of where we right file outputs for each of these hypothetical branches. Do we want to have two "output" directories?

By Tempest McCabe on 2023-04-10T17:04:05 (imported from GitLab)

Julia suggested that the I/O output directory should be set in with an ENV variable at the job level.

By Tempest McCabe on 2023-04-10T17:32:27 (imported from GitLab)

Eli suggested making a cp of current outputs, and running the develop branch out of that directory.

By Tempest McCabe on 2023-04-10T17:33:43 (imported from GitLab)

The branching plan:

• conus-dps (we may rename to "main") = "the stable branch". This is the branch that generates data to feed the API. We will merge this branch with "develop" when we do intentional releases.
• develop = "The working main branch". This is the branch with the most recent changes and development. When doing new work, create a feature branch off of the develop branch.

By Tempest McCabe on 2023-04-10T18:43:14 (imported from GitLab)

functionally, we have not been doing this, but did protect the main branch.

By Tempest McCabe on 2023-07-10T17:47:41 (imported from GitLab)

closed