[GH-ISSUE #1079] Establish Version Numbering System for tinytorch (Similar to mlsysbook) #1684

Closed
opened 2026-04-11 08:02:06 -05:00 by GiteaMirror · 1 comment
Owner

Originally created by @profvjreddi on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1079

We need to develop and implement a version numbering system for tinytorch, similar to the system used in mlsysbook. This will help track changes and improvements efficiently and ensure consistent referencing across documentation and releases.

Tasks:

  • Review the versioning approach in mlsysbook for inspiration and best practices
  • Propose a scheme (e.g., semantic versioning or a custom structure)
  • Document the system and guidelines for contributors
  • Update tinytorch documentation to reflect the new system

Context:

  • The lack of a versioning system makes tracking changes and citing specific development states difficult.
  • mlsysbook provides a strong baseline for such a numbering system—mirroring or extending this approach could unify our project workflows.

Let’s discuss and finalize the versioning policy as soon as possible.

Originally created by @profvjreddi on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/harvard-edge/cs249r_book/issues/1079 We need to develop and implement a version numbering system for tinytorch, similar to the system used in mlsysbook. This will help track changes and improvements efficiently and ensure consistent referencing across documentation and releases. **Tasks:** - Review the versioning approach in mlsysbook for inspiration and best practices - Propose a scheme (e.g., semantic versioning or a custom structure) - Document the system and guidelines for contributors - Update tinytorch documentation to reflect the new system **Context:** - The lack of a versioning system makes tracking changes and citing specific development states difficult. - mlsysbook provides a strong baseline for such a numbering system—mirroring or extending this approach could unify our project workflows. Let’s discuss and finalize the versioning policy as soon as possible.
GiteaMirror added the area: tinytorch label 2026-04-11 08:02:06 -05:00
Author
Owner

@profvjreddi commented on GitHub (Jan 23, 2026):

This has been implemented!

Versioning system established in commit 858c762ca (January 13, 2026).

What was implemented:

  • Semantic versioning (currently at v0.1.4)
  • pyproject.toml as the single source of truth for version (commit b2a4a927)
  • Automated version badge updates in README
  • CHANGELOG.md for tracking changes
  • Tag-based releases using tinytorch-v* prefix

The versioning approach mirrors the book's system (book-v* tags) for consistency across the project.

<!-- gh-comment-id:3790246058 --> @profvjreddi commented on GitHub (Jan 23, 2026): This has been implemented! **Versioning system established in commit [858c762ca](https://github.com/harvard-edge/cs249r_book/commit/858c762ca)** (January 13, 2026). **What was implemented:** - Semantic versioning (currently at v0.1.4) - `pyproject.toml` as the single source of truth for version ([commit b2a4a927](https://github.com/harvard-edge/cs249r_book/commit/b2a4a9276)) - Automated version badge updates in README - CHANGELOG.md for tracking changes - Tag-based releases using `tinytorch-v*` prefix The versioning approach mirrors the book's system (`book-v*` tags) for consistency across the project.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/cs249r_book#1684