Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Gentlemen and Ladies,

 I have a madly insane idea - when bug fixes/updates are applied to a
project - simply HIDE or REMOVE the unpatched version from the end user's
accessible locations.

I know that  the UNPATCHED version needs to remain, for rollbacks or other
badly done "updates" but, for heaven's sake if you insist on keeping the
unpatched version, call it "PackageName - Unpatched" or better yet give the
patched version a new name.

For, example: LibreOffice1 (the original version) LibreOffice1.1 (an updated
version) and finally, (LibreOffice1.1.1 -the version with all the latest
bug-fixes, enhancements, etc.).

When other platforms are also supported: refer to the program by appending
the name of the platform to the package name, i.e LibreOffice1.1.1 for
Android LibreOffice1.1 for Windows, etc.





--
View this message in context: 
http://nabble.documentfoundation.org/LibreOffice-Still-tp4117297p4125025.html
Sent from the Users mailing list archive at Nabble.com.

-- 
To unsubscribe e-mail to: users+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.