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.129.124]) by sourceware.org (Postfix) with ESMTPS id 779CF385E004 for ; Wed, 14 Feb 2024 13:29:53 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 779CF385E004 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 779CF385E004 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1707917395; cv=none; b=gseOnp+g4fpta5gmUU837FzUf3jy/mrD8WM5ejrIm+hB54mpRngOiahe9w2g0mrBJ6t/K0xhMp9RrXt8CyA9gKVC2WKIuBTIfLCy2jkiVVoXjDfrTnwY2Xq/aMQ5w7IrSbbJ1o4gddwglMd0SdmlPsdKlvG/RS2Hn5ZvSHhfbaI= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1707917395; c=relaxed/simple; bh=aGCenMNpLUARS9ykxpFkp0DYpEjqp6r+rR5F5gLtMRY=; h=DKIM-Signature:Message-ID:Date:MIME-Version:From:Subject:To; b=wyIoQPFPqthBOMligY0CG+bSSr4HeNGwPvPNXs87firbSKKorZgjD3tE2UMqJl5EKXcnX5S2QCFmVCqzUqFDN35sTnLXn6QbX9+7NWGRNbT1tHkbNVfKLjgMbL38r6jl5gWJq85oHmRKKrfkDrLztbMcfsYuK6cLmTvVxBJcYso= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1707917393; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=2PXSR9JgGtc51ViKSdy3zbue7UQs8e7jF4Z2he80asM=; b=Fubpx3zeAyVofdrQidkOpHMs1ZUlF91NVn4JwwzIikEYPHaWv4zFfYspEM6SjbGJnw7fAg STzNBv3Ftmvu9dDMgSvxo+0pUoU6BdoT3VMYchOALoqrKFla2psmKM+T2HCu7FxLsfcbpW ibAL7rHBgy6xMR4BlSD0gD/VRM8mH28= Received: from mail-ua1-f71.google.com (mail-ua1-f71.google.com [209.85.222.71]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-21-N-9G1lVeMduBYW0ydxfOPA-1; Wed, 14 Feb 2024 08:29:51 -0500 X-MC-Unique: N-9G1lVeMduBYW0ydxfOPA-1 Received: by mail-ua1-f71.google.com with SMTP id a1e0cc1a2514c-7d48198d021so2366399241.1 for ; Wed, 14 Feb 2024 05:29:51 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1707917389; x=1708522189; h=content-transfer-encoding:organization:content-language:to:subject :from:user-agent:mime-version:date:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=2PXSR9JgGtc51ViKSdy3zbue7UQs8e7jF4Z2he80asM=; b=D4Zp4SNtDxZWCZEcClUzVgOWOlllEu9hU6Y/jbT5VxVUSJ1RWbRVM8GGC/9PLu/KDa 53h7ptFzEdmvlPfYm3Cak3oaThKV1FuR29mFUqILR9OgWA2oka6FbauXVgrdyewVQvll UeBid/wBMBqgtSctb8+rKi4TJcJLcvaZexgenHK2k5fJ49iYbrV4wK0mT6NJwsXw1UJ5 v7WhiysgPmRa/J8V04nKYdx5IlitWR9L7ygiyz6Ter9rZdpc6PSEet3ScYuRjzhUuree /b7Ac8X+c0SpMCXyOSfjdkGenX2nLBpSgOHy6vE8zsQi9FiPB2WgLHj/SaMZgWiZh3QM PYiA== X-Gm-Message-State: AOJu0YwJXOksIVpP+S/pPbkXJy1YUNeuNbfLQwn1ICl1B8sJ4G1YgGMk FTnysSphxWjhraZymkldpFk6Z09RWxizR5yyhDw67j7yi6Lp5HgFXBxLVAPA2mYjNg2HEd+uTyO 8eEtKO3gGuEEfq7tiQO+Lb7yOjAi/fOSgRtNJzERN3VKTS4meS9ugmdslegTVieA4JNtqEytl3m oa3qmOiWlxtGVSOpVwVkS/WifpeqmxsMHr82cJp+A= X-Received: by 2002:a1f:ddc3:0:b0:4c0:254f:75d5 with SMTP id u186-20020a1fddc3000000b004c0254f75d5mr2521830vkg.10.1707917388774; Wed, 14 Feb 2024 05:29:48 -0800 (PST) X-Google-Smtp-Source: AGHT+IE9AM2LOGXHCuPGEcpi/fFm9g3s5QItCI8JEmneELZqA/lajks6PJ/v5jIYqInmxOCsUWjIZA== X-Received: by 2002:a1f:ddc3:0:b0:4c0:254f:75d5 with SMTP id u186-20020a1fddc3000000b004c0254f75d5mr2521795vkg.10.1707917388338; Wed, 14 Feb 2024 05:29:48 -0800 (PST) X-Forwarded-Encrypted: i=1; AJvYcCW/9k2tr89Gfd42IaLBguTqE0ZDg16qV40eQsB7TwDjnc4Rl1/igcUk84mAaDzQ0AbaOycV/m0uWRsumyWnlIAnnfDPvUDj07kM0nWO9dyaTmHKORn4+Jr1caR9veQ1qAiG2aN68Sm8BIOOrauu6W39cgQPB6/TMYP/+ye6HgV1l6BVhn6bvgnWLbQIat78Z+rjxpLsjm1sAI1m66iTLrsReQaW9X6b1vbmDyzUwEr/UBqrOzMo6KUAhBUPyxQhFp6o22Q5rZQt05IsOtuXeZMXNUirF69BjQ== Received: from [192.168.0.241] ([198.48.244.52]) by smtp.gmail.com with ESMTPSA id ob12-20020a0562142f8c00b0068f0307160bsm427970qvb.63.2024.02.14.05.29.47 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 14 Feb 2024 05:29:47 -0800 (PST) Message-ID: <779bc58e-0b2f-4b6b-9efc-e9655b2f2634@redhat.com> Date: Wed, 14 Feb 2024 08:29:46 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird From: Carlos O'Donell Subject: Planning for glibc releases --- What should go into glibc 2.40? To: libc-alpha , Adhemerval Zanella , Andreas Schwab , "Andreas K. Huettel" , Michael Hudson-Doyle , Simon Chopin , Aurelien Jarno , Florian Weimer Organization: Red Hat X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Language: en-US Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-6.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_MANYTO,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,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 List-Id: Community, In a recent Monday Patch Queue review meeting a suggestion was raised by Adhemerval to try doing more detailed plans for the glibc releases. The benefits of a detailed plan for a 6-month development cycle would be that it allows reviewers to support patch review for the committed plan. We do something similar as we approach the end of the development cycle by recording blockers in the release wiki and then reviewing and making progress on the blockers. The goal would be to do something similar but on a monthly cadence. For example: Month 1 - Feature 1 Month 2 - Fix 2 Month 3 - Enhancement 3 Month 4 - Hardware Enablement 4 Month 5 - Feature 5 Month 6 - Blockers We already had a "Planning" section in the release template page so I'm suggesting we reuse that section and plan against the months: https://sourceware.org/glibc/wiki/Release/2.40#Planning I have added 2 things I'd like to see this release and put them against February and April. My goal is to commit to these two items and support getting them completed in that month. If they aren't complete then we can re-evaluate. Development should proceed as normal but during patch queue review I will give priority to the items in the plan and seek reviewers for those items to attempt to complete the review (similar to how we handle blockers in Month 6). I don't want to define a complex process here. If there is something that you would like to see happen then add it to the plan and if a given month gets too busy then we'll discuss it as a community. Please add items to the plan :-) Thoughts? I'm particularly keen to hear if the distributions have any features, fixes, or enhancements they want to see completed. -- Cheers, Carlos.