Bugzilla:Meetings: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
== What will be discussed during this first meeting (agenda)? == | == What will be discussed during this first meeting (agenda)? == | ||
* First of all, the approval of the actual roadmap by the core developer team. | * First of all, the approval of the actual [[Bugzilla:Roadmap | roadmap]] by the core developer team. | ||
* Each assigned developer for a given task will be asked to inform us if they accept their role or not, and if yes, whether the deadline actually set seems reasonable. | * Each assigned developer for a given task will be asked to inform us if they accept their role or not, and if yes, whether the deadline actually set seems reasonable. | ||
* Update and validate the roadmap based on the previous point. This includes adding missing stuff, if any, and removing what we think won't be ready on time or which is finally considered as secondary. | * Update and validate the roadmap based on the previous point. This includes adding missing stuff, if any, and removing what we think won't be ready on time or which is finally considered as secondary. | ||
Revision as of 21:24, 30 January 2006
Bugzilla Meetings
When and where?
Our first IRC meeting will take place on Thursday, Feb 2, 2006 at 19:00 GMT (11:00 PST) in the #bugzilla-meeting channel. The following meetings will probably take place the same day and time on a weekly basis. This point will be discussed on Thursday.
After each meeting, a brief summary will be available on this page.
Who can attend?
Everyone interested in being actively involved in the Bugzilla development for 3.0. joel, Wurblzap, justdave, timeless, wicked, myk, Colin and LpSolit will be there. Feel free to join us (no support question will be discussed there though, use the usual #mozwebtools channel for that).
What will be discussed during this first meeting (agenda)?
- First of all, the approval of the actual roadmap by the core developer team.
- Each assigned developer for a given task will be asked to inform us if they accept their role or not, and if yes, whether the deadline actually set seems reasonable.
- Update and validate the roadmap based on the previous point. This includes adding missing stuff, if any, and removing what we think won't be ready on time or which is finally considered as secondary.
- Release date for 2.20.1 and 2.22rc1. This will mainly depend on how far QA tests are and whether the release manager is ready with the website and the documentation. The actual date for the releases is Saturday, Feb 4, 2006. The trunk will be open for development again as soon as these versions are releases.
- Short discussion on bugs which may be considered as WONTFIX by some developers. This is a good opportunity to do some triage before someone wastes his time writing or reviewing a patch which will never land.
- Suggestions developers may have.
- Discussion on the frequency of the meeting (weekly, twice per month, monthly).
Summaries of previous meetings
Actually none :) Come and have a look again on Friday.