Hi We need to hold the release until we get this either reverted or find out why it causes some existing unit tests to fail https://issues.apache.org/jira/browse/CAMEL-12610
On Sun, Jul 8, 2018 at 9:58 PM, Gregor Zurowski <gre...@list.zurowski.org> wrote: > Hi, > > Unfortunately I was not able to cut the release due to the following > problems with the Git repository when trying to push changes: > > remote: This repository has been locked due to synchronization issues: > remote: - /x1/gitbox/broken/camel.txt exists due to a previous error, > and prevents pushes. > remote: This could either be a benign issue, or the repositories could > be out of sync. > remote: Please contact us...@infra.apache.org to have infrastructure > resolve the issue. > remote: > To https://gitbox.apache.org/repos/asf/camel.git > ! [remote rejected] release/2.21.2 -> release/2.21.2 (pre-receive > hook declined) > error: failed to push some refs to > 'https://gitbox.apache.org/repos/asf/camel.git' > > Did anybody experience this in the past? > > Thanks in advance, > Gregor > > > On Tue, Jul 3, 2018 at 10:48 PM, Gregor Zurowski > <gre...@list.zurowski.org> wrote: >> Sure, I can take care of the release this weekend. >> >> Thanks, >> Gregor >> >> >> On Tue, Jul 3, 2018 at 1:09 PM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> Hi >>> >>> After the Camel 2.22.0 release, then I think we should work on getting >>> a new patch release out of the 2.21.x branch, eg 2.21.2. There are 38 >>> JIRAs fixed for this version and we will get a couple of more which >>> are pending to be backported. >>> >>> >>> >>> -- >>> Claus Ibsen >>> ----------------- >>> http://davsclaus.com @davsclaus >>> Camel in Action 2: https://www.manning.com/ibsen2 -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
