Path: csiph.com!newsfeed.xs4all.nl!newsfeed8.news.xs4all.nl!bofh.it!news.nic.it!robomod From: Andrius Merkys Newsgroups: linux.debian.maint.java Subject: antlr 4.10 released [Was: Re: packaging Go runtime for ANTLR4] Date: Wed, 13 Apr 2022 10:40:01 +0200 Message-ID: References: X-Mailbox-Line: From debian-java-request@lists.debian.org Wed Apr 13 08:37:10 2022 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.511 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, LDO_WHITELIST=-5, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -5.5 X-Gm-Message-State: AOAM533MJoksPa7JJWt94SbWUZsd6VvFTjC2IOBk8zjcc4SmKyqG5CUH N71q/q8lnAXGz1WX7IHu1Rzuf0ghpFM= X-Google-SMTP-Source: ABdhPJyk+GYUqhPa8LohoPbuShxSS7T1i8LfHukeoZ5oCtwXipWDkfMQ3nGifo+JtZ6fukldxWblow== X-Received: by 2002:a2e:a7c6:0:b0:24b:6615:ac9f with SMTP id x6-20020a2ea7c6000000b0024b6615ac9fmr7601130ljp.221.1649839014501; Wed, 13 Apr 2022 01:36:54 -0700 (PDT) MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Mailing-List: archive/latest/23010 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/98ce75cb-855d-21ec-a6a1-ead643bc9f5a@debian.org Approved: robomod@news.nic.it Lines: 19 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 13 Apr 2022 11:36:53 +0300 X-Original-Message-ID: <98ce75cb-855d-21ec-a6a1-ead643bc9f5a@debian.org> X-Original-References: Xref: csiph.com linux.debian.maint.java:12372 Hello, Some time ago there was a discussion about the need to coordinate uploads of antlr and its runtime packages, as in Debian they are split into several source packages across several teams: On 2021-07-29 10:09, Andrius Merkys wrote: > Maybe an antlr4 packaging team could be set up to coordinate > synchronized version bumps? antlr 4.10 has just been released. How should we proceed with packaging? What are the constrains? I maintain antlr4-cpp-runtime. I plan to upload updated package to experimental (needs to clear NEW) and wait for antlr 4.10 to appear in unstable. Best, Andrius