From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIMWL_WL_MED,DKIM_SIGNED, DKIM_VALID,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id b94ff769 for ; Fri, 4 Jan 2019 00:40:49 +0000 (UTC) Received: (qmail 12394 invoked by alias); 4 Jan 2019 00:40:34 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 43971 Received: (qmail 7070 invoked by uid 1010); 4 Jan 2019 00:40:34 -0000 X-Qmail-Scanner-Diagnostics: from mail-lf1-f44.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.100.2/25112. spamassassin: 3.4.2. Clear:RC:0(209.85.167.44):SA:0(-1.9/5.0):. Processed in 3.874286 secs); 04 Jan 2019 00:40:34 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vZLjBoIyRbSO1/fjYLuNGZ5ufWup3Fu/If+p2wciFo4=; b=JS/qaC5RG9+pR9+dd+1Ty5NOu/oHUxXTWDNPl32dafsd1fQxGkzMx59mJnkvRkK49S lQsk8rQWPe4uLu27xi6f2a0BoTQTmjnMdV2Z4m1URFuNTPuSBFFTFWESwNaOyvRuQNzb 9BMV0L/xZ0p2hVNBTANbNJKAQgAjk/aCyxkADeWFDvf+cYOynd1hHwUVGtiO1bi1e2Fc y678lWRK/qeT28Bz1UP0qTrD3l72xrFKgpmNZW+UeeG6LY4N6Kx5Tbli7+4HKicK6s0a Zk8vhIXnx9jqkD7CpeRp+8inj1k81rayWsg9iOdDQS32mvt2HSe4y53Tkl6j6GAW6aEQ sSHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=vZLjBoIyRbSO1/fjYLuNGZ5ufWup3Fu/If+p2wciFo4=; b=AJANdbeoXX9AKMRYHw0EfOdWCTxdO3DpE/mYvv6TNsYQiibSAiThxNauKi4Zh5WXCh OJK4lS7xzerdkyr+phxyifuEwnkoJf/ujpdpzRnJfdSZ/e8vty1EeLNxJBPgcjhEkHD3 eUhqiw0YMQTeixPZMH8qCNrpYxNH1ir/vECGR5CP63sUVme51gUoe1HCh0gLOoDgj6Sh rZWvyIg4X+NOmUfHranG5j0qYVjKhPSGP8hul2es8vZzV9rhJPbvMcu/YlaTYjq1VXx1 2b5jkfoJbUt1ugnoK4QeSG7/bnW9tanA5x/62wNM0kVmCQHJhPYoB3/QRZgNZM3iao4h ZDdQ== X-Gm-Message-State: AA+aEWZ+nwBcutQVlxgvDL0ulYWspeAyYe57HGg0xXpfzPlczr1l7ZOI 8xVjtSF0DQPVHlxpKmQnRJPVqhVqPridp29Z28SYvA== X-Google-Smtp-Source: AFSGD/XXpTRcj6X9u10MyKsv6AKzaJbCLu+EJpyXw6R5Xr39NXuZz04TDH2PodQdgu69IFjKFBocHKwxxmEnm2rzBPg= X-Received: by 2002:a19:d9d6:: with SMTP id s83mr26051760lfi.57.1546562424723; Thu, 03 Jan 2019 16:40:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Bart Schaefer Date: Thu, 3 Jan 2019 16:40:13 -0800 Message-ID: Subject: Re: [PATCH/RFC] Document some 5.{4,5,6} features in NEWS To: dana Cc: Zsh workers Content-Type: text/plain; charset="UTF-8" On Thu, Jan 3, 2019 at 10:48 AM dana wrote: > > I was going through the steps for creating a test release and noticed that > some new features in recent releases weren't mentioned in NEWS. I just wanted > to double-check whether there's any strong feeling regarding what's notable > enough for inclusion here. Is this fine, or is it more granular than intended? I would say this is about the right level of detail regarding each change. I have no opinion on whether everything mentioned here is signficant enough to have been mentioned. Your suggestion for updating creating-a-release.txt seems reasonable. As long as you're committing this, how about fixing this typo: > Apart from a fix for a configuration problem finding singal names from