Date

13 November 2008

In Attendance

Mike Seaton
Justin Miranda
Ben Wolfe
Burke Mamlin
Brian McKown
Paul Biondich

Agenda

• AMIA wrapup

• logicathon wrapup

Minutes

• lessons from the logicathon

  • Should we do separate branches for each feature?

    • If each feature is in one branch, one slow feature will keep all changes from being merged to trunk

    • Something that is encapsulated can/should be put in a separate branch

  • Hack-a-thons should follow Road Map

    • If hack-a-thon happens ahead of the road map time line, we should not wait on the time line

    • Road Map should give a full view of what upcoming code will go into trunk.

    • Something that is encapsulated can/should be put in a separate branch

    • If hack-a-thon happens ahead of the road map time line, we should not wait on the time line.

      • Have a Road Map "bin" of things that are being designed or nearing completion that will go onto road map.

      • Things that are completing design should go onto the Road Map.

      • Let Road Map determine the pathway of when a feature gets merged to trunk.

  • Core of persistence code is finished in the logicathon branch and should be scheduled for merge.

    • Should have something in core that can be visibly used to be able to test logic service.

• The roadmap needs to show all features that are coming up. However, how do we assign features that aren't designed yet?

  • Create an Alien Technology release that will hold all things not designed or not coded yet.

  • Things get pulled out of that "release" into numbered releases as we know how long they will take and how code reviews go

• Possible Roles

  • Release Manager

    • Volunteer to be in charge of a release for a certain amount of time.

  • Back Port Manager

    • Volunteer to back port bug fixes to previous releases that are still supported.