r6 - 27 Mar 2007 - 14:29:02 - PhilippeBossutYou are here: OSAF >  Journal Web  >  DevelopmentHome > ApplicationProject > AppsMeeting20051101

Apps meeting Tuesday November 1st 2005

Agenda

  • Specs
  • Schedule
  • Engineering
  • People

Summary

  • Plan : Bugs, bugs, bugs...
  • Progress : Bug trend encouraging. Total (P1+P2+P3) under the 100 bar for the first time!
  • Problems : Process perceived as too heavy in some cases. We clarified the "wiggle room" cases.

Actions

  • Philippe : review bug list to identify punt candidates for Thursday

Minutes

Specs

Nothing to report this week.

Schedule

The bug trend looks good despite a very big number of bugs logged against 0.6 last week.

The Bug Council will be meeting Thursday to scrub more P3s out of 0.6 and narrow the focus on what will need to make it in 0.6. P4 and P5 are likely to be punted wholesale. By November 9th (Code Complete), we will be fixing and taking in only blocking bugs (i.e. can't ship with them in). Please see Heikki's e-mail on the Dev list on this subject.

Engineering

Question on Processes

Should one line change not be reviewed? Should we use a different lightweigth process for lightweight bugs?

Show of hands: 50% of people think it's required. Review after check-ins should be considered OK in some cases.

Some pointing what we need some wiggle room to make speedy changes. We actually have it for special circumstances (app broken, build broken, ...). Also review approval can be granted without going through the formal Bugzilla review structure in the case of one liners. Some changes (comments, code not built) do not need to be reviewed (make sure you mention it in commit message). Also rememeber to use your svn sandbox when developing experimental stuff. Last, everything can be bypassed in case of emergency by contacting one of the Bug Council member through IRC.

Conclusion : the rules are there for most common cases, exceptions (wiggle room) can be handled through ad-hoc public communication. We also want to use the same rules for everyone, including external contributors.

Other

  • Should we branch : only at ZBR, as long as everybody is focused on 0.6 bug fixing, no need to branch. SVN is making this easier though (including merging) so we shouldn't be too shy about branching.
  • Tutorials and CPIA doc : we are making slow progress here but some progress nevertheless... To be continued.
  • Read Producing Open Source Software : Really, really good read. We'll be buying a bunch for the office. You can expense your copy. We do have lots to learn for sure.
  • Dogfooding : Mitch using m6 seriously and relatively pleased (modulo bugs...). Next, we'll use Chandler to publish the conf bridge schedule (Esther).

People

Recruiting : still in progress, some good leads being worked out.


Status

Philippe

  • Bug Council duties : I'm spending most of my working hours in Bugzilla.
  • Recruiting duties
  • Helped worked out a sidebar icon issue resolution
  • Started to read 0.7 specs
  • Final round of review on budget

John

  • Finished making a pass over all my bugs.
  • Actually kept up with all my new bugs this week.
  • Fix Bug #3939: assert on HasCapture dragging into the Sidebar.
  • Removed icons from the sidebar.
  • Got a rough draft of my hello world parcel working, after encountering a bunch of snags with pje's Annotation scheme.
  • Interviews

David

  • worked on various bugs:
    • partially fixed some of them
  • worked on docs:
    • near complete - framework issues (criteria)

Jed

  • Your status here...

Alec

  • Your status here...

Bryan

  • Your status here...

Donn

  • Major refactoring of CATS scripts complete, and now CATS seems to be running pretty smoothly
    • Still some profile stuff to look at
  • Fixed bugs 4499, 4444, 4392, 4324
  • Reviewed bug list
  • Interviewed QA Intern candidate Dan Steinick and wrote up impressions

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r6 < r5 < r4 < r3 < r2 | More topic actions
 
Open Source Applications Foundation
Except where otherwise noted, this site and its content are licensed by OSAF under an Creative Commons License, Attribution Only 3.0.
See list of page contributors for attributions.