NAME ^

ROADMAP - A plan for parrot 1.0 and beyond.

PURPOSE ^

Describe the work that is remaining to release parrot 1.0, including both user-visibile features and internals.

This document is intended to be a high level overview of remaining areas of work. For more detailed information about remaining tasks, see https://rt.perl.org/rt3.

It also contains information about future direction after 1.0.

LAYOUT ^

Each task is associated with a major release of parrot. Additionally, each task will refer to its current state, and a link to any documentation regarding the task (i.e. something on Launchpad, RT, or in the repository, or on the wiki). Tasks with no supporting documentation will be marked [Unspecifed].

1.0 ^

TBD.

2.0 ^

Build System ^

NOTE ^

The contents of this file are outdated and must be reviewed. See RT #48611.

UNREVIEWED CONTENT ^

There is no single 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.

For a high level overview of parrot milestones, please see: http://www.perlfoundation.org/parrot_grant_from_nlnet

RELEASE POLICIES ^

The following conditions must be met in order to release a new Parrot version:

All bugs which cause Parrot to dump core must be addressed

This is the highest priority.

Fix all bugs tied to the given milestone

RELEASE HISTORY ^

For a list of previous releases see parrothist.pod. For a list of new and fixed features in each release see ../NEWS.

OVERVIEW ^

The remaining tasks 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 https://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, but 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 ^

DOCUMENTATION ^

DESIGN ^

TODO ^

BUGFIX ^

PORTABILITY ^

HIGH LEVEL LANGUAGES ^

FUTURE ^

This document should eventually be obsoleted by use of the RT ticketing system, except to the extent that it documents things that show promise but have not yet been committed to. Every task that is actually ready to be done should be documented in RT, and reports generated based on that information.

BUGS (in this document) ^

As for the future development, it has been pointed out that RT is not the best system for handling such things (though it does have the advantage of being available). The main point is to have single point of contact to help volunteers check (and update) the status of issues important to them.


parrot