[PATCH 0/3] Final CHANGELOG changes for 4.18

[PATCH 0/3] Final CHANGELOG changes for 4.18

[Henry Wang]

Hi all,

This series should be the final CHANGELOG changes for 4.18.

The first patch is mentioning the MISRA-C improvement during the
4.18 dev cycle, so should be committed before we branch.

The second patch sets the release date and tag of 4.18 release and
should be included in both the staging and stable-4.18 once we
branch (next week).

The third patch starts a new unstable section, so should be in
unstable master/staging only.

Thanks.

Henry Wang (3):
  CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle
  CHANGELOG.md: Set 4.18 release date and tag
  CHANGELOG.md: Start new "unstable" section

 CHANGELOG.md | 9 +++++++++
 1 file changed, 9 insertions(+)

-- 
2.25.1

[PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Henry Wang]

Signed-off-by: Henry Wang <Henry.Wang@arm.com>
---
 CHANGELOG.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 165c5caf9b..47e98f036f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
    nodes using a device tree overlay binary (.dtbo).
  - Introduce two new hypercalls to map the vCPU runstate and time areas by
    physical rather than linear/virtual addresses.
+ - The project has now officially adopted 72 rules of MISRA-C.
 
 ### Removed
  - On x86, the "pku" command line option has been removed.  It has never
-- 
2.25.1

[PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Henry Wang]

Signed-off-by: Henry Wang <Henry.Wang@arm.com>
---
 CHANGELOG.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 47e98f036f..3c83878c9b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,7 +4,7 @@ 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/)
 
-## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
+## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
 
 ### Changed
  - Repurpose command line gnttab_max_{maptrack_,}frames options so they don't
-- 
2.25.1

[PATCH 3/3] CHANGELOG.md: Start new "unstable" section

[Henry Wang]

Signed-off-by: Henry Wang <Henry.Wang@arm.com>
---
 CHANGELOG.md | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3c83878c9b..48aff24f3a 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -4,6 +4,14 @@ 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/)
 
+## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
+
+### Changed
+
+### Added
+
+### Removed
+
 ## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
 
 ### Changed
-- 
2.25.1

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Stefano Stabellini]

On Thu, 19 Oct 2023, Henry Wang wrote:
> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
> ---
>  CHANGELOG.md | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 165c5caf9b..47e98f036f 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>     nodes using a device tree overlay binary (.dtbo).
>   - Introduce two new hypercalls to map the vCPU runstate and time areas by
>     physical rather than linear/virtual addresses.
> + - The project has now officially adopted 72 rules of MISRA-C.

I counted them again, they are 71 today. We have accepted 3 more
recently but for the CHANGELOG.md I would stick with what is on
docs/misra/rules.rst

Assuming 72 is changed to 71 on commit:

Acked-by: Stefano Stabellini <sstabellini@kernel.org>

Re: [PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Stefano Stabellini]

On Thu, 19 Oct 2023, Henry Wang wrote:
> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
> ---
>  CHANGELOG.md | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 47e98f036f..3c83878c9b 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -4,7 +4,7 @@ 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/)
>  
> -## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
> +## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30

Should we use xenbits.xenproject.org instead? I think that's the
official name. In any case:

Acked-by: Stefano Stabellini <sstabellini@kernel.org>

Re: [PATCH 3/3] CHANGELOG.md: Start new "unstable" section

[Stefano Stabellini]

On Thu, 19 Oct 2023, Henry Wang wrote:
> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
> ---
>  CHANGELOG.md | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/CHANGELOG.md b/CHANGELOG.md
> index 3c83878c9b..48aff24f3a 100644
> --- a/CHANGELOG.md
> +++ b/CHANGELOG.md
> @@ -4,6 +4,14 @@ 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/)
>  
> +## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD

same here about xen.org/xenproject.org

In any case:

Acked-by: Stefano Stabellini <sstabellini@kernel.org>


> +### Changed
> +
> +### Added
> +
> +### Removed
> +
>  ## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
>  
>  ### Changed

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Henry Wang]

Hi Stefano,

> On Oct 20, 2023, at 00:13, Stefano Stabellini <sstabellini@kernel.org> wrote:
> 
> On Thu, 19 Oct 2023, Henry Wang wrote:
>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>> ---
>> CHANGELOG.md | 1 +
>> 1 file changed, 1 insertion(+)
>> 
>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>> index 165c5caf9b..47e98f036f 100644
>> --- a/CHANGELOG.md
>> +++ b/CHANGELOG.md
>> @@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>    nodes using a device tree overlay binary (.dtbo).
>>  - Introduce two new hypercalls to map the vCPU runstate and time areas by
>>    physical rather than linear/virtual addresses.
>> + - The project has now officially adopted 72 rules of MISRA-C.
> 
> I counted them again, they are 71 today. We have accepted 3 more
> recently but for the CHANGELOG.md I would stick with what is on
> docs/misra/rules.rst

