Release: Dataverse Release 6.5

[cmbz]

Overview

• Main Dataverse release task tracking issue for release 6.5
• This tracking issue lists all sub-issues needed to make a release. Details are found in the Making Releases guide.
• Task assignments are generally made during the first sprint of the release
• Sub-issues are created in the appropriate repos (e.g., dataverse, dataverse-pm, or dataverse.harvard.edu)

Note

• We are prototyping this process. Release 6.5 is the first time we are trying this approach.

Release Timeline

• Start: FY25 Sprint 7 (2024-09-25 - 2024-10-09)
• Community PR Last Call: FY25 Sprint 10, on 2024-11-06 (2024-11-06)
• Core PR Last Call: FY25 Sprint 11, on 2024-11-27
• End: FY25 Sprint 11 (2024-11-20 - 2024-12-04)
• Release Date: Dec 6, 2024 (Friday)

Issues

• Release 6.5: Announce upcoming release #339
• Release 6.5: Community last call announcement #348
• Release 6.5: Conduct performance testing dataverse#10944
• Release 6.5: Conduct smoke testing dataverse#10946
• Release 6.5: Create release notes dataverse#10952
• Release 6.5: Deploy release candidate to demo.dataverse.org dataverse#10953
• Release 6.5: Prepare release branch dataverse#10954
• Release 6.5: Announce release #340
• Release 6.5: Deploy release on demo.dataverse.org dataverse.harvard.edu#313
• Release 6.5: Deploy on dataverse.harvard.edu dataverse.harvard.edu#314

Related

• update making releases page post 6.4 dataverse#10932

Resources

• FY25 Running Sprint Planning Notes
• Monitor: Dataverse Sprints and Releases, FY25 #228

[DS-INRAE]

Thanks for sharing! Can we post the release timeline in zulip or should we wait for a communication from your side ? 😀

[DS-INRAE]

Also, just a question on "freeze", does it mean PRs are nolonger taken into the review/QA process for the release or nolonger merged? ❄

[cmbz]

Hi @DS-INRAE! Freeze was a bad choice of words, but yes. I really meant "Last call!" Meaning it would be the last date we can consider including small PRs in a release. I'll change that in the issue body. Apologies for the confusion.

Also, we're experimenting with this new process to try to streamline, speed up, and better plan our releases. Therefore, it's a work in progress! Please expect changes as we try things out. :)

[DS-INRAE]

Thanks for the clarification Ceilyn!

[cmbz]

@DS-INRAE Hi Dimitri, just a fast update. You'd asked about the timeline here: #335 (comment). I'll send out the 6.5 announcement tomorrow. :)

[DS-INRAE]

Thanks! GLad to hear it is ready to be anounced 😄