From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============0142855251102358894==" MIME-Version: 1.0 From: Zawadzki, Tomasz Subject: [SPDK] Re: Preparation for SPDK 22.09 release Date: Fri, 23 Sep 2022 20:21:00 +0000 Message-ID: In-Reply-To: DM6PR11MB42207F63B6B99EF781B58996EE799@DM6PR11MB4220.namprd11.prod.outlook.com List-ID: To: spdk@lists.01.org --===============0142855251102358894== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Hello everyone, Merge window for SPDK 22.09 is now closed. Formal release will take place b= y September 30th. Branch "v22.09.x" is created and last patch on it tagged "v22.09-rc1". Any critical fixes identified shall be submitted to master branch and hash = tagged "22.09". Those will be backported to the "v22.09.x" branch. Thanks, Tomek > -----Original Message----- > From: Zawadzki, Tomasz > Sent: Tuesday, August 30, 2022 4:15 PM > To: Storage Performance Development Kit > Subject: [SPDK] Preparation for SPDK 22.09 release > = > Hello all, > = > The merge window for SPDK 22.09 release will close by September 23rd. > Please ensure all patches you believe should be included in the release a= re > merged to 'master' branch by this date. > You can do it by adding a hashtag '22.09' in Gerrit on those patches. > = > The current set of patches that are tagged and need to be reviewed can be > seen here: > https://review.spdk.io/gerrit/q/hashtag:%2222.09%22+status:open > = > On September 23rd new branch 'v22.09.x' will be created, and a patch on it > will be tagged as release candidate. > Then, by September 30th, a formal release will take place tagging the last > patch on the branch as SPDK 22.09. > = > Between release candidate and formal release, only critical fixes shall be > backported to the 'v22.09.x' branch. > Development can continue without disruptions on 'master' branch. > = > Thanks, > Tomek --===============0142855251102358894==--