lol I will send a v2.

> 
> Assuming 72 is changed to 71 on commit:
> 
> Acked-by: Stefano Stabellini <sstabellini@kernel.org>

Thanks!

Kind regards,
Henry

Re: [PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Henry Wang]

> On Oct 20, 2023, at 00:14, Stefano Stabellini <sstabellini@kernel.org> wrote:
> 
> On Thu, 19 Oct 2023, Henry Wang wrote:
>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>> ---
>> CHANGELOG.md | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>> 
>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>> index 47e98f036f..3c83878c9b 100644
>> --- a/CHANGELOG.md
>> +++ b/CHANGELOG.md
>> @@ -4,7 +4,7 @@ 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/)
>> 
>> -## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
>> +## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
> 
> Should we use xenbits.xenproject.org instead? I think that's the
> official name. In any case:

Hmmm, good question, but after some deeper look somehow I am more confused now.

So if I click the xen.git link in xenbits.xenproject.org <http://xenbits.xenproject.org/>, I will be directed to
"http://xenbits.xen.org/gitweb/?p=xen.git;a=summary”, where the http and https git URL
are both using "xenbits.xen.org”.

However, "https://xenbits.xenproject.org/gitweb/?p=xen.git;a=summary” is also a valid
link, but the https and http git URL are still both using “xenbits.xen.org”, also, all our previous
releases seem to use "xenbits.xen.org".

Could anyone in this community long enough provide a bit more details/clarifications on this?
I am ok to either change or not if the discussion is settled.

> 
> Acked-by: Stefano Stabellini <sstabellini@kernel.org>

Thank you very much!

Kind regards,
Henry

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Henry Wang]

Hi Stefano,

> On Oct 20, 2023, at 00:13, Stefano Stabellini <sstabellini@kernel.org> wrote:
> 
> On Thu, 19 Oct 2023, Henry Wang wrote:
>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>> ---
>> CHANGELOG.md | 1 +
>> 1 file changed, 1 insertion(+)
>> 
>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>> index 165c5caf9b..47e98f036f 100644
>> --- a/CHANGELOG.md
>> +++ b/CHANGELOG.md
>> @@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>    nodes using a device tree overlay binary (.dtbo).
>>  - Introduce two new hypercalls to map the vCPU runstate and time areas by
>>    physical rather than linear/virtual addresses.
>> + - The project has now officially adopted 72 rules of MISRA-C.
> 
> I counted them again, they are 71 today. We have accepted 3 more
> recently but for the CHANGELOG.md I would stick with what is on
> docs/misra/rules.rst

Thanks for the pointer of the doc, I checked the doc and noticed that
we actually support 65 rules and 6 directives (65+6=71 so you are correct),
but to avoid the confusion, would you mind me writing in this way:
"The project has officially adopted 6 directives and 65 rules of MISRA-C”?

Kind regards,
Henry

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Stefano Stabellini]

[-- Attachment #1: Type: text/plain, Size: 1299 bytes --]

On Fri, 20 Oct 2023, Henry Wang wrote:
> Hi Stefano,
> 
> > On Oct 20, 2023, at 00:13, Stefano Stabellini <sstabellini@kernel.org> wrote:
> > 
> > On Thu, 19 Oct 2023, Henry Wang wrote:
> >> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
> >> ---
> >> CHANGELOG.md | 1 +
> >> 1 file changed, 1 insertion(+)
> >> 
> >> diff --git a/CHANGELOG.md b/CHANGELOG.md
> >> index 165c5caf9b..47e98f036f 100644
> >> --- a/CHANGELOG.md
> >> +++ b/CHANGELOG.md
> >> @@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
> >>    nodes using a device tree overlay binary (.dtbo).
> >>  - Introduce two new hypercalls to map the vCPU runstate and time areas by
> >>    physical rather than linear/virtual addresses.
> >> + - The project has now officially adopted 72 rules of MISRA-C.
> > 
> > I counted them again, they are 71 today. We have accepted 3 more
> > recently but for the CHANGELOG.md I would stick with what is on
> > docs/misra/rules.rst
> 
> Thanks for the pointer of the doc, I checked the doc and noticed that
> we actually support 65 rules and 6 directives (65+6=71 so you are correct),
> but to avoid the confusion, would you mind me writing in this way:
> "The project has officially adopted 6 directives and 65 rules of MISRA-C”?

Sure that's fine!

Re: [PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Jan Beulich]

On 20.10.2023 03:23, Henry Wang wrote:
> 
> 
>> On Oct 20, 2023, at 00:14, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>
>> On Thu, 19 Oct 2023, Henry Wang wrote:
>>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>>> ---
>>> CHANGELOG.md | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>> index 47e98f036f..3c83878c9b 100644
>>> --- a/CHANGELOG.md
>>> +++ b/CHANGELOG.md
>>> @@ -4,7 +4,7 @@ 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/)
>>>
>>> -## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
>>> +## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
>>
>> Should we use xenbits.xenproject.org instead? I think that's the
>> official name. In any case:
> 
> Hmmm, good question, but after some deeper look somehow I am more confused now.
> 
> So if I click the xen.git link in xenbits.xenproject.org <http://xenbits.xenproject.org/>, I will be directed to
> "http://xenbits.xen.org/gitweb/?p=xen.git;a=summary”, where the http and https git URL
> are both using "xenbits.xen.org”.
> 
> However, "https://xenbits.xenproject.org/gitweb/?p=xen.git;a=summary” is also a valid
> link, but the https and http git URL are still both using “xenbits.xen.org”, also, all our previous
> releases seem to use "xenbits.xen.org".
> 
> Could anyone in this community long enough provide a bit more details/clarifications on this?

