TODO: Add incremental patches.
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, release
Research direction
Start by inspecting how MCPConfig currently stores and applies snapshot patch files; the issue does not name a file, entry point, or test. Define completion around applying the nearest suitable incremental patch while walking backward through project versions, treating a zero-size file as a removed patch, and preserving bulk MCPConfig release generation.
Written by the indexing model from the issue text.
Description
We're thinking about snapshots.
It occurs to us that, since snapshots are typically rather small incremental updates, it makes no sense to have all the patch files duplicated and practically identical across all versions leading up to a major release.
Take for example, the difference between 1.19-pre1 and 1.19-rc2. There were only about 60 files out of 188 that had changed between these versions, and most of those were simply line bumps. (another issue is incoming related to that)
What we'd like is some sort of incremental system, where the patch application process would start in the current project folder and walk backwards until it finds a suitable patch file to use.
A suitable file with size 0 will represent a removed patch, in case Mojang delete a file or so.
This will clean up the repo greatly, and aid in the process of creating bulk MCPConfig releases for snapshots.
- Dominant language
- Java
- Stars
- 247
- Forks
- 84
- PR merge metrics
- No merged PRs in 30d
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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.
More from MinecraftForge/MCPConfig
-
type: enhancement
Difficulty 5/5 Over a week Newbie friendliness 25/100
MinecraftForge/MCPConfig#172 ·
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
MinecraftForge/MCPConfig#168 ·
All issues in MinecraftForge/MCPConfig
Similar issues
-
P2 testing
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
area/core kind/bug status/triage team/core-shared
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
checkstyle/checkstyle#21755 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
spring-projects/spring-integration#11495 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day