Skip to content

Changed from previous lockpick versioning scheme to be more flexible (and match with atmosphere).#7

Open
auggeythecat wants to merge 1 commit into
impeeza:masterfrom
auggeythecat:master
Open

Changed from previous lockpick versioning scheme to be more flexible (and match with atmosphere).#7
auggeythecat wants to merge 1 commit into
impeeza:masterfrom
auggeythecat:master

Conversation

@auggeythecat

Copy link
Copy Markdown

The reason this is needed, is because there are currently 3 'mainstream' (aka, widely used) distributions of LockpickRCM.

Due to various bug fixes, and similar things, one of them is on 1.9.18, (which is mostest correctest), one is 1.9.19, and one is 1.9.20. These all support a maximum of 22.x.x, but based on the established naming convention, the latter two would be 23.x.x and 24.x.x respectively. It is becoming difficult to point people to it properly, and I see this getting much harder in future updates. So, I suggest we fix this now, so we don't have to deal with it later.

With the new suggestion, major and minor version would correspond to the major and minor versions of the corresponding atmosphere release, and bugfx would be for, well, bug fixes. This way it could just be referred to as, for example, 1.12.x and it would be accurate for any repo, (no matter how many bug fixes).

The three repos that this change is being pr'ed to, are as follows: https://github.com/impeeza/Lockpick_RCMDecScots, https://github.com/kofysh/Lockpick_RCM, and https://github.com/THZoria/Lockpick_RCMaster.

Thanks!

…oom for non-firmware/key derivation related updates. Aka, bug fixes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant