[ << Issues ] | [Top][Contents][Index][ ? ] | [ Regression tests >> ] | ||
[ < Introduction to issues ] | [ Up : Issues ] | [ Bug Squad checklists > ] |
7.2 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.
- Skim through every section of this chapter, Issues. Read in detail any sections called “Bug Squad...”, or any page linked from Bug Squad checklists.
- 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:
-
Sign in to google code by clicking in the top-right corner of:
http://code.google.com/p/lilypond/issues/list
- 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”.
-
Sign in to google code by clicking in the top-right corner of:
-
Configure your email client:
-
Any email sent with your gmail address in the
To:
orCC:
fields should go to abug-answers
folder. -
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 >> ] | ||
[ < Introduction to issues ] | [ Up : Issues ] | [ Bug Squad checklists > ] |