-
Notifications
You must be signed in to change notification settings - Fork 48
Releasing Sirius
####1. Make a Release Branch
To indicate that you are doing a release, it is a good idea to create a separate branch for the release and create a pull request.
git branch release-x.x.x
git checkout release-x.x.x
Only two files should change in a release commit, pom.xml
and build.sbt
. Only the version number of the project should change in these files as well.
The commit message should contain every commit, which should be the output from
git log --pretty --oneline
The commits should be organized into three sections:
- New Features
- Bugfixes
- Documentation/Project Maintenance
See 1bda7c9 for an example
####1. Increment Version and Tag ####2. Build and Deploy Scala Docs ####3. Deploy Scala Artifacts ####4. Increment Version to Next Snapshot
Copyright 2013-2017 Comcast Cable Communications Management, LLC
Using Sirius
Getting started with Sirius
Configuring Sirius
How to Deploy Sirius
Reference Applications
Migrations and Release Notes
Migration Guide 1.1.x to 1.2.x
Release Notes 2.0.0
Migration Guide 1.2.x to 2.0.x
Developing Sirius
Getting Started
Contributing Guildelines
License
Releasing Sirius
Scaladocs
Test Timeout Failures
Transaction Log
Implementation
Live Compaction
waltool
Other