You can not select more than 25 topics
			Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
		
		
		
		
		
			
		
			
				
					
					
					
						
							1.6 KiB
						
					
					
				
			
		
		
		
			
			
			
				
					
				
				
					
				
			
		
		
	
	
							1.6 KiB
						
					
					
				The following steps should be performed before releasing a new storm version. Note that in most case a simultaneous release of carl, storm, pycarl and stormpy is preferred.
- 
Update CHANGELOG.mdTo get all the commits from an author since the last tag execute:git log last_tag..HEAD --author "author_name"
- 
Update used carl version: - Update GIT_TAGinresources/3rdparty/carl/CMakeLists.txt
- Maybe update CARL_MINVERSIONinresources/3rdparty/CMakeLists.txt
 
- Update 
- 
Check that storm builds without errors and all tests are successful - Travis should run successfully
- Invoke the script test_build_configurations.py to build and check different cmake configurations
 
- 
Set new storm version: - Set new storm version in version.cmake
 
- Set new storm version in 
- 
Set new tag in git git tag -a new_version git push origin new_versionNext we push the tag to GitHub. This step requires the GitHub repo to to be configured as a remote. git remote add github https://github.com/moves-rwth/storm.git git push github new_versionThe new tag should now be visible on GitHub 
- 
Add new release in GitHub 
- 
Update Homebrew formula 
- 
Announce new storm version on website