Road Map

This page is a draft aimed at providing all the developers a board to discuss and define what features should be achieved for milestones and how and when a feature freeze should occur.

The roadmap can be discussed by everyone

• On #pida channel,
• On this page, by adding comments or remarks.
• Using Question tickets for important decisions.

Process

Trac already provides a system to define Milestones, and it should be used to prevent scattering information. Milestones can be described in terms of

• Essential components it contains
  Components are Services, Editors and miscellanies like the community plug-ins. Existing components are automatically distributed with the next milestone. Planned or currently developed components should have a Task associated to them.

• Documentation
  Documentation can be addressed to end users and developers. Again, a Task should be associated to any addition in the documentation. Developer documentation is currently also detailed in DeveloperDoumentation.

• Bugfix
  All bugs should be associated to a Defect in Trac.

Tasks and defects can be associated to a milestone, and this should be the unique way to identify what is needed to complete milestones to come, and keep track of previous milestones. Before or soon after a Ticket is created, discussion shall occur to determine its milestone target. This target can be updated until the feature freeze is announced.

At one point, and after having checked that all tickets are associated to a milestone, decision will be taken to start feature freeze. Then, the next milestone description should not be edited anymore to add or remove any task. Defects or questions could still be added though.

Trac automatically builds a graphical roadmap with the tickets information. This view is a summary of all information about milestones, but misses information like feature freeze date and discussion on the feature choices for example. The rest of this page is dedicated to this kind of information.

Milestone 0.5

Existing tasks' milestone should be discussed as soon as possible if the process described here is adopted. Discussion shall involve at least the ticket owner, the person it is assigned to, and Ali I guess. Tasks should also be created for the missing documents. After that, release blockers should be identified and worked on, and a feature freeze date could be chosen. - d_rol

Feature Freezed on Tue May 22 12:56:37 BST 2007

Released on Fri Jun 29 16:44:47 BST 2007

Milestone 0.5.1

Being worked out.

Discussion for Milestone 0.6

None yet.