From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23074 invoked by alias); 2 Jul 2018 15:22:24 -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 23061 invoked by uid 89); 2 Jul 2018 15:22:23 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.0 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS,URIBL_RED autolearn=ham version=3.3.2 spammy= X-HELO: relay1.mentorg.com Date: Mon, 02 Jul 2018 15:22:00 -0000 From: Joseph Myers To: "Maciej W. Rozycki" CC: Carlos O'Donell , GNU C Library , Tulio Magno Quites Machado Filho , Bill Schmidt Subject: Re: glibc 2.28 release on August 1st and extended ABI freeze for ppc64le float128. In-Reply-To: Message-ID: References: <4db8730d-158c-67e4-b4fd-55b3cc9a7100@redhat.com> User-Agent: Alpine 2.20 (DEB 67 2015-01-07) MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-SW-Source: 2018-07/txt/msg00028.txt.bz2 On Mon, 2 Jul 2018, Maciej W. Rozycki wrote: > Shall I file a separate BZ just for this patch, with the milestone set > to 2.28? Milestones should only be set on FIXED bugs; they aren't how we plan for what we want in what release. See point M1 at . -- Joseph S. Myers joseph@codesourcery.com