[ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
[ < Bug Squad overview ] | [ Up : Issues ] | [ Bug Squad checklists > ] |
8.3 Bug Squad setup
We highly recommend that you configure your email to use effective sorting; this can reduce your workload immensely. The email folders names were chosen specifically to make them work if you sort your folders alphabetically.
- Read every section of this chapter, Issues.
- If you do not have one already, create a gmail account and send the email address to the Bug Meister.
-
Subscribe your gmail account to
bug-lilypond
. -
Configure your google code account:
-
Wait until your gmail account is listed in:
http://code.google.com/p/lilypond/people/list
-
Sign in to google code by clicking in the top-right corner of:
http://code.google.com/p/lilypond/issues/list
You cannot log on if you have Google Sharing enabled http://www.googlesharing.net/.
- Go to your “Profile”, and select “Settings”.
- Scroll down to “Issue change notification”, and make sure that you have selected “If I starred the issue”.
-
Wait until your gmail account is listed in:
-
Configure your email client:
-
Any email sent with your gmail address in the
To:
orCC:
fields should go to abug-answers
folder.When setting up your filtering rules, be aware that Google Code might use different versions of your email address, such as ones ending in
@googlemail.com
or@gmail.com
. -
Any other email either from, or CC’d to,
lilypond@googlecode.com
should go into a separate
bug-ignore
folder. Alternately, you may automatically delete these emails.You will not read these emails as part of your Bug Squad duties. If you are curious, go ahead and read them later, but it does not count as Bug Squad work.
-
Any other email sent to (or CC’d to):
bug-lilypond
should go into a separate
bug-current
folder.
-
Any email sent with your gmail address in the
[ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
[ < Bug Squad overview ] | [ Up : Issues ] | [ Bug Squad checklists > ] |