NAME ^

ROADMAP - A plan for Parrot

PURPOSE ^

As of this writing, there is no one place in which all remaining parrot work is documented. There are various TODO files, the RT queue, comments in the source code and the documentation. This document is a first pass at unifying this information and providing a single point of reference for anyone interested in the current state of the parrot, whether they are developers looking for items to work on, or external users looking for an idea of when they can expect a release.

This document is not meant to contain all the metadata regarding particular tasks, but merely provide a summary of the tasks.

Strictly speaking, this document is not a roadmap - that requires input from the Architect and the Pumpking. However, its goal is to help improve project management for parrot, and enable an actual roadmap.

CURRENT RELEASE (0.2.0) ^

Parrot 0.2.0 has been released on May 8th 2005. For a list of new and fixed feature see ChangeLog.

OVERVIEW ^

The tasks that are remaining are broken down into the following categories, roughly listed in the order through which a task might progress.

METADATA ^

Each task has certain metadata associated with it which must be tracked. Eventually all metadata should be stored in RT at http://rt.perl.org/rt3/

DESIGN ^

These are pending design decisions which must be made before any code can be written to implement them. Note - DESIGN is a special kind of documentation task. Due to the nature of this kind of documentation, it deserves to be broken out into its own category.

TODO ^

Any item, whether visible to parrot users or hidden behind an API, that has already been designed (but not implemented) belongs here.

BUGFIX ^

Any items which have been implemented but don't work as expected.

PORTABILITY ^

Any items which are specific to a particular platform or require special attention for cross-platform compatibility.

DOCUMENTATION ^

Any items pertaining to source, API, or user level documentation.

HIGH LEVEL LANGUAGES ^

Parrot currently ships with several partial language implementations. Any tasks which are specific to those languages, or affect cross-language compatibility will be listed here.

ISSUES ^

METADATA ^

DESIGN ^

TODO ^

BUGFIX ^

PORTABILITY ^

DOCUMENTATION ^

HIGH LEVEL LANGUAGES ^

FUTURE ^

This document should eventually be obsoleted by use of the RT ticketing system. Every task that is to be done should be documented in the system, and reports generated based on that information.


parrot