| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Add initial support for testing fix patches.
A user on mailing list can request patch testing with:
and attach a patch.
|
| |
|
|
|
| |
Namespace can be used for some customization
in external reporter.
|
| |
|
|
|
|
|
|
| |
Provide better errors from bug update command.
In particular, distinguish between bad updates and internal errors.
Also better messages.
Allow duping onto closed bugs.
Don't allow unduping from closed bugs.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- save Message-ID and use In-Reply-To in subsequent messages
- remember additional CC entries added manually
- don't mail to maintainers if maintainers list is empty
- improve mail formatting and add a footer
- implement upstream/fix/dup/invalid commands over email
- add tests
|
| |
|
|
|
|
|
| |
Detect when we send first/non-first email for a bug.
Detect when we send moderation/non-moderation email for a bug.
Fix setting repro level in email reports.
Add end-to-end email reporting tests.
|
| |
|
|
|
|
| |
Managers can't decide when a repro is required.
First, there can be bugs with seq>0.
Second, a repro can be already obtained on another manager.
|
| | |
|
| |
|
|
|
|
|
|
| |
json decoding behavior is somewhat surprising
(see // https://github.com/golang/go/issues/21092).
This behavior is especially easy to hit in tests
that reuse reply objects.
To avoid any surprises, we zero the reply.
|
| | |
|
| |
|
|
| |
We already have manager name in Build and Crash references Build.
|
| |
|
|
|
| |
Query is useful for tests and other contexts
where non-standard request creation/sending is necessary.
|
| |
|
|
|
|
| |
1. Add manager name to builds.
2. Add centralized logging.
3. Add types for bug reports and bug updates.
|
| |
|
