You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+21-4Lines changed: 21 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,19 +26,36 @@ Inquires for commercial support can be directed to [[email protected]](info@alpho
26
26
27
27
## Related Projects
28
28
29
-
[Clinical Quality Language](https://github.com/cqframework/clinical_quality_language) - Tooling in support of the CQL specification, including the CQL verifier/translator used in this project.
29
+
[Clinical Quality Language](https://github.com/cqframework/clinical_quality_language) - Tooling in support of the CQL specification, including the CQL verifier/translator and engine used in this project.
30
30
31
-
[CQL Engine](https://github.com/DBCG/cql_engine) - Open source Java-based ELM evaluation engine.
31
+
[Clinical Reasoning](https://github.com/cqframework/clinical-reasoning) - Provides for complete evaluation of CQL logic, as well as implementations of operations defined by the FHIR Clinical Reasoning module and related FHIR IGs.
32
32
33
-
[CQL Evaluator](https://github.com/DBCG/cql-evaluator) - Integrates the CQL Translator and CQL Engine into an execution environment, and provides implementations of operations defined by FHIR IGs.
33
+
[VSCode Plugin](https://github.com/cqframework/vscode-cql) - Makes use of this CQL Language Server to provide CQL language capabilities for the VSCode environment.
34
34
35
35
## Commit Policy
36
36
37
37
All new development takes place on `<feature>` branches off `master`. Once feature development on the branch is complete, the feature branch is submitted to `master` as a PR. The PR is reviewed by maintainers and regression testing by the CI build occurs.
38
38
39
39
Changes to the `master` branch must be done through an approved PR. Delete branches after merging to keep the repository clean.
40
40
41
-
Merges to `master` trigger a deployment to the Maven Snapshots repositories. Once ready for a release, the `master` branch is updated with the correct version number and is tagged. Tags trigger a full release to Maven Central and a corresponding release to Github. Releases SHALL NOT have a SNAPSHOT version, nor any SNAPSHOT dependencies.
41
+
Merges to `master` trigger a deployment to the Maven Snapshots repositories.
42
+
43
+
Once ready for a release, the `master` branch is updated with the correct version number and is tagged. Releases SHALL NOT have a SNAPSHOT version, nor any SNAPSHOT dependencies. Releases must be deployed manually.
44
+
45
+
## Release Process
46
+
47
+
To release a new version of the language server:
48
+
49
+
1. Update master to be a release version (and all the reviews, bug fixes, etc. that that requires)
50
+
1. Example version: `3.8.0`
51
+
2. Passed CI Build = ready for release
52
+
3. Use the following command to release from your local build (releases are not automatic)
0 commit comments