Attendees

• David Lawrence (dkl)
• David Miller (justdave)
• Gervase Markham (gerv)
• Reed Loden (reed)

Agenda

• Where do we stand with 4.0?
• Document current Bugzilla layout both testing/staging/production
• Document current Bugzilla release process:
  • What steps are taken to push a new code update live?
  • How often is b.m.o updated?
  • When is it considered well tested and ready to go?
  • Who signs off and performs the actual push?
• How do we currently prioritize the features/fixes that Mozilla developers ask to be added to b.m.o and how are they categorized?
• Anything else we can think of.

Meeting Notes

Where do we stand with 4.0?

Update from Gerv: I'm most of the way through a rewrite/port of changes, turning them into an extension and a few small hook patches. It's been on hold for the past couple of weeks while I've been in the USA but I plan to take it up again soon.

• New extension called BMO to contain most customized code.
• Some small changes remain in the core Bugzilla code.

Action items:

• gerv: Check current work into bmo/4.0 repository for review (done)
• dkl: Work with gerv and justdave to come up with a schedule for release as well as a plan for testing and milestones (in progress)

Document current Bugzilla layout both testing/staging/production

• Staging server used for internal/external testing of new b.m.o code before release
• https://bugzilla-stage-tip.mozilla.org

Action items:

• dkl: Update internal Bugzilla wiki on intranet with project information related to b.m.o. Anything sensitive or specific to b.m.o will go on the internal intranet, where anything that can be consumed publicly will reside on http://wiki.mozilla.org/BMO (in progress)
• justdave: Add a description of the current topology for the b.m.o production environment to internal Bugzilla wiki (in progress)

Document current Bugzilla release process

• Staging server used to test release before being pushed to production.
• Updated during normal operations downtimes on Tuesday and Thursday nights.
• When schema changes are needed, the site is taken down fully, otherwise code pushes do not require disabling site.
• Using custom scripts that rely currently on specific tags in the Bazaar repository.

Action items:

• dkl: Document testing procedure and sign off for any scheduled update (in progress)
• justdave: Document current release process (done)
• jusdave will be performing production pushes as needed going forward.

How do we currently prioritize the features/fixes that Mozilla developers ask to be added to b.m.o and how are they categorized?

• There is a product/component for bugs/requests related specifically to b.m.o

https://bugzilla.mozilla.org/buglist.cgi?bug_status=__open__&component=Bugzilla%3A%20Other%20b.m.o%20Issues&product=mozilla.org

• Also features that are reported against the upstream Bugzilla product will have a [wanted-bmo] keyword added if the feature is determined to be useful for b.m.o

Action items:

• dkl: Create a current feature list table on the publicly facing BMO wiki listing the things being actively worked on. Also label the priority level and possible date of completion (in progress)
• dkl: Schedule a meeting of the Bugzilla minds to triage the currently open bug list to weed it down to a manageable level (in progress)