and I did the same for the M2 cause we didnt have any decision. Issue is in case of re-roll we corrupted the repo with a bad tag we CAN'T delete cause of git nature.
Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2016-02-22 11:02 GMT+01:00 Jonathan Gallimore <jgallim...@tomitribe.com>: > What's the issue with pushing the tag to the Git repository? We used to do > that on SVN, and I think TomEE 1.7.2, 1.7.3 and 7.0.0.M1 all had tags when > the vote was announced. > > Jon > > On Mon, Feb 22, 2016 at 9:56 AM, Romain Manni-Bucau <rmannibu...@gmail.com > > > wrote: > > > Hi guys, > > > > Coming from svn we didnt define any rule for the tag of the releases. > Cause > > of the vote process we shouldn't push the tag to tomee repo directly for > > review but on another repo - cause even if git doesnt allow that they > > shouldnt be mutable. > > > > I know some apache projects use github forks for that. Do we do the same? > > ie we push the tag under vote on our fork then once the vote *passed* we > > push it on tomee repo. > > > > > > wdyt? > > > > Romain Manni-Bucau > > @rmannibucau <https://twitter.com/rmannibucau> | Blog > > <http://rmannibucau.wordpress.com> | Github < > > https://github.com/rmannibucau> | > > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber > > <http://www.tomitribe.com> > > > > > > -- > Jonathan Gallimore > http://twitter.com/jongallimore > http://www.tomitribe.com >
