Page History

...

The downloadable release is a copy of the demo site made available for use on your local machine.  You will need virtualbox to run the images and meet the minimum hardware requirements to run all of the virtual machines at once for full functionality. With this you may make configuration changes suited to your environment and experiment with the software on your local machine. 

...

Maturity model of

...

code

...

Steps

1. Code is committed to a community repo.
2. Unit tests are run, if availableCI checks code repository for latest changes.
3. Code is compiled / packaged and made into an artifact on CI.  Unit tests are also run if available.
4. Artifact is deployed to our dev environment. Manual User Acceptance Testing occurs, testing  Manual testing may occur, for functionality and interoperability. Test interoperability against staging (which should mirror prod).
5. Release

...

1. artifact is deployed.  Bamboo build agent runs integration tests.  Users will do User Acceptance Testing to determine if all expected functionality works as expected.
2. If all tests pass, make a Release of OpenHIE, which specifies OpenHIE
3. Code is tagged as release in code repository.
4. If it is determined that, it should not break anything deploy it to staging.
   
   1. If it will break interoperability, determine dependency and wait.
5. Run automated Integration Tests.
6. Allow users to perform User Acceptance Testing.
7. Note all versions as a Demo Release. (e.g. Demo v0.2.0 1 = OpenEMPI OpenHIM 2.3.0, OpenHIM OpenEMPI 2.39.6, etc ...etc).  Deploy using automated scripts to demo environment. 

...

...

Status

Sandbox/Staging

...