Repository navigation
Replies: 2 comments 1 reply
|
Where was the decision finalized, by chance? |
1 reply
|
Whilst I do like this idea, this opens the doors for maintainability hell: How do you ensure commits to one branch, are reflected on the others? Ie.: your current documentation efforts (Which by the way -- you've been on fire as of late) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
(This follows the discussion started here: #160)
We've decided to move the official revisions of Sonic 1 to individual branches, rather than having them all be part of the same one and be controlled by a build flag. This is to make the source code less cluttered with if-else conditions, which are annoying to read and work with when making ROM hacks.
The question is how exactly we want this to be done. Copying what I've said in my original comment, here's what I've been proposing:
Clownacy has mentioned concerns about REVXB getting dropped entirely, so I guess this is where we more discussion is necessary. I still think it's pretty redundant to keep an entire branch for one tiny, poorly-implemented spike bug fix, but I can see the explanation of it being technically official as valid.
I'm still open for thoughts, though.
All reactions