Lightning-AI/pytorch-lightning

Tagging discussion with release number

Open

#11,512 opened on Jan 17, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)Python (26,687 stars) (3,233 forks)batch import
docsfeaturehelp wanted

Description

🚀 Feature

It would be nice to have included (used or related) PL version to keep the context as it can easily happen that discussing some specific cases can vary significantly based on the used version...

Pitch

keep the topic/case tide with its related PL version

Alternatives

In some way, we can add a tag with the latest version to each newly created topic as it is most likely that the users are synced and if not we can mention it in the topic and we will adjust it manually accordingly... In a similar fasion, we can check the topic creating data and back assign the last PL version back then...

Additional context

cc @borda @rohitgr7

Contributor guide

Tech stack
python
Domain
documentation
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
This feature request suggests adding version tags to discussions in the repository. The implementation could involve manually adding a label like 'v1.8' or 'latest' when a topic is created. Alternatively, it could be automated with a GitHub Action that checks the creation date and assigns the corresponding release version. Check the repository's discussion templates and label settings for existing version tags. The issue has 4 comments that may contain further suggestions.