Thanks for reaching out Russell!

I was not aware of this (new?) policy. I did open a PR to update the links accordingly: https://github.com/apache/kafka-site/pull/655

It would be great if you could take a look and help us to get this right.

I was not sure if the release notes should stay at `downloads.apache.org` (like checksum and KEYS file), or if we also need to update them to `dlcdn.apache.org`?


Thanks a lot,
  -Matthias


On 12/14/24 4:20 PM, Craig Russell wrote:
Dear Kafka PMC,

Thanks for taking care to follow ASF policy for your download pages.
https://www.apache.org/legal/release-policy.html#release-announcements

Your download page needs to be corrected. The artifact download links must not 
use downloads.apache.org but must use either a closer.lua script or 
dlcdn.apache.org.

Warm regards,
Craig

On Dec 13, 2024, at 15:16, Matthias J. Sax <mj...@apache.org> wrote:

The Apache Kafka community is pleased to announce the release for Apache Kafka 
3.7.2

This is a bug-fix release, closing 21 Jira tickets.

All of the changes in this release can be found in the release notes:
https://www.apache.org/dist/kafka/3.7.2/RELEASE_NOTES.html

You can download the source and binary release (Scala 2.12 and 2.13) from:
https://kafka.apache.org/downloads#3.7.2

---------------------------------------------------------------------------------------------------


Apache Kafka is a distributed streaming platform with four core APIs:


** The Producer API allows an application to publish a stream of records to one 
or more Kafka topics.

** The Consumer API allows an application to subscribe to one or more topics 
and process the stream of records produced to them.

** The Streams API allows an application to act as a stream processor, 
consuming an input stream from one or more topics and producing an output 
stream to one or more output topics, effectively transforming the input streams 
to output streams.

** The Connector API allows building and running reusable producers or 
consumers that connect Kafka topics to existing applications or data systems. 
For example, a connector to a relational database might capture every change to 
a table.


With these APIs, Kafka can be used for two broad classes of application:

** Building real-time streaming data pipelines that reliably get data between 
systems or applications.

** Building real-time streaming applications that transform or react to the 
streams of data.


Apache Kafka is in use at large and small companies worldwide, including 
Capital One, Goldman Sachs, ING, LinkedIn, Netflix, Pinterest, Rabobank, 
Target, The New York Times, Uber, Yelp, and Zalando, among others.

A big thank you for the following 31 contributors to this release! (Please 
report an unintended omission)

Andrew Schofield, Apoorv Mittal, Bill Bejeck, Chia-Ping Tsai, Chris Egerton, 
Christo Lolov, Colin P. McCabe, Colin Patrick McCabe, David Arthur, Divij 
Vaidya, Dmitry Werner, Gaurav Narula, Greg Harris, Igor Soarez, Josep Prat, Ken 
Huang, Kirk True, Kondrat Bertalan, Kuan-Po Tseng, Laxman Ch, Lianet Magrans, 
Luke Chen, Manikumar Reddy, Matthias J. Sax, Mickael Maison, Omnia Ibrahim, 
PoAn Yang, Rohan, TengYao Chi, Vedarth Sharma, Vikas Singh

We welcome your help and feedback. For more information on how to report 
problems, and to get involved, visit the project website at 
https://kafka.apache.org/

Thank you!


Regards,
  -Matthias J. Sax

Release Manager for Apache Kafka 3.7.2



Craig L Russell
c...@apache.org


Reply via email to