Robert Collins has proposed merging lp:~lifeless/python-oops/docs into lp:python-oops.
Requested reviews: Launchpad code reviewers (launchpad-reviewers) For more details, see: https://code.launchpad.net/~lifeless/python-oops/docs/+merge/77849 The reporter key needed some clarifications, so I have done so. Not worth doing a release for just this update. -- https://code.launchpad.net/~lifeless/python-oops/docs/+merge/77849 Your team Launchpad code reviewers is requested to review the proposed merge of lp:~lifeless/python-oops/docs into lp:python-oops.
=== modified file 'oops/config.py' --- oops/config.py 2011-09-18 22:36:02 +0000 +++ oops/config.py 2011-10-03 00:34:22 +0000 @@ -64,8 +64,13 @@ was triggered. * revno: The revision that the branch was at. * reporter: Describes the program creating the report. For instance you might - put the name of the program, or its website - as long as its distint from - other reporters. + put the name of the program, or its website - as long as its distinct from + other reporters being sent to a single analysis server. For dynamically + scaled services with multiple instances, the reporter will usually be the + same for a single set of identical instances. e.g. all the instances in one + Amazon EC2 availability zone might be given the same reporter. Differentiated + backend services for the same front end site would usually get different + reporters as well. (e.g. auth, cache, render, ...) * topic: The subject or context for the report. With a command line tool you might put the subcommand here, with a web site you might put the template (as opposed to the url). This is used as a weak correlation hint: reports from the
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-reviewers Post to : [email protected] Unsubscribe : https://launchpad.net/~launchpad-reviewers More help : https://help.launchpad.net/ListHelp
