IQSS / IQSS/dataverse

add additional dates to release date script

Open Beginner friendly
#12,445 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

See "NEW" below.

  • Write the script in pure Python with no dependencies.
  • Work backward from the provided Release Date, which we prefer to be on a Wednesday.
  • Curation Team Review starts on the Monday prior. After the date, put "(allocate 5 full days)".
  • Code Freeze starts on the Thursday prior.
  • Core PR Last Call starts on the Thursday prior.
  • Community PR Last Call starts on the Thursday prior.
  • NEW: Review Priorities on the Thursday prior.
  • Start starts three months before the Release Date, on a Thursday. It's ok to put "??" for the sprint number.
  • NEW: Define Release (show plan for the release) two weeks before start.

Here's some example output:

  • Start: Sprint ??, 2026-03-26
  • Community PR Last Call: 2026-05-21
  • Core PR Last Call: 2026-05-28
  • Code Freeze: 2026-06-04
  • Curation Team Review: 2026-06-08 (allocate 5 full days)
  • Release Date: 2026-06-17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Locate the release date script and run it with the example Release Date of 2026-06-17 to inspect its current output. Add Review Priorities and Define Release at the specified dates, keeping the script dependency-free, and verify the output includes all listed milestones and the requested five-day note.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
release
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
68/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.