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

Re: [Xen-devel] Xen 4.12 release planning


  • To: Lars Kurth <lars.kurth.xen@xxxxxxxxx>
  • From: Juergen Gross <jgross@xxxxxxxx>
  • Date: Fri, 27 Jul 2018 12:43:47 +0200
  • Autocrypt: addr=jgross@xxxxxxxx; prefer-encrypt=mutual; keydata= xsBNBFOMcBYBCACgGjqjoGvbEouQZw/ToiBg9W98AlM2QHV+iNHsEs7kxWhKMjrioyspZKOB ycWxw3ie3j9uvg9EOB3aN4xiTv4qbnGiTr3oJhkB1gsb6ToJQZ8uxGq2kaV2KL9650I1SJve dYm8Of8Zd621lSmoKOwlNClALZNew72NjJLEzTalU1OdT7/i1TXkH09XSSI8mEQ/ouNcMvIJ NwQpd369y9bfIhWUiVXEK7MlRgUG6MvIj6Y3Am/BBLUVbDa4+gmzDC9ezlZkTZG2t14zWPvx XP3FAp2pkW0xqG7/377qptDmrk42GlSKN4z76ELnLxussxc7I2hx18NUcbP8+uty4bMxABEB AAHNHkp1ZXJnZW4gR3Jvc3MgPGpncm9zc0BzdXNlLmRlPsLAeQQTAQIAIwUCU4xw6wIbAwcL CQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJELDendYovxMvi4UH/Ri+OXlObzqMANruTd4N zmVBAZgx1VW6jLc8JZjQuJPSsd/a+bNr3BZeLV6lu4Pf1Yl2Log129EX1KWYiFFvPbIiq5M5 kOXTO8Eas4CaScCvAZ9jCMQCgK3pFqYgirwTgfwnPtxFxO/F3ZcS8jovza5khkSKL9JGq8Nk czDTruQ/oy0WUHdUr9uwEfiD9yPFOGqp4S6cISuzBMvaAiC5YGdUGXuPZKXLpnGSjkZswUzY d9BVSitRL5ldsQCg6GhDoEAeIhUC4SQnT9SOWkoDOSFRXZ+7+WIBGLiWMd+yKDdRG5RyP/8f 3tgGiB6cyuYfPDRGsELGjUaTUq3H2xZgIPfOwE0EU4xwFgEIAMsx+gDjgzAY4H1hPVXgoLK8 B93sTQFN9oC6tsb46VpxyLPfJ3T1A6Z6MVkLoCejKTJ3K9MUsBZhxIJ0hIyvzwI6aYJsnOew cCiCN7FeKJ/oA1RSUemPGUcIJwQuZlTOiY0OcQ5PFkV5YxMUX1F/aTYXROXgTmSaw0aC1Jpo w7Ss1mg4SIP/tR88/d1+HwkJDVW1RSxC1PWzGizwRv8eauImGdpNnseneO2BNWRXTJumAWDD pYxpGSsGHXuZXTPZqOOZpsHtInFyi5KRHSFyk2Xigzvh3b9WqhbgHHHE4PUVw0I5sIQt8hJq 5nH5dPqz4ITtCL9zjiJsExHuHKN3NZsAEQEAAcLAXwQYAQIACQUCU4xwFgIbDAAKCRCw3p3W KL8TL0P4B/9YWver5uD/y/m0KScK2f3Z3mXJhME23vGBbMNlfwbr+meDMrJZ950CuWWnQ+d+ Ahe0w1X7e3wuLVODzjcReQ/v7b4JD3wwHxe+88tgB9byc0NXzlPJWBaWV01yB2/uefVKryAf AHYEd0gCRhx7eESgNBe3+YqWAQawunMlycsqKa09dBDL1PFRosF708ic9346GLHRc6Vj5SRA UTHnQqLetIOXZm3a2eQ1gpQK9MmruO86Vo93p39bS1mqnLLspVrL4rhoyhsOyh0Hd28QCzpJ wKeHTd0MAWAirmewHXWPco8p1Wg+V+5xfZzuQY0f4tQxvOpXpt4gQ1817GQ5/Ed/wsDtBBgB CAAgFiEEhRJncuj2BJSl0Jf3sN6d1ii/Ey8FAlrd8NACGwIAgQkQsN6d1ii/Ey92IAQZFggA HRYhBFMtsHpB9jjzHji4HoBcYbtP2GO+BQJa3fDQAAoJEIBcYbtP2GO+TYsA/30H/0V6cr/W V+J/FCayg6uNtm3MJLo4rE+o4sdpjjsGAQCooqffpgA+luTT13YZNV62hAnCLKXH9n3+ZAgJ RtAyDWk1B/0SMDVs1wxufMkKC3Q/1D3BYIvBlrTVKdBYXPxngcRoqV2J77lscEvkLNUGsu/z W2pf7+P3mWWlrPMJdlbax00vevyBeqtqNKjHstHatgMZ2W0CFC4hJ3YEetuRBURYPiGzuJXU pAd7a7BdsqWC4o+GTm5tnGrCyD+4gfDSpkOT53S/GNO07YkPkm/8J4OBoFfgSaCnQ1izwgJQ jIpcG2fPCI2/hxf2oqXPYbKr1v4Z1wthmoyUgGN0LPTIm+B5vdY82wI5qe9uN6UOGyTH2B3p hRQUWqCwu2sqkI3LLbTdrnyDZaixT2T0f4tyF5Lfs+Ha8xVMhIyzNb1byDI5FKCb
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Stefano Stabellini <sstabellini@xxxxxxxxxx>
  • Delivery-date: Fri, 27 Jul 2018 10:43:55 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
  • Openpgp: preference=signencrypt

