Proposal to adopt new Versioning Scheme #60
Replies: 6 comments
-
I think it's a good idea to have some versioning which changes with new builds. I feel it should be automatic, though, not manual. I would propose to use the current date or the commit number. |
Beta Was this translation helpful? Give feedback.
-
Using the commit number solely takes away the ease of understanding I suggested being present in situations such as determining which documentation page is up to date. It also isn't standardized on its own, which is probably important we make an effort into doing and why I suggested SemVer. We can be SemVer compliant while using both the build date and version number, however. This can easily be automated via Actions. |
Beta Was this translation helpful? Give feedback.
-
I'm not sure semantic versioning makes much sense as the API is just Sony's and there won't be breaking changes or much evolution (except additions). I think the build date (or 1.0-date) would be nice. |
Beta Was this translation helpful? Give feedback.
-
This isn't true though, breaking changes have occurred, notably when the SDK became more POSIX compliant — There are also a lot of features the SDK sorta shoves together like |
Beta Was this translation helpful? Give feedback.
-
Is this something that has been considered? It's been almost a year since this was brought up initially. What's the status so far on this being implemented? |
Beta Was this translation helpful? Give feedback.
-
Hello guys! I will transfer this to the pspdev repo and then convert it into a discussion. Feel free to continue. |
Beta Was this translation helpful? Give feedback.
-
Since its initial commit to this GitHub repository in Oct 2010, the reported SDK version has been
1.0+beta2
. This is despite significant changes having been made the last decade to justify, at the very least, a versioning bump.As opposed to a version bump however, changing the scheme may be better suited. Semantic Versioning comes immediately to mind as it has become a standard in software as of recent. SemVer allows for easily reporting the SDK build date, which would be ideal for better specifying SDK versions while still maintaining the original 1.0 beta2 status (if absolutely necessary).
An immediate use case for this would be to have our Doxygen documentation better be identified as the actively maintained one (as opposed to http://psp.jim.sh/pspsdk-doc/) by seeing a date printed on the header and at the landing page instead of identifying it from the small font footer.
Would love to have a discussion about this here, looking forward to a response.
Beta Was this translation helpful? Give feedback.
All reactions