You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@avro.apache.org by "Ismaël Mejía (Jira)" <ji...@apache.org> on 2026/08/14 13:14:00 UTC

[jira] [Assigned] (AVRO-4333) Automate Avro release

     [ https://issues.apache.org/jira/browse/AVRO-4333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ismaël Mejía reassigned AVRO-4333:
----------------------------------


> Automate Avro release
> ---------------------
>
>                 Key: AVRO-4333
>                 URL: https://issues.apache.org/jira/browse/AVRO-4333
>             Project: Apache Avro
>          Issue Type: Improvement
>          Components: build
>            Reporter: Ismaël Mejía
>            Assignee: Ismaël Mejía
>            Priority: Major
>
> The release of a new version of Avro is a manual process that requires lots of attention to not make mistakes. It odes not help the multiple languages and tools involved.
> We must automate as many steps as possible to get to the point that making a release is an easy and 'trivial' process as it should be.
> Other projects are following these type of practices and we can definitely learn from them, the 3-step process (Prepare RC, Cancel RC, Publish) from Parquet seems like a good candidate
> [https://github.com/apache/parquet-java/pull/3548]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)