From 30e9d06497ab4e1e54c5bd1dc54fb076758fa337 Mon Sep 17 00:00:00 2001 From: Chris Holmes Date: Wed, 8 Jul 2020 08:54:33 -0700 Subject: [PATCH 1/2] Small updates --- process.md | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/process.md b/process.md index 464b550f4..58c6093e6 100644 --- a/process.md +++ b/process.md @@ -34,15 +34,12 @@ open issues against the milestone. * **Agreement from core team**: The core STAC team should meet (on phone or on gitter) and decided that the release is ready. This should include review of the issues, as well as looking at the spec holistically, to make sure the new changes keep with a coherent whole. -* **Validate Examples**: All examples given in the specification should be programmatically validated against their relevant -schema. For 0.6.0-RC1 and before this is a manual process, but with CirclCI in place this should happen automatically. But -someone should still review that all the schemas have been updated and align with the current state of the spec, as that -can not happen automatically. * **Final Spec Read Through**: There should be a final read through of the core specification to make sure it makes sense and there are no typos, errors, etc. * **Update the version numbers**: There are several places in the spec that use the version number in text or a link. These -include the readme, and the openapi specs. Right now the best thing to do is just a search & replace. Hopefully in the future -there will be scripts or continuous integration to do this. +include the readme and various examples. The schemas also need to be updated, so they can auto-deploy to schemas.stacspec.org, +replacing `/dev/` with `/v/` - corresponding with the tag on github. Right now the best thing to do is just a +search & replace. * **Update the Changelog**: The [changelog](CHANGELOG.md) should be reviewed to make sure it includes all major improvements in the release. And anything in 'unreleased' section should move to the version of the spec to be released. * **Merge dev to master**: As there is no 'build' process, since the specification *is* the markdown files in the github From 187347fd19b163c2fac7cbbc58da86db549c6d6e Mon Sep 17 00:00:00 2001 From: Matthias Mohr Date: Wed, 8 Jul 2020 18:02:04 +0200 Subject: [PATCH 2/2] Update process.md --- process.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process.md b/process.md index 58c6093e6..495cd24f3 100644 --- a/process.md +++ b/process.md @@ -38,7 +38,7 @@ with a coherent whole. and there are no typos, errors, etc. * **Update the version numbers**: There are several places in the spec that use the version number in text or a link. These include the readme and various examples. The schemas also need to be updated, so they can auto-deploy to schemas.stacspec.org, -replacing `/dev/` with `/v/` - corresponding with the tag on github. Right now the best thing to do is just a +replacing `https://schemas.stacspec.org/dev/` with `https://schemas.stacspec.org//` - corresponding with the tag on GitHub, usually including a leading `v`. Right now the best thing to do is just a search & replace. * **Update the Changelog**: The [changelog](CHANGELOG.md) should be reviewed to make sure it includes all major improvements in the release. And anything in 'unreleased' section should move to the version of the spec to be released.