← Back to team overview

erma-core team mailing list archive

ERMA Release Process

 

Since we're getting ready to do our second release from github, I figured
that it was a good time to look at our release/review process. Per our
previous discussion features will be promoted to a feature stream (not
master) on your github repo. Once a feature is reviewed it can be merged
into master for the next release. I was looking at git-tag to create a
"version x" that someone could checkout. The idea being whenever we cut
binaries we'd also tag the current commit with "Version X.Y". Does this
sound acceptable?

Matt

Follow ups