On 27/07/18 12:32, Lars Kurth wrote:
> 
> 
>> On 27 Jul 2018, at 08:51, Juergen Gross <jgross@xxxxxxxx
>> <mailto:jgross@xxxxxxxx>> wrote:
>>
>> On 27/07/18 00:13, Stefano Stabellini wrote:
>>> On Wed, 25 Jul 2018, Juergen Gross wrote:
>>>> Its time to plan the Xen 4.12 release dates.
>>>>
>>>> There have been concerns with the schedule of 6 months between releases,
>>>> as this scheme is leading to too many supported versions of Xen at a
>>>> time. The needed resources to backport bug fixes and security fixes as
>>>> well as doing the tests for all those releases are a limiting factor to
>>>> push out the current main release as well as point releases on time.
>>>>
>>>> After some discussions at the Xen developer summit, on xen-devel and
>>>> between the committers a slightly longer release cycle of 8 or 9 months
>>>> was suggested.
>>>>
>>>> With 18 months of full support and 36 months of security support the
>>>> number of concurrent supported releases will be the same with either 8
>>>> or 9 months release cycles, so I have chosen an 8 month cycle for now.
>>>> Having only 3 possible times in the year for a release will make it
>>>> easier to avoid major holiday seasons.
>>>>
>>>> In case there is no objection I'm planning Xen 4.12 with:
>>>>
>>>> * Last posting date: December 14th, 2018
>>>> * Hard code freeze: January 11th, 2019
>>>> * Release: March 7th, 2019
>>>>
>>>> Release of Xen 4.13 would then be early November 2019, 4.14 at early
>>>> July 2020.
>>>
>>> Given the holdidays season (it is not just Julien going on vacation but
>>> pretty much everybody), wouldn't it be better to move the hard code
>>> freeze by a couple of weeks? For instance Jan 25th? We can still keep
>>> the release date as Mar 7th, there should be still enough time?
>>
>> I don't think planning with a 6 week freeze period is a good idea. The
>> last releases took longer than 2 months.
>>
>> We could slip the complete release by 2 weeks, of course. In this case
>> I'd move the last posting date to January. So something like:
>>
>> * Last posting date: January 11th, 2019
>> * Hard code freeze: January 25th, 2019
>> * Release: March 21st, 2019
> 
> Another alternative would be to move the dates backwards rather than
> forward. The 4.12 development window effectively opened 21-06-18, so a
> last posting data and hard code freeze before Xmas should be OK. Then
> assume that there won't be RC's for at last 2 (maybe 3) weeks during the
> winter holidays. But as long as someone is there to keep an eye on
> OSSTEST and to do a force push and build an RC1 before Xmas that may be
> OK: but it would probably still be OK if RC1 slipped until just after
> New Years Eve.

You are neglecting that the reason for no RC directly after the freeze
is normally due to bugs. And those need to be found and fixed by
someone. So putting the freeze directly before a holiday season just
makes the freeze longer without any major advantage.


Juergen

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

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