Open nassimseddiki opened 11 years ago
Very interesting :-) We cannot block manual git commit and git push on release branch, but "twgit release freeze" could add a technical commit for tracking purpose. Indeed, commands "twgit release start", "twgit feature merge-into-release", "twgit release list", … could make use of this.
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