Closed matthewtiscareno closed 5 months ago
@matthewtiscareno I created a new release/1.0.0
branch, and then manually triggered the build of the LDD, created a PR, merged, and the release has been tagged. 🎉
Okay, I see how you did that. I can do similarly in the future.
Thanks, @jordanpadams!
@matthewtiscareno these 4 LDDs have been posted to https://pds.nasa.gov/datastandards/dictionaries/index-missions.shtml#vgr!
Great! Thank you again, @c-suh and @jordanpadams
@rgdeen: Please proceed with using this LDD
Is the LDD IngestLDD in Github?
Yes
Has the LDD Namespace been registered in the Namespace Registry?
Yes
Need by date?
No response
Need by date rationale
@rgdeen is ready to validate data products against this dictionary.
GitHub Tagged Release of LDD
The corresponding URL would be https://github.com/pds-data-dictionaries/ldd-vgr/releases, but there are no releases there.
I just now merged v1.0.0.0, but I see only now from these instructions that that merge should have had the word "release" in the branch name. Of course, you cannot change the name of a branch once you've created it, so I was not able to meet that criterion. I'm hoping EN can help me with whatever is still needed for this dictionary to be fully published and released.
PDS4 IM Versions to Release
1.16, 1.17, 1.20, 1.21
LDD Submission Package
No response