-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Freeze release & frozen release notification #91
Comments
Very interesting :-) |
Oh we agree, the frozen state would not block any merge into a release. It would only be informative :) I was wondering if the freeze command would create a commit or a tag. A commit involves some code modification doesn't it? But a tag may break the release finish/start process? Anyway, glad you find that interesting :) |
One possibility to automate: http://git-scm.com/2010/08/25/notes.html $ git notes --ref=twgit add -m 'YYYYMMDD, frozen' 0385bcc3
$ git push origin refs/notes/twgit
$ git log --show-notes=twgit |
Fantastic :) I'll start with that ! |
Hi!
It would be useful for our QA team to mark a release as 'frozen', a command like :
twgit release freeze
When checking out (or merging into) a frozen release branch, the user would be notified :
twgit release start
Switched to branch 'release-x.x.x'
(i) Local branch 'release-x.x.x' up-to-date with remote 'origin/release-x.x.x'.
(i) 'release-x.x.x' is Frozen.
The idea is to be able to identifiy, on a given release branch, the commits that were performed after the release was frozen, through a simple git log or even a twgit command (twgit release list after_freeze).
What do you think?
Thanks
The text was updated successfully, but these errors were encountered: