Release BuildingSync 2.7.0

.github/workflows/ci.yml

@@ -45,7 +45,7 @@ jobs:
           DJANGO_SETTINGS_MODULE: bsyncviewer.settings.gh_actions
         run: tox -e ${{ matrix.tox_env }}
       - name: Coveralls
-        if: ${{ success() && matrix.tox_env == 'python' }}
+        if: ${{ success() && matrix.tox_env == 'python' && matrix.python-version == '3.9' }}
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: coveralls --service=github

CHANGELOG.md

@@ -1,11 +1,24 @@
 # BuildingSync Use Case Selection Tool
 
-## Version 1.3.0
+## Version 1.4.0
 
-- Replaces the old `selection-tool` names with `buildingsync-website`.
-- Release BuildingSync 2.6
-- Update documentation for BuildingSync 2.6
+Date Range: 10/05/23 - 09/30/25
+
+- Release BuildingSync 2.6, 2.7
+- Update documentation for BuildingSync 2.6, 2.7
 - Prep for BEDES v2.6 mapping
+- Replaces the old `selection-tool` names with `buildingsync-website`.
+- Updates to support Python 3.9 (older versions have been deprecated)
+- Support latest version of jellyfish
+
+New Issues:
+
+- New Issue [#191](https://github.com/BuildingSync/BuildingSync-website/issues/191), BEDES v2.6 mapping
+
+Closed Issues and Features:
+
+- Fixed [#189](https://github.com/BuildingSync/BuildingSync-website/issues/189), Download Examples button broken
+- Fixed [#192](https://github.com/BuildingSync/BuildingSync-website/issues/192), BEDES v2.5 mapping
 
 ## Version 1.2.0
 

README.md

@@ -287,11 +287,12 @@ Follow these steps to add a new schema version to the selection tool:
 2. Convert existing use cases schematron files to the new schema. Add the new use cases.
 3. When the use cases have been reviewed, make them public in the admin interface. Add the schematron file and hit "Save" once and wait for each use case.
 4. Update the versions in the DEFAULT_SCHEMA_VERSION in the dev.py, gh_actions.py, and docker.py with the latest release.
-5. Create XML example files and place them in the `bsyncviewer/lib/validator/examples/schema<VERSION>` directory. Make sure that the example_files.zip file is updated if any of the example files have changed (This is likely since the new example files will be pointing to the new schema).
+5. Add the schema file into `bsyncviewer/lib/buildingsync_schemas`. Create XML example files and place them in the `bsyncviewer/lib/validator/examples/schema<VERSION>` directory. Make sure that the example_files.zip file is updated if any of the example files have changed (This is likely since the new example files will be pointing to the new schema).
 6. Test the validator with a local new XML example file.
 7. Create PR and merge with the changes.
 8. Reparse BEDES terms to map them to the new schema following the steps in the BEDES section above.
 9. Deploy website on production.
+10. If needed, update CHANGELOG and create PR from develop to main for new release of this site (see [release_instructions.md](docs/release_instructions.md)).
 
 ### Adding Examples from the TestSuite repo
 

app_version.txt

@@ -1 +1 @@
-1.1.2
+1.4.0

bsyncviewer/lib/schema_parser.py

@@ -569,7 +569,7 @@ def _walk_sequence_or_choice_element(self, parent_element, root_path, current_tr
                 num_added += 1
                 return_rows.append({
                     'name': elem.name,
-                    'description': "; ".join([anno.documentation for  anno in elem.annotations]),
+                    'description': "; ".join([anno.documentation for anno in elem.annotations]),
                     'type': elem.name,
                     'parent_path': root_path,
                     'path': root_path + '.' + elem.name,
@@ -613,7 +613,7 @@ def _walk_sequence_or_choice_element(self, parent_element, root_path, current_tr
                 num_added += 1
                 return_rows.append({
                     'name': elem.name,
-                    'description': "; ".join([anno.documentation for  anno in elem.annotations]),
+                    'description': "; ".join([anno.documentation for anno in elem.annotations]),
                     'path': root_path + '.' + elem.name,
                     'type': NamedElement.my_string(),
                     'parent_path': root_path,
@@ -648,7 +648,7 @@ def _walk_sequence_or_choice_element(self, parent_element, root_path, current_tr
                 ref_type_clean = elem.ref_type
             return_rows.append({
                 'name': ref_type_clean,
-                'description': "; ".join([anno.documentation for  anno in elem.annotations]),
+                'description': "; ".join([anno.documentation for anno in elem.annotations]),
                 'path': root_path + '.' + ref_type_clean,
                 'type': ReferenceElement.my_string(),
                 'parent_path': root_path,