As a developer contributing to SGrPython I would like to have automated release of the python generated code from the specification. Currently a developer need to copy the xsd files from this repository into the SGrRepository and build the python package locally. This has led to quite the confusion on which version of SGrSpecifications is implemented in SGrPython.
As a developer contributing to SGrPython, I face challenges in manually copying the XSD files from the SGrSpecifications repository to SGrRepository to build the Python package locally. This process has caused confusion regarding the version of SGrSpecifications implemented in SGrPython.
Suggested Solution
Implementing a CI/CD pipeline would automate and streamline the release process:
Introduce Semantic Versioning (Semver) to SGrSpecifications.
Create a PyPI repository for SGrPythonSpecifications.
Add Github actions
On Merge into Develop:
Build Python module
Release module on PyPI with a Semver-beta tag
On Merge into Master:
Build Python module
Release module on PyPI with a Semver
Increment Semver
Acceptance Criteria
[ ] SGrSpecification versioning
[ ] PyPi Repository
[ ] GitHub Actions
[ ] Develop pipeline
[ ] Master pipeline
Open Questions
Is there an existing versioning schema for SGrSpecifications?
How was this issue addressed in the Java implementation?
User Voice
As a developer contributing to SGrPython I would like to have automated release of the python generated code from the specification. Currently a developer need to copy the xsd files from this repository into the SGrRepository and build the python package locally. This has led to quite the confusion on which version of SGrSpecifications is implemented in SGrPython.
As a developer contributing to SGrPython, I face challenges in manually copying the XSD files from the SGrSpecifications repository to SGrRepository to build the Python package locally. This process has caused confusion regarding the version of SGrSpecifications implemented in SGrPython.
Suggested Solution
Implementing a CI/CD pipeline would automate and streamline the release process:
Acceptance Criteria
Open Questions
Is there an existing versioning schema for SGrSpecifications? How was this issue addressed in the Java implementation?