From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 94359 invoked by alias); 3 Jul 2017 07:28:28 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 44745 invoked by uid 89); 3 Jul 2017 07:27:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=held X-HELO: homiemail-a52.g.dreamhost.com To: "libc-alpha@sourceware.org" From: Siddhesh Poyarekar Subject: glibc 2.26 freeze is ON Message-ID: Date: Mon, 03 Jul 2017 07:28:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-07/txt/msg00018.txt.bz2 Hi, Please note that as of right now, the 2.26 freeze is on. If your patches are already approved then please push them as soon as you can so that they're available to architecture maintainers for testing. If they're not reviewed or approved, they need to be held back until 2.26 is released unless it is a bug fix or is one of the release blockers[1]. If you have a patchset that should be in 2.26, please propose it as a release blocker[1]. Siddhesh [1] https://sourceware.org/glibc/wiki/Release/2.26