[hibernate-issues] [Hibernate-JIRA] Commented: (HHH-5660) Leverage Git for better release process

From what I understand, other people are guaranteed that somebody from the Hibernate team tagged the release and thus certified it. Useful when the repo is a clone of a clone of a clone (ie who is the real Jango Fett in Star Wars).

Leverage Git for better release process --------------------------------------- Key: HHH-5660 URL: http://opensource.atlassian.com/projects/hibernate/browse/HHH-5660 Project: Hibernate Core Issue Type: Improvement Affects Versions: 3.6.0 Reporter: Steve Ebersole Assignee: Steve Ebersole Fix For: 3.6.1 Initially thinking: # pre-release ## Update versions/scm-urls # release ## `mvn clean deploy` # post-release ## `git commit` - commits the workspace state for tagging ## `git tag -s 3.6.1.Final -m 'tagging 3.6.0 release'` - creates a *signed* tag, do we need/want signed tags? ## `git push origin 3.6.1.Final` - pushes the tag to origin (GitHub) ## Update the versions/scm-urls for the next dev cycle ## `git commit` ## `git push origin`