Paul Scott wrote: > you are expected to download the whole thing again?
Yes. > Also, there are no hints given for updating as opposed to a new install Because the way to update is to do a complete install. > What it needs: (some are desperately needed, some are improvements) > > - A specific 'How to update' landing page That page would contain one line: "To update, download and install the new version of OOo." > - A better way of showing 'what's changed' than Release notes just > referencing bug numbers Would you rather that the entire bug report was cut and pasted there? Or are you advocating that people be unable to figure out which items in issuezilla have been fixed/included in the version of OOo that is being released? > but for now there's at least one user who hasn't got the latest security > upodates and bugfixes applied, and I'd bet there's a whole lot more out a) IIRC, only two versions of OOo have had security patches released for them. In both instances, "patched" versions of OOo were available for downloading whilst those patches were on the website. b) Patch upgrades can only go so far. One major issue in creating patches, is that certain assumptions are made about the build to be patched against. If, for whatever reason, a different build was used for the version of OOo that you installed, you just rendered that software useless. > Updating (software *and* process) is something it's worth spending some time > on.. And what do you think the difference between OOo 2.0.3 and OOo 2.0.4 is? xan jonathon --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
