NVIDIA-Merlin / NVIDIA-Merlin/Merlin

Transition to calendar versioning

Open
#714 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
907
Forks
129
PR merge metrics
No merged PRs in 30d

Description

This issue has no description.

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

The issue body names no files, tests, or entry points. First clarify the intended calendar-versioning scheme, affected release workflow, and compatibility requirements with maintainers. Done should include an agreed versioning policy and updated release-related project artifacts, but the payload does not identify which artifacts are involved.

Written by the indexing model from the issue text.

Assessment

Domain
release
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.