Lightning-AI / Lightning-AI/pytorch-lightning
Tagging discussion with release number
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31.4k
- Forks
- 3.8k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 6
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
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by determining where new topics are created and how the related PL version could be obtained; done means newly created topics receive the appropriate version tag, with a defined approach for older topics and users on different versions.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100