Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
calendar/lightning bug reports
11 views
Skip to first unread message
Wayne
Feb 11, 2013, 10:50:25 PM2/11/13
to mozilla-supp...@lists.mozilla.org
I recently triaged thunderbird product bugs to make sure no calendar
bugs were there. Then I took a look at product=calendar bugs, and
surprised to see over 500 unconfirmed, and ~25 higher severity that have
no activity in past year.
Anyone interested in joining a calendar bugday, to clean a few of these,
with assistance of others?
Cheers
W.
bugs were there. Then I took a look at product=calendar bugs, and
surprised to see over 500 unconfirmed, and ~25 higher severity that have
no activity in past year.
Anyone interested in joining a calendar bugday, to clean a few of these,
with assistance of others?
Cheers
W.
Bill Braun
Feb 11, 2013, 11:51:45 PM2/11/13
to
Bill
Philipp Kewisch
Feb 12, 2013, 6:30:04 AM2/12/13
to
Hey Wayne,
I would be delighted if you could organizer a bugday like this! If you
want me to put up a blog post, just send me the text and I'll post it.
Email me with more info if you need anything.
Bill: All you will need is a copy of the nightly thunderbird and
lightning builds. The process is usually to go through the bugs, try to
reproduce them and then decide if its really a bug (you also get that
error) or a support issue (it works for you, the user might not have
something set up correctly). Also, for bugs with little information ("it
doesn't work."), ask for more information like error console messages, etc.
More complete instructions will be available when a bugday starts.
Regards,
Philipp
I would be delighted if you could organizer a bugday like this! If you
want me to put up a blog post, just send me the text and I'll post it.
Email me with more info if you need anything.
Bill: All you will need is a copy of the nightly thunderbird and
lightning builds. The process is usually to go through the bugs, try to
reproduce them and then decide if its really a bug (you also get that
error) or a support issue (it works for you, the user might not have
something set up correctly). Also, for bugs with little information ("it
doesn't work."), ask for more information like error console messages, etc.
More complete instructions will be available when a bugday starts.
Regards,
Philipp
0 new messages