g 2 things:
>> > >
>> > > 1. When commiting the work on a task, making sure that every commit is
>> > > compilable. For instance, in the pattern above, by squashing
>> > > commit1+commit2, commit3+4, etc.
>> > > 2. When merging community contributions wit
done on the same
> day
> > because the Camel branches are modified very frequently and each change
> can
> > potentially be in conflicts with yours.
> > >
> > > it is a quite cumbersome approach but I don't see any safer way.
> > >
> > > Regards,
>
; > On Thu, Jun 22, 2023 at 8:08 AM Petr Kuzel .invalid>
> > wrote:
> >
> >> Hi Otavio,
> >>
> >> the codebase does not have the release quality
> >> after each commit. Test-driven development could
> >> even invite devs to separately c
oach but I don't see any safer way.
Regards,
Nicolas
From: Otavio Rodolfo Piske
Sent: Thursday, June 22, 2023 08:53
To: dev@camel.apache.org
Subject: Re: Some thoughts on bisecting Camel and our git commit practices
Hi,
Release-tagged commits don't
y, June 22, 2023 08:53
To: dev@camel.apache.org
Subject: Re: Some thoughts on bisecting Camel and our git commit practices
Hi,
Release-tagged commits don't help here. The whole point of bisecting is
finding out precisely which commit introduced a certain behavior or bug, so
that I and
> Mr. Petr Kužel, Software Engineer
> Eurofins International Support Services s.à r.l.
> Val Fleuri 23
> L-1526 LUXEMBOURG
>
> -Original Message-----
> From: Otavio Rodolfo Piske
> Sent: Wednesday, June 21, 2023 11:17
> To: dev
> Subject: Some thoughts on bis
bisecting Camel and our git commit practices
Folks,
You may have seen that PRs constantly report failures when testing changes
on core. This is almost always caused by flaky tests.
I have been trying to find the root causes of those flaky tests. Quite
often this involves going all the way to early
Folks,
You may have seen that PRs constantly report failures when testing changes
on core. This is almost always caused by flaky tests.
I have been trying to find the root causes of those flaky tests. Quite
often this involves going all the way to early versions of Camel 3 to find
stable executio
