Replies: 7 comments
-
Note This discussion is related from #60 |
Beta Was this translation helpful? Give feedback.
-
I think we'll need at least the following:
I think things we should discuss here would be:
There is probably more, let me know. |
Beta Was this translation helpful? Give feedback.
-
There are several ways of doing this.... however I think that the easiest one is to use "repo" in |
Beta Was this translation helpful? Give feedback.
-
Yeah, agreed. Using pspdev/pspdev to do releases from makes sense. |
Beta Was this translation helpful? Give feedback.
-
I've created the following PRs to clean up the tagging up system that we currently have that just isn't working. With these changes we can just tag pspdev and be done with it. We would still like to introduce tracking the version of the underlying repos that were used like discussed here, but that I haven't gotten to yet. The PRs:
|
Beta Was this translation helpful? Give feedback.
-
Okay, I think I found out how I can add some basic versioning information, but I'm still experimenting with it. Basically, I would like to add the following line to each repo:
Which results in a line like this:
So, name, commit hash, commit date. For this change I would need to add |
Beta Was this translation helpful? Give feedback.
-
I've created some PRs to add lines to the build information file:
I'm still working on figuring out how to do this for pspsdk. Do we even care about psp-packages? Technically users can just use pacman to update. |
Beta Was this translation helpful? Give feedback.
-
After having some discussions started here:
https://discord.com/channels/479828644970364928/693948645145575434/1232366213779427440
Most of the toolchain developers have agreed that improving our Tagging and Release process could help end developers to identify breaking changes and improvements.
Please continue this discussion here and let's try to define a proper plan together.
Cheers.
Beta Was this translation helpful? Give feedback.
All reactions