A little note for the updates ?

[samo79]

Any new (OS) update is already released with a proper changelog (visible clicking into the "Info" button of AmiUpdate), but as many people always forgot to read it (or just like to read it later) how about adding also a small readme file into the LhA file containing the same changelog parts ?

I think it would be better, more user friendly and even more professional for certain aspect

[kicko]

That would be good to have. I also forget what the changes were after download. So difficult to tell friends that asks whats new etc.

[samo79]

Yep, as changelogs of the various updates finally become visible i really can't see the reason to not add also a small readme

[kas1e]

@Samo79
Problem is: you download new archive, it containt inside "release_notes". Where they all should be placed ? Create some new volume on system parition just to collect release notes ? Or just do not install them, and only put in arhive ? Then, if anyone will install it, reboot, and do not save archive, no release notes at all as well.

[kicko]

@kas1e

In the rollback drawer where all updates are. For example in 4-12-2012 is amiupdate 2.23. Could be a file with the info log for it. No need to have some special drawer for smaller changelogs. The same info that you get when checking the info button before downloading an update. But this will not happen. It was just an idea.

[samo79]

@Samo79
Problem is: you download new archive, it containt inside "release_notes". Where they all should be placed ? Create some new volume on system parition just to collect release notes ? Or just do not install them, and only put in arhive ? Then, if anyone will install it, reboot, and do not save archive, no release notes at all as well.

Yes Roman, as Kicko correctly say we may put all into rollback drawer (better choice imho), or in alternative the changelogs files can be copied in SYS:Documentation (the correct place for all docs/text files in general)
Also as latest option we can always leave them inside their original archives and nothing else, many people tend to do a proper backup also for the single updates they download (for example i do that anytime a new archive comes to AmiUpdate) and so on .. possibilities still

[HKvalhe]

It surely would be nice to have a note about the updates of AmigaOS components, what the changes are, what the current version of them are and a short but easy explanation of what they are and do. Would be very helpful, and i agree with Krister's suggestion.

[kas1e]

@samo79

we may put all into rollback drawer

But rollback driver its for rollback stuff. Will be a bit unlogical to say "hey, we have all release notes in rollback driver". Will be imho unlogical and messy.

or in alternative the changelogs files can be copied in SYS:Documentation (the correct place for all docs/text files in general)

That one imho better, right. Something like SYS:Documentation/ReleaseNotes/ , and there just put all release notes from all the programms.

Also as latest option we can always leave them inside their original archives and nothing else, many people tend to do a proper backup also for the single updates they download (for example i do that anytime a new archive comes to AmiUpdate)

That one no-go as well, because users will scream later that "we want to see release notes, where they are ? deleted after installing ? blah !".

Imho, SYS:Documentation/ReleaseNotes/ are fine enough. Just now need to convince somehow SSolie and others to do that, and then almost all adequate users wish will be done

[samo79]

@kas1e

Ok. then let's go with the "SYS:Documentation/ReleaseNotes/" path

[samo79]

From latest AmiUpdate 2.31 changelog:

- Added some substantial new functionality. The user now has the option to save the extended information of each update, which is usually used for release information. This works on a server-by-server basis, and is set within the preferences editor. Open the preferences editor and go to the "Servers" tab. A new column has been added to show whether the release information from each server should be saved or not. The feature can be toggled by selecting the server and clicking "Edit". Once enabled, the release information will be saved in the SYS:Documentation/ReleaseInfo drawer. A file will be created for each unique update, and the information will be saved into it under a heading denoting the version and the date of this update. The file will be named after the package name, so all release information will be collected in one file for each package. For example, each update of "Kernel" will be saved into a file called "SYS:Documentation/ReleaseInfo/Kernel_release_info". Each version will have a separate section within this file showing the information for each release.

Thanks Rigo !