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

I&T Tasks for Sprints ending 10/20/22, 11/10/22, 12/1/22, 12/22/2022 I&T tasks #30

Open
24 of 27 tasks
tloubrieu-jpl opened this issue Dec 22, 2022 · 6 comments
Open
24 of 27 tasks

Comments

@tloubrieu-jpl
Copy link
Member

tloubrieu-jpl commented Dec 22, 2022

🟢 Issues Ready For I&T

Information Model:

Registry & web API

Validate

DOI Service

📜 Test Plan / Procedure

⚙️ Automated Tests

@jordanpadams jordanpadams changed the title Sprint ending 12/22/2022 I&T tasks I&T Tasks for Sprints ending 10/20/22, 11/10/22, 12/1/22, 12/22/2022 I&T tasks Dec 23, 2022
@jordanpadams
Copy link
Member

@viviant100 @tloubrieu-jpl combined all the tickets that I think we need test cases for since B13.0 I&T.

I think we need to come up with a more automated/refined process for this in the future. Maybe continuously generate an in-progress RDD. We could even update to not only have the I&T column to designate something that needs to be tested, but also an additional label to indicate testing complete (or at least test cases developed).

@viviant100
Copy link

@jordanpadams sounds good. A changelog will also be helpful for I&T to know what's fixed/updated during the I&T cycle.

@jordanpadams
Copy link
Member

@viviant100 what changelog are we referring to here? changelog for the RDD?

@viviant100
Copy link

A changelog for the RDD would work, or anything that indicates what changes since last delivery to I&T so I&T can V&V those new changes.

@tloubrieu-jpl
Copy link
Member Author

I would rather focus on developing better change logs for the repositories which could contain tags on tested features and have links to those change logs in a work document for I&t or by using the software summary of the snapshot build (which need to be updated more regularly but this has been broken since we cannot update on the main branch anymore). To me the primary software management tool is standard git repository based, the rdd is more a specific view for our 6 months build cycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants