| Message ID | 20221122112623.1441905-4-Henry.Wang@arm.com (mailing list archive) |
|---|---|
| State | Superseded |
| Headers | show |
| Series | Populate entries for 4.17 | expand |
On 22/11/2022 11:26, Henry Wang wrote: > Signed-off-by: Henry Wang <Henry.Wang@arm.com> > --- > v2 -> v3: > - Take the opportunity to also adjust the 4.17 entry since this > patch will be applied only after branching. Does this means the date will not be updated in the CHANGELOG.md for 4.17? Cheers,
Hi Julien, (+George since this is about the release date) > -----Original Message----- > From: Julien Grall <julien@xen.org> > Subject: Re: [PATCH v3 3/3] CHANGELOG: Start new "unstable" section > On 22/11/2022 11:26, Henry Wang wrote: > > Signed-off-by: Henry Wang <Henry.Wang@arm.com> > > --- > > v2 -> v3: > > - Take the opportunity to also adjust the 4.17 entry since this > > patch will be applied only after branching. > > Does this means the date will not be updated in the CHANGELOG.md for 4.17? Again sorry for causing your confusion. But actually I am also confused after checking CHANGELOG in our previous releases, because none of them is precise... So in 4.16 [1], the link of the release was not correct (I believe we fixed this), in 4.15 [2], the release date was TBD, and in 4.14 [3], the 4.14 entry was not created. This makes me a little bit curious about what we are going to do this time, as you are the release technician, so I will follow your working style. Either (1) We make a fixed date of release and commit the updated version of this patch with this fixed date and release tag before branching, then don't touch the CHANGELOG at all after, Or (2) We branch off later this month and update the CHANGELOG one or two days before the official release, works for me. [1] https://xenbits.xen.org/gitweb/?p=xen.git;a=tag;h=refs/tags/RELEASE-4.16.0 [2] https://xenbits.xen.org/gitweb/?p=xen.git;a=tag;h=refs/tags/RELEASE-4.15.0 [3] https://xenbits.xen.org/gitweb/?p=xen.git;a=tag;h=refs/tags/RELEASE-4.14.0 Kind regards, Henry > > Cheers, > > -- > Julien Grall
On 22.11.2022 14:01, Henry Wang wrote: >> -----Original Message----- >> From: Julien Grall <julien@xen.org> >> Subject: Re: [PATCH v3 3/3] CHANGELOG: Start new "unstable" section >> On 22/11/2022 11:26, Henry Wang wrote: >>> Signed-off-by: Henry Wang <Henry.Wang@arm.com> >>> --- >>> v2 -> v3: >>> - Take the opportunity to also adjust the 4.17 entry since this >>> patch will be applied only after branching. >> >> Does this means the date will not be updated in the CHANGELOG.md for 4.17? > > Again sorry for causing your confusion. But actually I am also confused after > checking CHANGELOG in our previous releases, because none of them > is precise... > > So in 4.16 [1], the link of the release was not correct (I believe we fixed this), > in 4.15 [2], the release date was TBD, and in 4.14 [3], the 4.14 entry was not > created. > > This makes me a little bit curious about what we are going to do this time, > as you are the release technician, so I will follow your working style. > > Either (1) We make a fixed date of release and commit the updated version of > this patch with this fixed date and release tag before branching, then don't touch > the CHANGELOG at all after, Or (2) We branch off later this month and update the > CHANGELOG one or two days before the official release, works for me. Personally I think it should be the latter approach. Who know by how much more we're going to slip ... Jan
diff --git a/CHANGELOG.md b/CHANGELOG.md index 5ef507a49c..e2fb1974d6 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,7 +4,9 @@ Notable changes to Xen will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) -## [4.17.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) +## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD + +## [4.17.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.17.0) - 2022-12-?? ### Changed - On x86 "vga=current" can now be used together with GrUB2's gfxpayload setting. Note that
Signed-off-by: Henry Wang <Henry.Wang@arm.com> --- v2 -> v3: - Take the opportunity to also adjust the 4.17 entry since this patch will be applied only after branching. - Add 4.17 release date. - Drop Julien's Acked-by because of the change of the patch. v1 -> v2: - Add Julien's Acked-by. --- CHANGELOG.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)