-
Notifications
You must be signed in to change notification settings - Fork 132
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1062 from finos/fdc3-2.1-release
FDC3 2.1 release
- Loading branch information
Showing
249 changed files
with
19,320 additions
and
1,768 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,6 @@ | ||
| --- | ||
| id: fdc3-standard | ||
| title: FDC3 2.1 (pre-draft) | ||
| title: FDC3 2.2 (pre-draft) | ||
| sidebar_label: Abstract | ||
| --- | ||
|
|
||
|
|
||
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,62 @@ | ||
| # FDC3 website readme | ||
|
|
||
| ## Releasing new versions of the Standard | ||
|
|
||
| To create a new version of the website, a number of NPM scripts need to be run that will create the version and update certain content within it (as automatically as possible). There are then a number of additional manual steps to run. | ||
|
|
||
| 1. Enter the website directory and make sure the site has been built: | ||
|
|
||
| ```bash | ||
| cd website | ||
| npm run build | ||
| ``` | ||
|
|
||
| 2. Then run the versioning script - this should work cross-platform, but can be brittle... | ||
| - edit *website/package.json* and replace the version number in the `version` script to the version number you wish to create: | ||
| `version": "cross-env-shell VERSION=2.1 ...` | ||
| - Run it: | ||
|
|
||
| ```bash | ||
| npm run version | ||
| ``` | ||
|
|
||
| - Check the reported version number is as expected and that the scripts ran without errors. | ||
|
|
||
| 3. Check that the version script has done what it needs to: | ||
| - The new website version should exist in _website/versioned_docs_ | ||
| - Links to schema files should have been updated to the versioned links, e.g. check *website/versioned_docs/version-2.1/context/ref/Context.md* has a link like <https://fdc3.finos.org/schemas/2.1/context/context.schema.json> (where '2.1' would be 'next' in the pre-draft) | ||
| - The overview docs (often called spec.md) should have had '(next)' in their titles replaced with the version, e.g. '(2.1)', e.g. check *website/versioned_docs/version-2.1/api/spec.md* | ||
| - A new set of schemas should exist in *website/static/schemas* | ||
| - Check all schema files/folders got copied, including *api/*, *context/*, *bridging/*, *bridgingAsyncAPI/* and the *appd* files. | ||
| - Check that their `$id` fields were updated to match their new URLs, e.g. *website/static/schemas/2.1/context/context.schema.json* should have an `$id` that looks like: `"$id": "https://fdc3.finos.org/schemas/2.1/context/context.schema.json"` (where '2.1' would be 'next' in the pre-draft) | ||
| - Check that the appD schema's `version` field has been updated, i.e. *website/static/schemas/2.1/appd.schema.json* should have `"version": "2.1",` (where '2.1' would be 'next' in the pre-draft) | ||
| 4. Make a number of additional manual changes: | ||
| - Edit the titles of *website/versioned_docs/version-2.1/fdc3-intro.md* and *website/versioned_docs/version-2.1/fdc3-standard.md* to remove '(pre-draft') | ||
| - Edit the titles of *docs/fdc3-intro.md* and *docs/fdc3-standard.md* to use the next planned version number | ||
| - Edit the last Standard version's abstract to update its status and dates, e.g. *website/versioned_docs/version-2.0/fdc3-standard.md* | ||
| - Edit the new Standard version's abstract to update its status and dates, e.g. *website/versioned_docs/version-2.1/fdc3-standard.md* | ||
| - Edit the `Version` element of `themeConfig.navbar.items` in *website/docusaurus.config.js* to include the new version as the first element. | ||
| 5. Edit CHANGELOG.md to mark the unreleased changes as teh new version and create a new unreleased section for the next version. | ||
| - Note that the title of the release section usually includes a compare link for the previous version. These are based on tags - the tag needed will not exist yet, but is created in a later step. It should be fine to set it to what the tag name will be. | ||
| 6. If creating a new NPM module version at the same time, then | ||
| - Return to the root of the repository (i.e. parent dir of the *website* dir) and edit *package.json*, | ||
| - Set the `version` filed to the new standard version - but consider appending a beta label, e.g.: `"version": "2.1.0-beta.1",` | ||
| - The new NPM module will be built and submitted to NPM via a Github action automatically when this PR is merged. | ||
| 7. Test you changes locally by running the site: | ||
| ```bash | ||
| cd website | ||
| npm run build | ||
| npm run start | ||
| ``` | ||
| 8. Create a PR and send out details for other maintainers to review and test. | ||
| 9. Merge the PR - website and NPM module will be deployed automatically. | ||
| 10. Goto <https://github.com/finos/FDC3/releases> and create a new release and tag for the new version. | ||
| - Copy the change log into the release description. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # Intro | ||
|
|
||
| Quicktype, the chosen generation tool currently has some limitations that prevent fully automatic schema generation from the existing TS types. For example it can not handle interfaces that contain methods in their definition. It also fails to generate schemas even if a type contains unused references to other types or interfaces that contain async functions (Promise return types). Therefore, in order to generate the `api\schemas\api.schema.json` some manual intervention was needed. | ||
|
|
||
| Once these limitations are not an issue the `api\schemas\t2sQuicktypeUtil.js` script should be moved to the root level of the project and a new npm script `"api-schema-gen": "node t2sQuicktypeUtil.js src/api schemas/api/api.schema.json"` should be added. | ||
|
|
||
| `api\schemas\api.schema.json` - partially auto-generated schema from the existing `src\api` types. | ||
| `api\schemas\baseImplementationMetadata.schema.json` - Used by bridging types that leave out the metadata of the calling application as it does not apply to bridging. | ||
| `api\schemas\intentResolution.schema.json` - At the moment it is not possible to auto-generate this due to limitations in the generation tool (quicktype) | ||
| `api\schemas\t2sQuicktypeUtil.js` - Script used to run the generation of the schema from the types. Should be moved to the root level of the repo once fully-automated generation can be achieved. |
Oops, something went wrong.