[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] RFC: Version support policy


  • To: Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxx>
  • Date: Wed, 23 Feb 2022 13:20:26 +0000
  • Accept-language: en-US
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=YaA0pvouXxcedgS0dwikwDh+3s3XQh7JbYVRgKIjLFE=; b=H+j73V/UIc18gZW1BklmLcEzffuNXisHvw0c4GsKgmKUOPOV8zRd5k8hCX6hd227QGMtdkqltZ7jTi9uhvd0eIKVEFVfCyldKWFPU/Z0tYDTu9Iddx79OvKhhxaiHa2lz6yLGpDpHj2YvhowM1H4laaT1hxz56Wvzv7Ey+vzQT5QQ+BIyrOmrRwinqBXPSLuRpJ8cO/waZPDVSI5zwT9uALgh5KEk7WJoQxpzlPHPefB9kmBJGW7kL3I6lkzlFr9LuZ0yTDKY++5j0Wvm3exg1iMPezfxmHz4qw8cno1fWkEHAZeB1xBsqEd6mZTk3GkE8TxvgOLKloQI+anixnWFQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=It9xbV0zvEBNBAocYozZ0r12hVOuj+dMe5Zn2XTLFJomH2Cogmd+wk5FGg2opC58Eckbtb4/t1kBp/wHCGZ0PGpvRX7BhsNTZPYJPV9+OXvPnLoyKUEXn1Ntvmd2p+KV4XX4bJU7/ndSkzN6IMGOAgqDCKTglu1RV4hc/xvtWHVYuMAK+WwAdl2c8K7Gz+aUxUjaZRtnXUZdA83NdnXfKg2tF5hj6fg07ydcq8jaUCds5tltsHZEskPT1o38+HWu532DBi7C5IXrw0XVCks92Pt7DHZl07SrNVYyZjf0eb1H1iF2igVzIqvwOXzMLriN94ece2dzsQ1CDHZa2lgj7g==
  • Authentication-results: esa6.hc3370-68.iphmx.com; dkim=hardfail (body hash did not verify [final]) header.i=@citrix.onmicrosoft.com
  • Cc: Jan Beulich <jbeulich@xxxxxxxx>, Ian Jackson <iwj@xxxxxxxxxxxxxx>, Committers <committers@xxxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <Andrew.Cooper3@xxxxxxxxxx>, Julien Grall <julien@xxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, Wojtek Porczyk <woju@xxxxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 23 Feb 2022 13:20:45 +0000
  • Ironport-data: A9a23:pdBA56JmW5LMRAodFE+Rz5IlxSXFcZb7ZxGr2PjLsTEM7AuW5UVEl zVBCC3DeKqUMyGmS21FGIS3phgF7JOGnNQwSgBsqSpjHysQ8MCaX4vBdBf6NHjNd5zIHRw5t MhONYaQdcw5RXSMrxmgaea58HIm2PmEF7aU5IIoQsxUbVYMpHAJ1UIz8wJAvrNVvDSZP++sk d35/pDRYgX70mErY25Et/vb8U8+5K2r42oSsw1iNK1A7QPSz3UbMskSdPq7R5farii4PQIYq 8LrluzRErbxpk91Yj+duu+nNBVMGNY+BCDW4pZsc/HKbiNq+2pigs7XCNJGMR0N02/TxIgro DlwncfYpTkBb/WkdNs1C3G0IwkmVUGR0OaaSZQXmZX7I3zuKxMA8d03ZK0FFdRwFtJMKXNP7 ZQlxAUlNXhvsQ4ULIWTEYGAjux7RCXi0Rh2VntIlVk1Bt5+KXzPrjmjCXa1E17ci+gXdcsya fb1ZhI3dDPLZB5rCmtNJ5UuxuLyqnz0eDtH/Qf9SaofuwA/zSR02bnpdtHUZsaLVYNemUPwS mDupjqjREtAbZrGlGTDoinEauznxEsXXKo9Gbqi+fMsrECVwmULIBYXSUG6sb+yjUvWt9d3d RBKq3px/fJaGEqDXNWlYQaei0K94TFMS9VZENYY8C+/4/+Bi+qeLjddFWMQADA8j+ctXiAj3 FKNm9LvBBRsvaeTRHbb8a2bxRuwJCwUIGkqdSICCwwf7LHLv4YxkzrOSMhiC6+/itDpGTD2z CuOpSJ4jLIW5eYU042r8FaBhCijzrDZQwhw6gjJU2aN6gJieJXjd4Gu8ULc7/tLMMCeVFbpl HoOltWa7esOJYqQjyHLS+IIdJms7uyAOSfRgnZuGYcg7DWn/3O/fYFW7yp6LU0vOcEBERfiZ 0rWuB9N6YVIFGuna7dtZIC8ANhsyrLvffzkSfL8ftdIeoJ2dgKM4Gdpf0H44oz2uBFyy+dlY 87dKJvySyZBYUh68Naob78F9rQsxQQO+Tn8QoChyk6L1LGVYmHAHN/pL2CyRuw+6aqFpiDc/ NBeK9aGxn1jbQHuXsXE2dVNdA5XdBDXEbiz8pUKLbDbfmKKDUl8U6e5/F83R2Byc025fM/s9 2r1ZEJXwUGXaZbveVTTMSALhF8CsP9CQZMH0c4EYA7AN5sLO9/HAEIjm30fJ+VPGAtLl6Mcc hX9U5/casmjsxyek9jnUbHzrZZ5aDOgjh+UMiyubVAXJsA8GlGUpIe0JFewpEHi6xZbU+Nk/ 9VMMSuBHPI+q/lKVp6KOJpDMXvr1ZTipA6CdxSReYQCEKkd2INrNzbwnpcKzzIkcn3+Ks+h/ 1/OW38w/LCVy6dsqYWhrf3U/u+BTroldmIHTjaz0FpDHXSDloZV6dQbC7jgkPG0fD6cxZhOk s0PkamnaaVfxAwiXkgVO+8D8J/SLuDH+tdy5g9lAG/KfxKsDLZhKWOBxs5BqutGwboxhOd8c hnnFgVyUVlRBP7YLQ==
  • Ironport-hdrordr: A9a23:ijFVu65kvhcQ6rMLsQPXwXmBI+orL9Y04lQ7vn2ZFiY7TiXIra yTdaoguCMc0AxhJU3Jmbi7Scy9qADnhOJICOgqTPuftWzd1ldAQ7sSlLcKrweQeBEWs9Qtr5 uIEJIOR+EYb2IK9foSiTPQe71Lobm6GeKT9JzjJh9WPFhXgspbnmNE43OgYytLrX59dP0E/f Snl6h6jgvlXU5SQtWwB3EDUeSGjcbMjojabRkPAANiwBWSjBuzgYSKXSSw71M7aXdi0L0i+W /Kn0jS/aO4qcy2zRfayiv684lWot380dFObfb8y/T9aw+cyjpAVr4RGYFqjwpF5d1HL2xa1O Ukli1QfPibLUmhOV1d7yGdnTUImwxelEMKgWXo/0cL5/aJHA7SQvAx9b5xY1/X7VEts8p717 8O12WFt4BPBReFhyjl4cPUPisa3XZdMRIZ4J8uZlFkIMIjgYVq3MQiFYJuYeM9NTO/7JpiHP hlDcna6voTeVSGb2rBtm0qxNC3RHw8EhqPX0BH46WuonVrtWE8y1FdyN0Un38G+p54Q55Y5/ 7cOqAtkL1VVMcZYa90Ge9ES8qqDW7GRw7KLQupUB7aPbBCP2iIp4/84b0z6u3vcJsUzIEqkJ CES19cvX5aQTOZNSRP5uw9zvngehTOYd228LAs23FQgMyIeIbW
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Thread-index: AQHXkDev9/QrG+8IgUOEs2JU9EeShqt6ldOAgRojewCAC/K9gIAALOIAgAAB2YCAAApzgIABanSA
  • Thread-topic: [PATCH] RFC: Version support policy


