That's an interesting idea, especially as these messages like "please don't push" are highlighting the current process is fragile.
Personally I quite like the fact that I can see the previous tags in my history during development but I guess it's just a habit. What do others think? On 22 March 2018 at 11:25, Jordan Gigov <colad...@gmail.com> wrote: > I was thinking to propose this part of the release process gets changed a > bit, so that the commit of a "Final" version never goes into "master", but > remains on a tag. > > Something like this: > # detach head > git checkout > # edit file and change hibernateVersion > editor gradle/base-information.gradle > # commit while in detached state > git add . && git commit > # add tag to current untracked HEAD > git tag 5.whatever > # push the tag > git push origin refs/tags/5.whatever > > > This way the release versions do not pollute the branches, but grow besides > them, and you don't need to issue "do not push" warnings. > > On 22 March 2018 at 13:03, andrea boriero <and...@hibernate.org> wrote: > >> *Please do not push anything to 5.2 branch.Thanks,Andrea* >> _______________________________________________ >> hibernate-dev mailing list >> hibernate-dev@lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hibernate-dev >> > _______________________________________________ > hibernate-dev mailing list > hibernate-dev@lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hibernate-dev _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev