[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Xen 4.18 release: Reminder about feature/code freeze
 
- To: Ayan Kumar Halder <ayankuma@xxxxxxx>
 
- From: Julien Grall <julien.grall.oss@xxxxxxxxx>
 
- Date: Mon, 11 Sep 2023 04:09:03 -0400
 
- Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Anthony PERARD <anthony.perard@xxxxxxxxxx>, 	Bertrand Marquis <Bertrand.Marquis@xxxxxxx>, Henry Wang <Henry.Wang@xxxxxxx>, 	Jan Beulich <jbeulich@xxxxxxxx>, Roger Pau Monné <roger.pau@xxxxxxxxxx>, 	"community.manager@xxxxxxxxxxxxxx" <community.manager@xxxxxxxxxxxxxx>, "jgross@xxxxxxxx" <jgross@xxxxxxxx>, 	"sstabellini@xxxxxxxxxx" <sstabellini@xxxxxxxxxx>, 	"xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
 
- Delivery-date: Mon, 11 Sep 2023 08:09:43 +0000
 
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
 
 
 
 
 Hi Henry, 
 
On 11/09/2023 02:08, Henry Wang wrote: 
> CAUTION: This message has originated from an External Source. Please  
> use proper judgment and caution when opening attachments, clicking  
> links, or responding to this email. 
> 
> Hi everyone, 
> 
> This is the reminder that we are currently in the feature freeze. I  
> apologise 
> 
> for the delay. 
> 
> I decided to make the code freeze date on Fri Sep 22, 2023, to give  
> people more 
> 
> time to react because of my late reminder about feature freeze. The  
> hard code 
> 
> freeze date will remain unchanged, i.e. Fri Oct 6, 2023. So currently  
> we have 2 
> 
> weeks before code freeze and another 4 weeks before hard code freeze. If 
> 
> everything goes well, we can cut 4.18 rc1 at Fri Sep 29, 2023. 
> 
> Also, below is the critical items on my list for 4.18 release: 
> 
> 1. [PATCH 0/7] tools: More Python 3 fixes (part 1 of N) 
> 
> https://gitlab.com/xen-project/xen/-/issues/114 
> 
> 2. tools: Switch to non-truncating XENVER_* ops 
> 
> https://lore.kernel.org/xen-devel/20230117135336.11662-1-andrew.cooper3@xxxxxxxxxx/ 
> 
> 3. dom0less vs xenstored setup race Was: xen | Failed pipeline for  
> staging | 6a47ba2f 
> 
> https://marc.info/?l=xen-devel&m=168312468808977  
> <https://marc.info/?l=xen-devel&m=168312468808977> 
> 
> https://marc.info/?l=xen-devel&m=168312687610283  
> <https://marc.info/?l=xen-devel&m=168312687610283> 
> 
> 4. The proper eIBRS support for x86 
> 
> https://lore.kernel.org/xen-devel/ec8e75da-743b-50dc-4665-854c446c974e@xxxxxxxxxx/ 
> 
> 5. [PATCH 1/2] credit: Limit load balancing to once per millisecond 
> 
> https://lore.kernel.org/xen-devel/20230630113756.672607-1-george.dunlap@xxxxxxxxx/ 
> 
> 6. [PATCH 0/2]  Revoke IOMEM/IO port/IRQ permissions on PCI detach for  
> HVM guest 
> 
> https://lore.kernel.org/xen-devel/20230809103305.30561-1-julien@xxxxxxx/ 
> 
> 7. [PATCH v2 0/8] Fixes to debugging facilities 
> 
> https://lore.kernel.org/xen-devel/21cc28b9-91d1-1e6e-23ac-00c44f3ec08e@xxxxxxxxx/ 
> 
 
Did you miss "[PATCH v6 00/13] xen/arm: Split MMU code as the prepration  
of MPU work" ? 
 
 AFAIU Henry listed all the critical series for 4.18. Can you explain why do you think this is one? 
 
 Cheers, 
 
  
 
It see that patches from [PATCH v6 06/13] xen/arm: Split page table  
related code to mmu/pt.c ... are yet to be reviewed and committed. 
 
- Ayan 
 
> Kind regards, 
> 
> Henry 
> 
  
 
    
     |