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

Versions of modules should be controlled in centralized location #52

Closed
chan-hoo opened this issue Feb 13, 2024 · 0 comments · Fixed by #63
Closed

Versions of modules should be controlled in centralized location #52

chan-hoo opened this issue Feb 13, 2024 · 0 comments · Fixed by #63
Assignees
Labels
NCO EE2 compliance For EE2 compliance to meet NCO implementation standards

Comments

@chan-hoo
Copy link
Collaborator

To meet the NCO standards, the versions of the modules used in the tasks should be controlled in the versions directory (NCO standards, pp 19, Table 3). It should contain build.ver and run.ver to compile and run, respectively.

@chan-hoo chan-hoo added the enhancement New feature or request label Feb 13, 2024
@chan-hoo chan-hoo self-assigned this Feb 13, 2024
@chan-hoo chan-hoo added NCO EE2 compliance For EE2 compliance to meet NCO implementation standards and removed enhancement New feature or request labels Feb 19, 2024
@chan-hoo chan-hoo moved this from Todo to In Progress in land-DA_workflow_management Feb 27, 2024
@chan-hoo chan-hoo linked a pull request Feb 27, 2024 that will close this issue
15 tasks
@chan-hoo chan-hoo moved this from In Progress to In Review in land-DA_workflow_management Feb 27, 2024
@github-project-automation github-project-automation bot moved this from In Review to Done in land-DA_workflow_management Mar 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NCO EE2 compliance For EE2 compliance to meet NCO implementation standards
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant