Retarget the progress bar to GZDoom 2.1.1 - #202
Merged
Merged
Conversation
2.0.05 is done: 1179 of 1179. The bar now measures against 2.1.1 (2016-02-23), which puts us at 1300 of 2980, 43.6%. 2.1.1 rather than jumping to 2.3 because it lands the sim where the renderer staircase already stopped (db766f9fe, 2016-02-03) and near the Cocoa backend target (108dcf122, 2016-09). Aiming past it would leave the sim, the renderer and the platform layer at three different points in upstream history, which is the divergence the staircase doc exists to prevent. Also records where ZScript actually begins, since the VM landing in Dec 2014 makes that easy to get wrong. The language arrives at 433bf4601 (2016-10-13), the commit that converts inventory/player/specialspot to ZSCRIPT and drops them from the DECORATE include list. g2.3pre does not contain it, g2.4pre does -- so GZDoom 2.4 is the first release with ZScript, and 2.3 is the wall. The site needed no change: index.html renders every figure from progress.json, so retargeting is progress.sh plus a re-run.
rc4l
enabled auto-merge
August 5, 2026 01:42
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
2.0.05 is done — 1179 of 1179. The bar now measures against 2.1.1 (2016-02-23): 1300 of 2980, 43.6%.
Why 2.1.1 and not 2.3
2.1.1 lands the sim where the renderer staircase already stopped (
db766f9fe, 2016-02-03) and near the Cocoa backend target (108dcf122, 2016-09). Aiming past it would leave the sim, the renderer and the platform layer at three different points in upstream history — the divergencedocs/renderer-staircase.mdexists to prevent.Where ZScript actually begins
Worth recording, because the VM landing in Dec 2014 makes this easy to get wrong. The VM is only infrastructure; the ZScript language arrives at
433bf4601(2016-10-13) — the commit that convertsinventory.txt/player.txt/specialspot.txtto ZSCRIPT and drops them from the DECORATE include list. Ancestry check:g2.3predoes not contain it,g2.4predoes.So GZDoom 2.4 is the first release with ZScript, and 2.3 (2016-09-19) is the last one without — that's the wall, and the target after this one.
Site
No change needed.
commit-tracker/index.htmlrenders every figure fromprogress.json, so retargeting isprogress.shplus a re-run.