Release 6.5: Prepare release branch

[cmbz]

Overview

• Release 6.5: Prepare release branch
  • Prepare Release Branch
  • Merge “develop” into “master”
  • Add Milestone to Pull Requests and Issues
  • (Optional) Test Docker Images
  • Build the Guides for the Release
  • Create a Draft Release on GitHub
  • Run a Build to Create the War File
  • Build Installer (dvinstall.zip)
  • Make Artifacts Available for Download
  • Publish the Release
  • Update Guides Link
  • Close Milestone on GitHub and Create a New One
  • Update the Container Base Image Version Property

Related

See completion order here:

• Release: Dataverse Release 6.5 dataverse-pm#335

[pdurbin]

@cmbz just some feedback for you that in practice I'm not looking at the steps in the description above. I'm following https://preview.guides.gdcc.io/en/develop/developers/making-releases.html which is more real, if that makes sense. It's a checklist with very specific steps.

[cmbz]

@pdurbin I was pretty certain that we copied the list above from the https://preview.guides.gdcc.io/en/develop/developers/making-releases.html document, remember? Did it change?

[pdurbin]

It looks like we copied from https://dataverse-guide--10932.org.readthedocs.build/en/10932/developers/making-releases.html#prepare-release-branch for example.

I'm not sure if more changes were made before merging.

Also, we made another PR later:

• more post-6.4 "making releases" doc tweaks #11029

I'm just saying it's a moving target. I would prefer the description to say to go to https://preview.guides.gdcc.io/en/develop/container/dev-usage.html and do steps 7 through 23 or whatever. 😅

[cmbz]

Works for me! I'll make sure it does for 6.6.

[cmbz]

@pdurbin we should close the issue, yes?

[pdurbin]

Well, merging this PR will close it automatically:

• bump to 6.5 #11091

But up to you.

See also Leonid's comment at https://iqss.slack.com/archives/C03R1E7T4KA/p1733957819653069?thread_ts=1733948198.674539&cid=C03R1E7T4KA

[cmbz]

@pdurbin My bad! I completely missed the linked pull request.