-
Notifications
You must be signed in to change notification settings - Fork 0
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
B12.0 Refine AWS Registry Deployment Strategy #2
Comments
📆 April status: On schedule |
📆 May status: delayed due to issues with SA's deployment of Fargate in AWS. able to work other tasks in parallel as we await the deployment, so no impact on other tasks identified at this time. |
📆 June status: additional delays continue due to lack of SA resources to assist with Fargate / AWS issues. SA resource issues have been resolved, but 3 tasks are still delayed for preparing DN deployments. no foreseen impact on build deliverables at this time, but another delay may have impacts. |
📆 July status: delays per June setbacks. no foreseen impact on build deliverables at this time, but another delay may have impacts. |
📆 August status: WIP. delays due to lack of availability of SA team. on schedule for B12.0 delivery. tightly coupled with NASA-PDS/pds-registry-app#152 |
All necessary B12.0 tasks completed. Other tasks can be deferred to B12.1. |
No description provided.
The text was updated successfully, but these errors were encountered: