The first question is general one, and fundamental with all updates: all the information in every update, about new features and changes given to users in very simply, plain, and i can say "dumb-mode", while almost all amiga users today advanced ones, and aware about all the bugs which they want to see fixed. Of course, some amiga users still "casual ones" (less and less, but they still present) , and for them, simple-change-log are fine, but much more users prefer detailed change-log and updates descriprion.
As i see it , it should (well, should bad word here, let's change it on "will be good") go in 2 ways:
1. simple/dumb-mode as it now for public newses/sites/information/etc.
2. readme with details change log about every changed and updated component somethere in the root of ISO or arhive (btw, there is one more moment: better to release just full ISOs imho, its debatable of course,but installing update1, then 2, and then 3, its a bit mess. Full clean ISO are better for sure).
If you all not want to bother with it, will be just cool to cut+paste all the bug-zilla "fixed"/"changed"/"added" entrys to that file. So, advanced users, programmers and all will know what was fixed exactly (from what they reported), what not fixed, what they can test to see if it fixed, and what was added or not.
3. for all the new files releases with update, add documentation about what was changed / fixed / added since last update/release. Because for example, i see new notepad in update3. But do not know what changes in it, so i maybe miss someting good. the same for other bins and libs.
I see there nothing hard to put that files into updates, and major os releases , it will be not hard work , and will be very-very good for users to see how all of this was fixed, who fix it (and even try to send mesages to authors of fix, without worring about who works on what and so on).
I am sure, almost all the users will say "yes, it will be cool", to have 2 change logs: one are simply one as it now, and one detailed one, just copy+paste from bugzilla, or even a bit "manually changed". Just take a look as Thore do for MUI. Something like this for every component are very good to have. Its all debatable of course, all what is important : if os4devs want to do it, to make os4 better.
@Ssolie
You are new team-lead now, and as i see you want to make better communication with end users, so, maybe that a change to make all better in that terms ? Through, after i read how you answer to users in some threads here, i fear you can just lock that thread as well
The next question is exactly about update3 and detailed change log (you can see, how bad to not have detailed change log for advanced users, and even for plain users as well). Let's begin (and even, if it just example of how its all unclear, will be cool if devs will also answer on my example questions too):
What exactly updated ? Its just bug-fixed or something new added ? If fixed, then which bugs exactly, if something new added, then what ?Updated Installation Utility program;
How they updated ? Bug-fixing or new features? Which ones ? Did they works now faster or slower, better or worse ? Did they all works fully as driver should, with all that fast speed tricks, dmas or whatever else ? Was there added something very good lately beetwen update2 and update3 ?Updated PATA and SATA drivers;
Which issues exactly ?Fixed Amiga shared object issues;
What exactly was updated, and which gui components ?Updated Intuition and GUI components;
What did it mean, and how we can use it , and how good or bad its for end users ?New consistent full release string including update number;
What exactly was fixed and what exactly was impoved ? I know only that Hans improve out-of-memory corruption, and that Karlos add some fixes, but nothing detailed and nothing more about other fixes and updates.Updated and improved Warp3D support;
How it done ? For what machines ? I know that only for sam series Maxx add DMA support for rtg.library, but not for pegasos2 / a1 and others. Or did dma works for all machines now ? Or did faster 2d graphics support mean something else, like better WritePixelArray() itself, or some other functions of P96 ?Faster 2D graphics support;
That is very interesting: what was fixed exactly. Was elf.library.kmod (let's think that its' kernel related) fixed in terms of bug which i report before, and was all fixed in terms of bugs which Alfkil report ? I know you will say "which bugs?" , but the same i say "how can i check my bugs was they fixed or not, if we have no detailed change-log".Various kernel fixes for increased stability;
Knowing how much work Thore spend on it, and how much was added, its all can't be so simplified. Its all was fixed a lot, hundreds of bugs was fixed, tons of new features was added, and its all not only about porting, but just in general. Good that in case with mui, we have what we need : real change_log with all the information we need.Updated MUI with many new features to make porting MUI 4.0 based applications simpler;
How it was impoved ? In which areas ? Just bug-fixing or what ?Improved notifications support.
Now you can see how all of this "too-simply", and just make problems for advanced users.
I hope that os4devs will understand how all of this important, and will not say something like "users should not know about it". If you want to make aos4 better, then we all should aware about best of all for devs, users and customers. Hope that topic will make any sense