> On Feb 22, 2022, at 3:42 PM, Marek Marczykowski-Górecki 
> <marmarek@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> 
> On Tue, Feb 22, 2022 at 04:05:19PM +0100, Jan Beulich wrote:
>> On 22.02.2022 15:58, George Dunlap wrote:
>>>> On Feb 22, 2022, at 12:18 PM, Wojtek Porczyk <woju@xxxxxxxxxxxxxxxxxxxxxx> 
>>>> wrote:
>>>> On Mon, Feb 14, 2022 at 09:50:25PM +0000, George Dunlap wrote:
>>>>> I think it’s too much effort to ask developers to try to find the actual
>>>>> minimum version of each individual dependency as things evolve.
>>>> 
>>>> By "find the actual minimum version", do you mean to get to know the 
>>>> version
>>>> number, or install that version on developer's machine?
>>> 
>>> Well suppose that a developer writes code that depends on an external 
>>> library.  The external library on their own machine is 4.5; so they know 
>>> that 4.5 works.  But will 4.4 work?  How about 4.0?  Or 3.9?  Or 2.2?  
>>> Maybe it works on 3.8+ and 2.13+, but not 2.0-2.12 or 3.0-3.7.
>>> 
>>> I don’t think it’s fair to ask people submitting patches to do the work of 
>>> tracking down which exact versions actually work and which ones don’t 
>>> actually work;
>> 
>> But somebody will need to do this. If it's not done right away, someone
>> (else) will hit a build issue on a perhaps just slightly older platform.
> 
> That's why declare what version _should_ work (and test that via CI),
> instead of trying to find what is the minimum version that is actually
> required. This may result in saying "you need libfoo 3.4" while in
> practice 3.3 would be fine too, but I think that's reasonable
> compromise.

This paragraph is a little unclear; you say “should”, but then talk about what 
has been tested to work.

To me “what version should work” means you track down the version of the 
library where the relied-upon functionality was introduced; in your libfoo 
example, it would be 3.3.  I think we should only include versions that have 
been tested to work.  If the CI loop only tests libfoo 3.4, then we should list 
3.4 as the requirement.  If someone else tests 3.3 themselves and reports that 
it works, then we can use 3.3.

 -George

Attachment: signature.asc
Description: Message signed with OpenPGP


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.