These are chat archives for UltraStar-Deluxe/USDX
you are currently the only one who still knows what all your issues are for
i mostly describe if the title doesn't state what the issue is all about.
anyways if you are going to fix an issue, please assign yourself to it so other devs know not to spend time on that
i already do so.
regarding #78 , I'd suggest not having a plaintext readme as that will be additional work to keep it current and nowadays everyone can browse a website or read formatted .md
or the pdf
it's for the actual game. and yes, that would be a bit more work. but not that much. the readme can be the documantation. the README.md does have to state everything important for the deveoploment (such as guidelines etc., notes, abouts, how-tos).
for #77 , all files that are available are in the git repositories somewhere. as far as I know none of the active developers has any additonal files.
too bad. i hope we can get into contact with the original authors someday, somewhen
regarding #75 , I have no idea how to react to this. not enough information. if you are in doubt regarding that, use a pull request and another dev will take a look and answer
it'S the aggregated (:wink:) issue for everything related to the big merge commit. i've sceen alot of things are removed without even mentioning why, and some things were violating the license. that issue is used as blacklog for checking what things have to be reverted and what things should stay "changed". the issue is also created to have a discussion related to that specific topic /changes. it's not possible to create a PR for such complex merge, it would be a big chunk of code, or changes. Some things covering that problem were already changed with the recent commit regarding the installer files.
ok, then there is your decision. do it :grinning: ("Giddy-Up")
the "VERSION" would be more for the codebase, but if it should exist already before the next release, I could add it as milestone issue
a branch should be used
yep. but branching isn't that good in git, therefore non conflciting, good and stable changes could be done to the master, and keep the branch on par/up-to-date