Sounds like a plan that is fine with me given that this is just a minor change.
2017-07-01 18:22 GMT+02:00 Stefan Bodewig <[email protected]>: > On 2017-06-30, Dominik Psenner wrote: > > > While working on the Jenkinsfile so that jjenkins builds all kinds of > > branches for us I noticed that pr-11 made it into master without us > carving > > out a release. > > It's been my fault. I committed it to master out of habit and merged it > to develop later when I realized my mistake. > > > If not, should we rewind master to a previous commit so long this > > change is not published? > > It has been pushed to master and synced to github already. We can't know > whether anybody has checked them out already. Force pushing in order to > rewind the branch doesn't sound like a good idea to me. I'd leave them > in master until we cut the next release. > > Stefan > -- Dominik Psenner
