Release workflow¶

Pre release¶

• Nosetests, check coverage
• Mypy checks
• Translations
• Update version number
• Update version number in Sphinx
• Update changelog
• Update upgrade and installation notes
• Prepare release statement

Release¶

• Merge develop to master
• Push to GitHub
• Upgrade demo versions, if database upgrades:
  

  pg_dump openatlas_demo > /var/lib/postgresql/openatlas_demo.sql
  pg_dump openatlas_demo_dev > /var/lib/postgresql/openatlas_demo_dev.sql
  

• Test demo
• Upgrade CRAWS and ACDH-CH instances
  • Backup database
  • Check logs
  • Upgrade
  • Raise version at online versions
  • Send newsletter

Post release¶

• Update Redmine roadmap
• Git tag
• Push master and tags to GitHub, GitLab and Bitbucket
• Update GitHub latest release
• Raise version of develop branch

News¶

Maybe use the news feature for release information e.g.

h2. version:5.0.0

You find a list of all releases at the "Roadmap":/projects/uni/roadmap. For a complete list of issues click on the version number. To see the issue description click on the issue number. Technical update information can be found in the application at *install/upgrade/upgrade.md.*

This is a major release with a lot of additions and changes.

h3. #1048: Bootstrap layout

The layout was completely overhauled with the "Bootstrap":https://getbootstrap.com/ framework. 
One of the main reasons was a more responsive interface e.g. showing larger maps. 
Although some things moved around the general workflow should be the same.

h3. #1050: API

A first version of an API to make it easier for other application to use data from OpenAtlas directly was implemented. 
More information can be found here: [[documentation|API]]

h3. #1089: Human Remains

Archeologists can now enter human remains which work similar to finds.

h3. #1136: Map enhancements

Besides larger maps (depending on screen size) there are a few new features like switching from cluster to marker on the fly.
Also the display of archeological features was enhanced a lot.

h3. #1138: Display usage of CIDOC CRM classes and properties

In the model it is now shown which classes and properties are used how often. Because this reveals entered data the link was moved from the public menu to the index page seen after login.

h3. #1175: Additional date checks

Involvement dates were already checked against actor lifespan but now there are checks between event dates and involvement dates too.
You might want to run date checks again (Admin -> Check dates) to test your data for inconsistency