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 X-Spam-Level: X-Spam-Status: No, score=-4.5 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A433FC433DB for ; Thu, 7 Jan 2021 15:45:39 +0000 (UTC) Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 3A7B023406 for ; Thu, 7 Jan 2021 15:45:39 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 3A7B023406 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=xen-devel-bounces@lists.xenproject.org Received: from list by lists.xenproject.org with outflank-mailman.62956.111709 (Exim 4.92) (envelope-from ) id 1kxXTO-0004n3-5c; Thu, 07 Jan 2021 15:45:14 +0000 X-Outflank-Mailman: Message body and most headers restored to incoming version Received: by outflank-mailman (output) from mailman id 62956.111709; Thu, 07 Jan 2021 15:45:14 +0000 Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kxXTO-0004mw-2V; Thu, 07 Jan 2021 15:45:14 +0000 Received: by outflank-mailman (input) for mailman id 62956; Thu, 07 Jan 2021 15:45:12 +0000 Received: from us1-rack-iad1.inumbo.com ([172.99.69.81]) by lists.xenproject.org with esmtp (Exim 4.92) (envelope-from ) id 1kxXTM-0004mr-NT for xen-devel@lists.xenproject.org; Thu, 07 Jan 2021 15:45:12 +0000 Received: from mail-lf1-x12a.google.com (unknown [2a00:1450:4864:20::12a]) by us1-rack-iad1.inumbo.com (Halon) with ESMTPS id 4a42fa11-f76b-46af-9552-8e5e470f8053; Thu, 07 Jan 2021 15:45:11 +0000 (UTC) Received: by mail-lf1-x12a.google.com with SMTP id l11so15687248lfg.0 for ; Thu, 07 Jan 2021 07:45:11 -0800 (PST) Received: from [192.168.1.7] ([212.22.223.21]) by smtp.gmail.com with ESMTPSA id t3sm1217401lfe.263.2021.01.07.07.45.09 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 07 Jan 2021 07:45:09 -0800 (PST) X-BeenThere: xen-devel@lists.xenproject.org List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xenproject.org Precedence: list Sender: "Xen-devel" X-Inumbo-ID: 4a42fa11-f76b-46af-9552-8e5e470f8053 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=OnS5rTIyKAoe/Q+H/eVLqBUtownc6+MH3ifL+Uvmbh0=; b=Hw/Rmo4bl9/GTizBwVGJ4zl8ZM7ky3eNI5Tt9PNJLGEzhXEwfLsprIR14RY2hW6XTL Wpfdbh6JeszAc7wi6q1gqUEonyRNAB8j7xa+6/JVQpulyqWANpVmxiuPGUwj8dtcY0m+ rqBS4HRraB/XMDucEMBWavVc0j8HlDNWcX78TezmfxHj7a8OwPTjRR+A+4ROwiQJm/b2 PWN+b6U6nWFwqp4hsJcnv3OW22eJuJ7osvWb9SuGaq8qmG9sEW2bIqh2bIV7RoO4bF+9 w6FA7H3cL4xCy1NkJDNVvh09kq6pNWSIdEFl2lZ0xPnuOI+VKB9uSblcTlY8P5yWVmRm F2/w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=OnS5rTIyKAoe/Q+H/eVLqBUtownc6+MH3ifL+Uvmbh0=; b=NG0Ls373mJPUks1siFDcmMxTN7oSEZvVomEBVFAoOXgVNQRoqjE8mHaBftoTLuFbVN ZuI2nUNEYeWQXC5bf8sTPcECEq40HTTPXm6zkOLu/L/ukWk4PpCZXRZ0o3Q21S0/j+Z3 ClipCctJ/NLYV98LQ8OmrOI7JtrWiFcF+snM+vmEETTIoxJLzxAhftvpR1vEoDZME3oV 57ZEQYDMTTNAWxQdPgzeCpYSGlfylNUWJ65PG2fruZWZ9XdNp4h4PfpdC7IxGzQRdP8+ ua1xLgyoEoEwvG0+kGLYEu9pw64kGCPgQZMA1uxcI3i4hnErWDRMZKkFIXw/GA3BVV0Y Y8bA== X-Gm-Message-State: AOAM532ducf5vZfVr5p2c+oHHhtk0qEzgeahB2/YIDPfRStw0UEZf3QX HrsAUQf+1jjGRH35vFRPxKPf0TVwkoc= X-Google-Smtp-Source: ABdhPJw+xR/HWSfJ1h/WY2o5ZCDmJwFZ/kron8pssoF8T84/eUYlbp27gpfv/WL0V50pHshkTDyhcQ== X-Received: by 2002:a2e:2f16:: with SMTP id v22mr4263707ljv.198.1610034310109; Thu, 07 Jan 2021 07:45:10 -0800 (PST) Subject: Re: [ANNOUNCE] Xen 4.15 release schedule and feature tracking To: Ian Jackson Cc: xen-devel@lists.xenproject.org, committers@xenproject.org References: <24567.7198.846779.557032@mariner.uk.xensource.com> From: Oleksandr Message-ID: <6f5a592f-10a5-059b-7d63-bf86764e3fbb@gmail.com> Date: Thu, 7 Jan 2021 17:45:03 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <24567.7198.846779.557032@mariner.uk.xensource.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US On 07.01.21 16:35, Ian Jackson wrote: Hi Ian > Hi. As the Release Manage for Xen 4.15 I am going to start tracking > the status of features which people are looking to get into Xen 4.15. > > NB that the Last Posting Date is just over a week from now. > > If you are working on a feature you want in 4.15 please let me know > about it. I work on virtio-mmio on Arm which involves x86's IOREQ/DM features. Currently I am working on making the said features common, implementing missing bits, code cleanup an hardening, etc. I don't think the virtio-mmio is a 4.15 material, but it would be great have at least "common" IOREQ/DM in 4.15. > Ideally I'd like a little stanza like this: > > S: feature name The corresponding thread named: IOREQ feature (+ virtio-mmio) on Arm https://www.mail-archive.com/xen-devel@lists.xenproject.org/msg87002.html > O: feature owner (proponent) name > E: feature owner (proponent) email address Julien as initiator of this activity, me as a person who continues this activity and tries to get it upstreamed: Julien Grall Oleksandr Tyshchenko > P: your current estimate of the probability it making 4.15, as a %age Difficult to say, it depends ... RFC was posted Aug 3, 2020, The last posted version is V3. Currently I am in the middle of preparing v4, still need to find a common ground for few bits. > > But free-form text is OK too. Please reply to this mail. > > NB the primary responsibility for driving a feature's progress to meet > the release schedule, lies with the feature's proponent(s). > > As a reminder, here is the release schedule: > > Friday 15th January Last posting date > > Patches adding new features should be posted to the mailing list > by this cate, although perhaps not in their final version. > > Friday 29th January Feature freeze > > Patches adding new features should be committed by this date. > Straightforward bugfixes may continue to be accepted by > maintainers. > > Friday 12th February **tentatve** Code freeze > > Bugfixes only, all changes to be approved by the Release Manager. > > Week of 12th March **tentative** Release > (probably Tuesday or Wednesday) > > Any patches containing substantial refactoring are to treated as > new features, even if they intent is to fix bugs. > > Freeze exceptions will not be routine, but may be granted in > exceptional cases for small changes on the basis of risk assessment. > Large series will not get exceptions. Contributors *must not* rely on > getting, or expect, a freeze exception. > > The codefreeze and release dates are very much provisional and will be > adjusted in the light of apparent code quality etc. > > If as a feature proponent you feel your feature is at risk and there > is something the Xen Project could do to help, please consult me or > the Community Manager. In such situations please reach out earlier > rather than later. > > Ian. > -- Regards, Oleksandr Tyshchenko