This is a set of things we want to discuss surrounding the Mozmill Project and the latest 1.3 release.
First I want to spend about 15mins talking about various high-level issues people have had either with the tool or with the release process for 1.3 and get them down. Then I want to spend the bulk of the meeting agreeing on ways forward between us (Mozmill Developers) and the Mozmill Mozilla user community.
Issues
- Docs are unclear and still in "draft" form and in multiple places still.
- No 1.3 release branch/tag for people to pull from [mikeal:Actually this was tagged today (12/3/2009), we should still discuss the process for bugfix releases going forward tho]
- Going forward we need to end the dependency of the current test repo with mozmill/master and instead require a release.
- Chaotic system for denoting blocking Mozmill bugs
- Visibility into development process is poor
- New results pages and integration with litmus [mikeal:Henrik and I are doing this right now, will be ready by Wednesday]
- Add yours now
Solutions
- Can we get a "blocking-Mozmill" flag or use the standard "blocking" flag inside the Mozmill component? For Mozmill's next release blockers. [mikeal: this is especially important when we talk about the XBL2 stuff coming up]
- Have a once a month mozmill bug triage phone call for interested folks?
- Propose yours here