Re: [tdf-discuss] Re: Naming builds. Please???
On Thursday 08 December 2011 07:50, Marc Paré wrote:
Le 2011-12-07 12:58, Terrence Enger a écrit :
Presumably the implementation of whatever is chosen will
allow copying. The suggesion here is that we may get
easier-to-read reports by making it easy for people to copy
the same stuff the same way.
Why not just make it automatic by having a "Submit bug" button
somewhere and it would already fill in all of the identifying
fields without the user having to fill them out. This would make
sure the devs get the right information on the bug submissions all
the time and the button would be programmed right into the
software. Probably the best place to put it would be in the "About"
Traditionally i understand reporting a bug is not an easy one step
process. This to:
* Prevent frivolous bugs - "I can't find "File - Page Layout".
* Prevent duplications, which happen anyway partly due to many
terminologies that people employ. (Lost track of how often i've heard
people call a system box a hard drive).
Why not add this to "Insert - Field" as "Insert - Field - Program
Version" and "Insert - Field - ODF Version".
Unsubscribe instructions: E-mail to firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted
- Re: [tdf-discuss] Re: Naming builds. Please??? (continued)
Impressum (Legal Info)
: 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