I don't understand that argument.
But what argument you else need, if developers ask for some readme/changelog file, where will be noted what was changed (at least key-features and major changes). They want to know it without loosing hours to find out it .. that imho pretty obvious and no need arguments.. Some text file, something like i note in previous post, and which Trixie update later (and we for sure and 100% miss something , which we not know, and which no one will know, and which no one will remember to recheck if he have problems back in the past). You are wrong if you think that no one will read it, change logs and release notes reads everyone who want to know what happens since last release. Its good that we at least add release_info driver for updates, but SDK shouldn't be exception, there also need to have something like this. Its just will make live of 3d party developers easy, and to make such a readme only few hours need it (i can help with it with no problems when time for new SDK come).I.e. you want 3d party developers who want to do something in their spare time, to grab previous SDK, new SDK, and sit hours and compare manually dates, do diffs, check sizes, loose countless hours just to find out what and where was changed ? Imho that not very good. For us (who know what was changed), it will take just a few hours to do such a file, and we will save hours of productivity of 3d party devs.A diff is 100% accurate.
Of course, notice every single change will be hard for , but key-changes readme are must if we want to make life of 3d party developers easy. I.e. , until i with Trixie not post that info, who ever know what was changed except some smarties who check dates of archives ? Why they should download new SDK on top of old one, if they do not know what was changed ? I mean, its really obvious that with each SDK release there should come "what_new.txt", or something like this, where we can (at least briefly) note what was changed, updated and co. There will be no needs to write any single change in every autodoc and will be enough to say "fixed bucnh of typos in autdocs", but such a "big" updates like fresh mui includes, new dos sdk, new kernel functions and so on are 100% and must be noted, so developers will know what new they can do, without random guess work and loosing hours of time , which they can spend on actual coding with usage of new stuff. Better we will spend few hours one time, in compare that every 3d party developer will do the same and in sum we will have less hours of productivity.
Some note like "that is not full list of changes, we just describe major ones", can be added to the end of readme file, so ppls will know that there not everything noted, just some major moments.Anything a human tells you would be a lie to some degree because they will omit things.
