From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by sourceware.org (Postfix) with ESMTPS id 988833858C53 for ; Fri, 5 Aug 2022 13:05:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 988833858C53 Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-56-kTthpMcAPuiJQ3wwpNdXSQ-1; Fri, 05 Aug 2022 09:05:50 -0400 X-MC-Unique: kTthpMcAPuiJQ3wwpNdXSQ-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id E2233801755 for ; Fri, 5 Aug 2022 13:05:49 +0000 (UTC) Received: from comet.redhat.com (unknown [10.39.194.34]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 877142166B26 for ; Fri, 5 Aug 2022 13:05:49 +0000 (UTC) From: Nick Clifton To: binutils@sourceware.org Subject: 2.39 branch is open for business Date: Fri, 05 Aug 2022 14:05:48 +0100 Message-ID: <87o7wysuvn.fsf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.78 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_NONE, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: binutils@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Binutils mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Aug 2022 13:05:52 -0000 Hi Guys, The 2.39 release is out, and so the 2.39 branch is open again for check-ins as normal. Although in general I would suggest not adding new features to the 2.39 branch as they are unlikely to be seen unless there is a need to make a 2.39.1 release. Ideally the next release (2.40) will happen at the end of January next year... Cheers Nick