tronprotocol / tronprotocol/java-tron
Tracking: prepare and manage release_v4.8.3 branch
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.2k
- Forks
- 1.7k
- Avg merge
- 6d 20h
- Merged PRs (30d)
- 14
Description
This issue is to coordinate the creation and tracking of the release_v4.8.3 branch from develop.
Branch Details
- Version:
v4.8.3 - Branch to create:
release_v4.8.3 - Base branch:
develop
Tasks
- Create
release_v4.8.3branch fromdevelop - Push final PRs to
release_v4.8.3(e.g., version bump, changelog, fixes, features) - Perform QA and testing on
release_v4.8.3 - Merge
release_v4.8.3back tomasterwhen testing is complete - Tag
GreatVoyage-v4.8.3(Ockham)onmasterand release - Merge
masterback todevelop(if applicable)
Notes
Once the release_v4.8.3 branch is created, it will act as the staging area for all final updates and fixes for this release.
Any non-release-related changes should continue in develop.
Release date
The release is targeted for end of November
PRs
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
Start by reviewing the repository's current branch and release workflow, then track creation of release_v4.8.3 from develop. Follow the listed release PRs, QA, merge, and tagging steps; the work is done when the release is merged to master, tagged GreatVoyage-v4.8.3(Ockham), and master is reconciled with develop if needed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100