Well, "xenproject" appeared later as a name, with the intention of
becoming the "canonical" one. Still it was likely easiest at the time
to simply add respective redirects in the web server(s).

Jan

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Nicola Vetrini]

On 20/10/2023 03:31, Henry Wang wrote:
> Hi Stefano,
> 
>> On Oct 20, 2023, at 00:13, Stefano Stabellini <sstabellini@kernel.org> 
>> wrote:
>> 
>> On Thu, 19 Oct 2023, Henry Wang wrote:
>>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>>> ---
>>> CHANGELOG.md | 1 +
>>> 1 file changed, 1 insertion(+)
>>> 
>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>> index 165c5caf9b..47e98f036f 100644
>>> --- a/CHANGELOG.md
>>> +++ b/CHANGELOG.md
>>> @@ -33,6 +33,7 @@ The format is based on [Keep a 
>>> Changelog](https://keepachangelog.com/en/1.0.0/)
>>>    nodes using a device tree overlay binary (.dtbo).
>>>  - Introduce two new hypercalls to map the vCPU runstate and time 
>>> areas by
>>>    physical rather than linear/virtual addresses.
>>> + - The project has now officially adopted 72 rules of MISRA-C.
>> 
>> I counted them again, they are 71 today. We have accepted 3 more
>> recently but for the CHANGELOG.md I would stick with what is on
>> docs/misra/rules.rst
> 
> Thanks for the pointer of the doc, I checked the doc and noticed that
> we actually support 65 rules and 6 directives (65+6=71 so you are 
> correct),
> but to avoid the confusion, would you mind me writing in this way:
> "The project has officially adopted 6 directives and 65 rules of 
> MISRA-C”?
> 
> Kind regards,
> Henry

Just dropping this small suggestion: the general term used by MISRA to 
indicate either
a Rule or a Directive is Guideline, so it's also correct to say that 71 
Guidelines have been
adopted.

-- 
Nicola Vetrini, BSc
Software Engineer, BUGSENG srl (https://bugseng.com)

Re: [PATCH 1/3] CHANGELOG.md: Mention the MISRA-C improvement in 4.18 dev cycle

[Henry Wang]

Hi Nicola,

> On Oct 20, 2023, at 14:28, Nicola Vetrini <nicola.vetrini@bugseng.com> wrote:
> 
> On 20/10/2023 03:31, Henry Wang wrote:
>> Hi Stefano,
>>> On Oct 20, 2023, at 00:13, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>> On Thu, 19 Oct 2023, Henry Wang wrote:
>>>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>>>> ---
>>>> CHANGELOG.md | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>>> index 165c5caf9b..47e98f036f 100644
>>>> --- a/CHANGELOG.md
>>>> +++ b/CHANGELOG.md
>>>> @@ -33,6 +33,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/)
>>>>   nodes using a device tree overlay binary (.dtbo).
>>>> - Introduce two new hypercalls to map the vCPU runstate and time areas by
>>>>   physical rather than linear/virtual addresses.
>>>> + - The project has now officially adopted 72 rules of MISRA-C.
>>> I counted them again, they are 71 today. We have accepted 3 more
>>> recently but for the CHANGELOG.md I would stick with what is on
>>> docs/misra/rules.rst
>> Thanks for the pointer of the doc, I checked the doc and noticed that
>> we actually support 65 rules and 6 directives (65+6=71 so you are correct),
>> but to avoid the confusion, would you mind me writing in this way:
>> "The project has officially adopted 6 directives and 65 rules of MISRA-C”?
>> Kind regards,
>> Henry
> 
> Just dropping this small suggestion: the general term used by MISRA to indicate either
> a Rule or a Directive is Guideline, so it's also correct to say that 71 Guidelines have been
> adopted.

Correct, I wrote separately just to simply keep some consistency between the wording that
we already did for 4.17, see [1].

[1] https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=CHANGELOG.md;h=165c5caf9beaff72da4ea07d326743500f470466;hb=HEAD#l55

Kind regards,
Henry

> 
> -- 
> Nicola Vetrini, BSc
> Software Engineer, BUGSENG srl (https://bugseng.com)

Re: [PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Henry Wang]

Hi Jan,

> On Oct 20, 2023, at 13:59, Jan Beulich <jbeulich@suse.com> wrote:
> 
> On 20.10.2023 03:23, Henry Wang wrote:
>> 
>> 
>>> On Oct 20, 2023, at 00:14, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>> 
>>> On Thu, 19 Oct 2023, Henry Wang wrote:
>>>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>>>> ---
>>>> CHANGELOG.md | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>> 
>>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>>> index 47e98f036f..3c83878c9b 100644
>>>> --- a/CHANGELOG.md
>>>> +++ b/CHANGELOG.md
>>>> @@ -4,7 +4,7 @@ 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/)
>>>> 
>>>> -## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
>>>> +## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
>>> 
>>> Should we use xenbits.xenproject.org instead? I think that's the
>>> official name. In any case:
>> 
>> Hmmm, good question, but after some deeper look somehow I am more confused now.
>> 
>> So if I click the xen.git link in xenbits.xenproject.org <http://xenbits.xenproject.org/>, I will be directed to
>> "http://xenbits.xen.org/gitweb/?p=xen.git;a=summary”, where the http and https git URL
>> are both using "xenbits.xen.org”.
>> 
>> However, "https://xenbits.xenproject.org/gitweb/?p=xen.git;a=summary” is also a valid
>> link, but the https and http git URL are still both using “xenbits.xen.org”, also, all our previous
>> releases seem to use "xenbits.xen.org".
>> 
>> Could anyone in this community long enough provide a bit more details/clarifications on this?
> 
> Well, "xenproject" appeared later as a name, with the intention of
> becoming the "canonical" one. Still it was likely easiest at the time
> to simply add respective redirects in the web server(s).

I take above comment as you also prefer the “xenbits.xenproject.org”? Could you please kindly
confirm that? If that is the case, I will send a v3 with the link changed, as 2 committers now both
prefer the “xenproject” one and I won’t argue for that.

Kind regards,
Henry

> 
> Jan

Re: [PATCH 2/3] CHANGELOG.md: Set 4.18 release date and tag

[Jan Beulich]

On 20.10.2023 17:06, Henry Wang wrote:
>> On Oct 20, 2023, at 13:59, Jan Beulich <jbeulich@suse.com> wrote:
>> On 20.10.2023 03:23, Henry Wang wrote:
>>>> On Oct 20, 2023, at 00:14, Stefano Stabellini <sstabellini@kernel.org> wrote:
>>>> On Thu, 19 Oct 2023, Henry Wang wrote:
>>>>> Signed-off-by: Henry Wang <Henry.Wang@arm.com>
>>>>> ---
>>>>> CHANGELOG.md | 2 +-
>>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/CHANGELOG.md b/CHANGELOG.md
>>>>> index 47e98f036f..3c83878c9b 100644
>>>>> --- a/CHANGELOG.md
>>>>> +++ b/CHANGELOG.md
>>>>> @@ -4,7 +4,7 @@ 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/)
>>>>>
>>>>> -## [unstable UNRELEASED](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=staging) - TBD
>>>>> +## [4.18.0](https://xenbits.xen.org/gitweb/?p=xen.git;a=shortlog;h=RELEASE-4.18.0) - 2023-10-30
>>>>
>>>> Should we use xenbits.xenproject.org instead? I think that's the
>>>> official name. In any case:
>>>
>>> Hmmm, good question, but after some deeper look somehow I am more confused now.
>>>
>>> So if I click the xen.git link in xenbits.xenproject.org <http://xenbits.xenproject.org/>, I will be directed to
>>> "http://xenbits.xen.org/gitweb/?p=xen.git;a=summary”, where the http and https git URL
>>> are both using "xenbits.xen.org”.
>>>
>>> However, "https://xenbits.xenproject.org/gitweb/?p=xen.git;a=summary” is also a valid
>>> link, but the https and http git URL are still both using “xenbits.xen.org”, also, all our previous
>>> releases seem to use "xenbits.xen.org".
>>>
>>> Could anyone in this community long enough provide a bit more details/clarifications on this?
>>
>> Well, "xenproject" appeared later as a name, with the intention of
>> becoming the "canonical" one. Still it was likely easiest at the time
>> to simply add respective redirects in the web server(s).
> 
> I take above comment as you also prefer the “xenbits.xenproject.org”? Could you please kindly
> confirm that?

Indeed I do.

Jan