Issue #11076 has been updated by Daniel Pittman. Category set to error reporting Status changed from Unreviewed to Needs Decision Assignee set to Nigel Kersten
Nigel, it sounds like we have general consensus that this is the right path; can you, in your product hat, make the final call and advance the ticket to the appropriate state. Presumably also schedule someone to get the work done or whatever. ---------------------------------------- Feature #11076: Error messages should all have a unique identifier https://projects.puppetlabs.com/issues/11076 Author: Nigel Kersten Status: Needs Decision Priority: Normal Assignee: Nigel Kersten Category: error reporting Target version: Affected Puppet version: Keywords: Branch: It's difficult to search for phrases when trying to work out what has provoked a given error message. Something IBM did quite awesomely was to have unique identifiers for their error messages so that you could more easily search for information on them. I'm not suggesting we abandon providing a human-readable phrase explaining the error in context, but that we instead append a unique identifier of some kind so that we can more easily provide significantly more detail in our documentation around errors. Love to get feedback on this idea, particularly from docs and UX. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
