Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prepare for 7.6.0 #4178

Merged
merged 1 commit into from
Sep 13, 2024
Merged

Prepare for 7.6.0 #4178

merged 1 commit into from
Sep 13, 2024

Conversation

simonvik
Copy link
Contributor

@simonvik simonvik commented Sep 13, 2024

Reviewers must check the following items:

  • Release notes are complete (major release only)
  • Release notes no longer target trunk (major release only)
  • The change log is populated
  • The VRT history in include/vrt.h is populated
  • The VRT history refers to the next VRT version
  • The macro VRT_MAJOR_VERSION was updated if applicable
  • The macro VRT_MINOR_VERSION was updated if applicable
  • The new VRT version follows releases guidelines
  • The new VRT version matches the one from the VRT history
  • Bundled devicedetect.vcl was updated (major release only)
  • Running ./autogen.des && make distcheck succeeds
  • The version in configure.ac is correct
  • The copyright notice in configure.ac covers the current year
  • The copyright output in lib/libvarnish/version.c covers the current year
  • There are no other changes than the ones listed above

@simonvik simonvik marked this pull request as ready for review September 13, 2024 10:44
Copy link
Member

@dridi dridi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will read the release notes and start checking boxes while you are busy with the following :]

doc/sphinx/whats-new/changes-7.6.rst Outdated Show resolved Hide resolved
Comment on lines 30 to 33
The port of a *listen_endpoint* given with the ``-a`` argument to ``varnishd``
can now also be a numerical port range like ``80-89``, besides the existing
options of port number (e.g. ``80``) and service name (e.g. ``http``). With a
port range, Varnish will accept connections on all ports within the range.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is the range inclusive? I think it should tell here even if it is not the reference manual.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for (i = lo; i <= hi && !error; i++) {

Its inclusive and thats the only thing that makes sense?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure it's the only one, I had to pause and wonder.

doc/sphinx/whats-new/index.rst Outdated Show resolved Hide resolved
doc/sphinx/whats-new/index.rst Outdated Show resolved Hide resolved
doc/sphinx/whats-new/upgrading-7.6.rst Outdated Show resolved Hide resolved
doc/changes.rst Outdated Show resolved Hide resolved
include/vrt.h Show resolved Hide resolved
Copy link
Member

@dridi dridi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not seeing a problem :)

@simonvik simonvik merged commit ed1243c into varnishcache:7.6 Sep 13, 2024
1 of 11 checks passed
@simonvik simonvik deleted the 7.6 branch September 13, 2024 13:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants