[HAVE REVIEW] Tinderbox should use notice for tree state changes

RESOLVED FIXED in 2.4

Status

Webtools
Mozbot
--
enhancement
RESOLVED FIXED
17 years ago
12 years ago

People

(Reporter: Hixie (not reading bugmail), Assigned: Hixie (not reading bugmail))

Tracking

other
Other
Other

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

17 years ago
From the wishlist: 

<timeless> use /notify for tree state changes

Really? Why?

Comment 1

17 years ago
people would like to be able to ignore channel banter but receive channel 
notifies from the bot warning about horkage, greenage, opening and closing.
(Assignee)

Comment 2

17 years ago
Fair enough. Will require an upgrade to the mozbot API to support /notify.
New QA.
QA Contact: matty → timeless
(Assignee)

Updated

16 years ago
Whiteboard: 2.2
(Assignee)

Updated

16 years ago
Target Milestone: --- → Mozbot 2.4
(Assignee)

Comment 4

16 years ago
Created attachment 75837 [details] [diff] [review]
Patch: Version 1

Adds a notice() method to the mozbot API. Updates the documentation to reflect
this. (Also updates the version and corrects a typo in the docs.) Changes
Tinderbox to use either say or notify, configurable via the 'useNotice'
variable.
(Assignee)

Updated

16 years ago
Status: NEW → ASSIGNED
Keywords: review
Summary: Tinderbox should use /notify for tree state changes → [HAVE FIX] Tinderbox should use /notify for tree state changes
Whiteboard: 2.2

Updated

16 years ago
QA Contact: timeless → timeless
Summary: [HAVE FIX] Tinderbox should use /notify for tree state changes → [HAVE FIX] Tinderbox should use notice for tree state changes

Updated

16 years ago
Attachment #75837 - Flags: review+

Updated

16 years ago
QA Contact: timeless → kerz
(Assignee)

Comment 5

16 years ago
r=timeless
Keywords: review
Summary: [HAVE FIX] Tinderbox should use notice for tree state changes → [HAVE REVIEW] Tinderbox should use notice for tree state changes
(Assignee)

Comment 6

16 years ago
Checked in.
Status: ASSIGNED → RESOLVED
Last Resolved: 16 years ago
Resolution: --- → FIXED
QA Contact: kerz → mozbot
You need to log in before you can comment on or make changes to this bug.