Bugzilla:Meetings
Bugzilla Meetings
When and where?
We hold meetings on the 4th Wednesday of every month at 14:00 UTC.
The next meeting will be on Wednesday, 27 August 2014, at 14:00 UTC (click for time in your timezone).
You can participate in the following ways:
Via IRC: server: irc.mozilla.org channel: #bugzilla
Mozilla Vidyo: in the Bugzilla room; if you don't have Mozilla LDAP access, use this guest link: https://v.mozilla.com/flex.html?roomdirect.html&key=kCjGNHjpT8sj
Air Mozilla: https://air.mozilla.org/bugzilla-development-meeting-20140723/
Telephone: +1 650 903 0800, x92 98008 or +1 800 707 2533, pin 369 - conf 98008
Minutes will be taken at https://etherpad.mozilla.org/bugzilla-meeting and transcribed to the wiki shortly after the meeting ends.
We will try to have someone acting as a moderator on the IRC channel to summarize the discussion on IRC for those who can't watch the stream and also to relay questions from IRC to the video call.
Who can attend?
Everyone interested in being actively involved in the Bugzilla project can attend. Project leads and core developers will be there, but we welcome anyone interested in contributing, whether it be to development, testing, planning, the website, or anything else. This is not a forum for support questions, however.
What will be discussed during our next meeting (agenda)?
Wednesday, 27 August 2014
- Summary of the last meeting.
- [glob] BMO would like to implement the following:
- add a "minor update" boolean to all places where a bug can be changed (show_bug, bulk_updates, attachments, API param, ...)
- if set, do not generate or send bugmail for that change
- this is a change of the current policy:
- The Bugzilla Team has shied away from creating this option because it puts the power of determining what's "important" in the hand of the person changing the bug, not the person receiving the email notification
- i'd prefer for this to be implemented upstream, but will make a bmo extension if the upstream policy is to remain
- [sgreen] Although I hate adding more params, I think there should be a param for this, so that site admins can determine whether they want this feature or not. An even better option is to have a param that takes a group as its input, and you need to be in that group to see this option. My concern is that newbies would use this option when making an important comment, and the developers (bug watchers) wouldn't be notified. Just like a can do on MoWiki.
- [dkl] Ideas on how to do upgrade automated testing using Travis CI. Hosting landfill dumps for Travis CI workers to download and import turned out be a bad idea and is no longer possible and so we need a new method.
- Maybe generate the test data systematically using a script for each version of the database being upgraded?
- Just use the blank database created by checksetup.pl, upgrade to new version and run checksetup.pl and just test schema updates and not worry about data migration?
- Add other items here.
Summaries of previous meetings
2014
2013
2012
2011
2010
2009
Tuesday, March 10th (50th IRC meeting)
2008
Tuesday, April 8th (40th IRC meeting)
2007
Tuesday, July 10th (30th IRC meeting)
2006
Thursday, February 2nd (our first IRC meeting!)
Tuesday, June 6th (10th IRC meeting)
Tuesday, October 31st (20th IRC meeting)