Closed jamsden closed 2 years ago
The vote has passed: https://lists.oasis-open-projects.org/g/oslc-op-pgb/topic/oslc_tracked_resource_set/84998115
OASIS ticket: https://issues.oasis-open.org/browse/TCADMIN-4054
Publication: https://lists.oasis-open-projects.org/g/oslc-op/topic/your_psd01_for_oslc_tracked/85355975
@jamsden Chet and Paul flagged many issues in the draft, could please go over the ticket and the email and mirror their changes to the source, please? Or at least create Github issues to cover all their requests and target PSD02/PS01 milestone.
Specs section on the website needs to be updated with links from https://lists.oasis-open-projects.org/g/oslc-op/message/632
@jamsden are we ready to tag 68b38ccf2a3182c991b51dca68c42ef8531f4bbe with trs-v3.0-psd01
?
I should update the zip file?
No need, I think the ZIP is only for the voting and OASIS admin.
https://github.com/oslc-op/oslc-specs/issues/546
Spec links and the NS files are updated
Tag is pushed
@jamsden for the future, this EPIC should contain the "Copy it from [[EPIC checklist]]" contents and the outer list is a guidance to be perused on the wiki when needed. Happy to update the checklist if you think it will help.
Overall process
prettier --write specs/%your_spec%/
. Pro tip: run prettier on save using https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode#user-content-format-on-saveoslc-specs
and use the checklist below as the issue description. Also put the EPIC issue under the newly created milestone.%shortname%-v%version%-%STAGE%%REVISION%
(e.g.rm-v2.1-PSD02
) once the spec has been deployed to staging AND Chet has given his LGTM in the issue you created in theoasis-open-projects/administration
repo.open-services.net/ns
with a link to a specific format or version of a vocabulary. Check accessibility using https://achecker.ca/checker/index.php, fixing issues that seem importantEPIC checklist
Copy it from [[EPIC checklist]]
Release ZIP generation steps
python3 -m http.server 8000
orpython -m SimpleHTTPServer 8000
ornpm install -g local-web-server
and then runws
. Access from local filesystem may cause JS errors connected with security around local file access. You browser may render file and http protocols differently. DO NOT USE BROWSERSYNC AT THIS STAGE! DO NOT SIMPLY OPEN FILES FROM THE FILESYSTEM, YOU MUST RUN A WEB SERVER!PGB notice template
PGB ballot template (only for PSDs, further ballots are opened by Chet)