On 6/2/2020 12:39 PM, Iremonger, Bernard wrote: > Hi Ferruh, > >> -----Original Message----- >> From: dev <dev-boun...@dpdk.org> On Behalf Of Ferruh Yigit >> Sent: Thursday, May 28, 2020 4:56 PM >> To: dpdk-dev <dev@dpdk.org> >> Cc: Thomas Monjalon <tho...@monjalon.net> >> Subject: [dpdk-dev] DPDK Release Status Meeting 28/05/2020 >> >> Minutes 28 May 2020 >> ------------------- >> >> Agenda: >> * Release Dates >> * Zoom vs Skype >> * 20.05 retrospective >> * LTS >> >> Participants: >> * Arm >> * Debian/Microsoft >> * Intel >> * Mellanox >> * NXP >> * Red Hat >> >> >> Release Dates >> ------------- >> >> * v20.05 is released on Tuesday 26 May >> * https://mails.dpdk.org/archives/dev/2020-May/168769.html >> * https://core.dpdk.org/download/ >> * https://doc.dpdk.org/guides/rel_notes/release_20_05.html >> >> Thanks everyone who contributed. >> >> * v20.08 dates: >> * Proposal/V1:Friday, 12 June 2020 > > Is the merge deadline Friday, 3 July? > >> * -rc1:Wednesday, 8 July 2020
Hi Bernard, I personally find having the distinction for "merge deadline" and '-rc1" is confusing. I prefer to follow only -rc1. The thing to consider is, if -rc1 is 8 July, and you are sending a new version of the patch on that day, 8 July, I think it is not surprising if the patch misses the -rc1. So patch should be at least a few days before the -rc1, to give enough time for it to be processed. Should we formalize that a few days as "merge deadline" and explicitly call that day, as said above I don't think so but I don't know what others think about it. Roughly, please send your last version of the patch at least 2 work days before the -rc1. @Thomas, what do you think, is it a fair measurement?
