Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Code refresh from upstream #198

Open
TonyWildish-BH opened this issue Nov 8, 2024 · 2 comments
Open

Code refresh from upstream #198

TonyWildish-BH opened this issue Nov 8, 2024 · 2 comments
Assignees
Labels
EPIC - Deployment process How to manage deployment/upgrade/rollback in production Later Don't worry about this now MVP Things that need to be considered for the MVP release

Comments

@TonyWildish-BH
Copy link
Collaborator

No description provided.

@TonyWildish-BH
Copy link
Collaborator Author

TonyWildish-BH commented Nov 8, 2024

We should look again at the upstream repo for updates, there have been several.

  • Evaluate the upstream changes
  • Decide if we want them locally
  • Merge, test, deploy
  • Document the procedure
    I have some semi-documented notes on how to do this that can form a basis

Success will be defined by:

  • Updated codebase deployed in the Beta
  • Process defined and documented for repeating this in 3 months time.

@TonyWildish-BH TonyWildish-BH added MVP Things that need to be considered for the MVP release EPIC - Deployment process How to manage deployment/upgrade/rollback in production Later Don't worry about this now labels Nov 8, 2024
@BIOKU-BH
Copy link

BIOKU-BH commented Dec 9, 2024

Tony, Could you kindly share with me the semi-documented notes on this? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
EPIC - Deployment process How to manage deployment/upgrade/rollback in production Later Don't worry about this now MVP Things that need to be considered for the MVP release
Projects
None yet
Development

No branches or pull requests

2 participants