From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id DE6AAECAA27 for ; Thu, 25 Aug 2022 18:48:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243309AbiHYSsw (ORCPT ); Thu, 25 Aug 2022 14:48:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47484 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243473AbiHYSsq (ORCPT ); Thu, 25 Aug 2022 14:48:46 -0400 Received: from ms.lwn.net (ms.lwn.net [45.79.88.28]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 76422B56F2; Thu, 25 Aug 2022 11:48:41 -0700 (PDT) Received: from localhost (unknown [IPv6:2601:281:8300:73::5f6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ms.lwn.net (Postfix) with ESMTPSA id 6F19031A; Thu, 25 Aug 2022 18:48:40 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 ms.lwn.net 6F19031A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lwn.net; s=20201203; t=1661453320; bh=GKo/HAiBH1pXBkoB5hyeNe5OnaTVwZXlZaRMSpQF2cw=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=TcsXQfqYBT0COO2IbL78QjtCZUDRmFCGfh3DDIdkW584XixMW+lQnzwj+D/kIJXi0 RMlCYwBI1K2ZhF7sFELlJ2CUs7wWuzHJpPX6JIIAtoDJJTl1c/JKAWycxWJiP+5V0e HMxhlCs+2AePO9I/9B0s6tKh3THSK3iOIO0jeEc8ilHkg1sTEydvdjvqaIZuRGwSJn spZLldruA8nOuQK+Y1nJuhKRpSYnjNXlsKExuB0drOrLLKSEuWO1SrsGn8iNo3ukaG ihIvde59tEbzJ5Rk7r4tCQw1iOQGoVul/+g8klzOhnGz+CeonrL/aDhpdVtBYIcfDR cJxA6dvzLutLQ== From: Jonathan Corbet To: Lukas Bulwahn , linux-doc@vger.kernel.org Cc: linux-kernel@vger.kernel.org, Lukas Bulwahn Subject: Re: [PATCH] docs: Update version number from 5.x to 6.x in README.rst In-Reply-To: <20220824080836.23087-1-lukas.bulwahn@gmail.com> References: <20220824080836.23087-1-lukas.bulwahn@gmail.com> Date: Thu, 25 Aug 2022 12:48:39 -0600 Message-ID: <87a67syxa0.fsf@meer.lwn.net> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-doc@vger.kernel.org Lukas Bulwahn writes: > A quick 'grep "5\.x" . -R' on Documentation shows that README.rst, > 2.Process.rst and applying-patches.rst all mention the version number "5.x" > for kernel releases. > > As the next release will be version 6.0, updating the version number to 6.x > in README.rst seems reasonable. > > The description in 2.Process.rst is just a description of recent kernel > releases, it was last updated in the beginning of 2020, and can be > revisited at any time on a regular basis, independent of changing the > version number from 5 to 6. So, there is no need to update this document > now when transitioning from 5.x to 6.x numbering. > > The document applying-patches.rst is probably obsolete for most users > anyway, a reader will sufficiently well understand the steps, even it > mentions version 5 rather than version 6. So, do not update that to a > version 6.x numbering scheme. > > Update version number from 5.x to 6.x in README.rst only. I've gone ahead and applied this. For the other files: - I don't think 2.Process.rst needs any immediate attention. We could change the wording from "recent release history" to "The release history in early 2022 looked like:" or something like that. There is no reason why it has to be the latest releases. - applying-patches.rst should just go. I didn't prevail last time I tried to make that point, but I still don't think that we help anybody by dragging 1990's instructions around now. Thanks, jon