Hey Chris,
Here are the results of just running the upgrade system tests on the
latest 3.3 branch:
http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1671061000--apache--3.3--69fbaf2457/2022-12-14--001./2022-12-14--001./report.htm
Hi José,
Thanks for your help! I was able to locally rerun two of the three failed
tests and get passing results; the reports for them can be found at:
https://home.apache.org/~cegerton/system_tests/2022-12-14--015/report.html
(Connect REST test)
https://home.apache.org/~cegerton/system_tests/202
Hey all,
Here are the system test results for the 3.3 branch:
http://confluent-kafka-branch-builder-system-test-results.s3-us-west-2.amazonaws.com/system-test-kafka-branch-builder--1670984851--apache--3.3--22af3f29ce/2022-12-13--001./2022-12-13--001./report.html
The commit for that run is 22af3f2
Thanks Chris!
I started a build for the system tests against the 3.3 branch using
Confluent's infrastructure. I'll reply here when the results are
avaialbe.
--
-José
Hi all (especially committers/PMC who have served as release manager
before),
I've created the first release candidate for 3.3.2 (
https://github.com/apache/kafka/tree/3.3.2-rc0) and am almost ready to
start a vote on it, but I haven't run system tests for it yet. I've tried
to kick off a run on m
Hi Ron,
You're in luck, I was just about to start generating a release candidate!
I'm fine with including the fix for KAFKA-14392 in 3.3.2.
Cheers,
Chris
On Mon, Dec 12, 2022 at 3:13 PM Ron Dagostino wrote:
> Hi Chris.
> https://eu01.z.antigena.com/l/dqC_AcOJullnCjJyPkdUEcH~mlZJ_G4H3YPEhXpPTM
Hi Chris. https://github.com/apache/kafka/pull/12856 "KAFKA-14392:
KRaft broker heartbeat timeout should not exceed
broker.session.timeout.ms" just merged to trunk and seems like a
reasonable candidate for 3.3.2. Can it be included?
Ron
On Fri, Nov 18, 2022 at 10:57 AM Chris Egerton wrote:
>
>
Hi all,
Here is the release plan for 3.3.2:
https://cwiki.apache.org/confluence/display/KAFKA/Release+plan+3.3.2
Currently there is one open blocker issue and one open non-blocker,
non-critical issue. I plan to generate the first release candidate once the
blocker issue is resolved, unless other
Thanks for volunteering!
+1
Best,
Bruno
On 17.11.22 09:57, Luke Chen wrote:
Thanks for volunteering!
On Thu, Nov 17, 2022 at 1:07 AM José Armando García Sancio
wrote:
+1. Thanks for volunteering.
--
-José
Thanks for volunteering!
On Thu, Nov 17, 2022 at 1:07 AM José Armando García Sancio
wrote:
> +1. Thanks for volunteering.
>
> --
> -José
>
+1. Thanks for volunteering.
--
-José
Thanks for volunteering for the release!
+1
-Bill
On Wed, Nov 16, 2022 at 10:58 AM David Jacot
wrote:
> +1. Thanks for volunteering!
>
> On Wed, Nov 16, 2022 at 4:09 PM Chris Egerton
> wrote:
> >
> > Hi all,
> >
> > I'd like to volunteer to be the release manager for the next bugfix
> > releas
+1. Thanks for volunteering!
On Wed, Nov 16, 2022 at 4:09 PM Chris Egerton wrote:
>
> Hi all,
>
> I'd like to volunteer to be the release manager for the next bugfix
> release, 3.3.2.
>
> If there are no objections, I'll send out a release plan by EOD (Eastern
> Time) Friday that includes a list
Hi all,
I'd like to volunteer to be the release manager for the next bugfix
release, 3.3.2.
If there are no objections, I'll send out a release plan by EOD (Eastern
Time) Friday that includes a list of all of the fixes we are targeting
along with a timeline.
Cheers,
Chris
14 matches
Mail list logo
