Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • 2.3.1
  • 2.2.2
  • 2.2.1
  • 2.2.0
  • 2.1.0
  • 2.0.0
  • 1.4.1
  • 1.4.0
  • 1.3.1
  • 1.3.0
  • 1.2.0
12 results
Blame Permalink
Code owners
Assign users and groups as approvers for specific file changes. Learn more.
README-release.md 980 B

Release Process

  1. User has cloned the blessed repository and has write access to it.
  2. User has updated the version field in composer.json. If this does not match the version in the tag name, the release cycle will complete, BUT composer will issue an error when users try to install the dependency.
  3. User runs the following command: php phing.phar release -Dversion=1.2.3 -Dbranch=myBranch
  4. The designated branch is checked out.
  5. A tag is created with the name equal to the version number with no extra characters
  6. The repository is pushed to origin with all tags.

The end result is a new tag in the remote repository equal to the version number. Composer clients will now pick up on the new version number.

For instance, if version 1.1.0 was released, a composer client with the following dependency would pick up on the new change:

"require": {
	"uwmadison_doit/rpc-netid-php": "1.*"
}