__color__,__group__,ticket,summary,component,priority,version,owner,status,created,_changetime,_description,_reporter
4, Release,1525,improved NCI/FFI,none,normal,,,new,2010-03-22T22:28:06Z,2010-04-06T21:45:37Z,"The existing interface to and implementation of NCI needs refinement. See NCITasklist

This task does not depend on Lorito, but design and implementation should take the future of Lorito into consideration.",allison
3,2.11 Release,607,ordered destruction,GC,major,,,new,2009-04-28T22:56:44Z,2012-01-04T10:38:38Z,"Extend or modify the existing GC and GC modules to allow ordered destruction (guarantee that the children of one PMC will all be destroyed before that PMC, etc).",allison
4,2.11 Release,622,serialize/resumable execution,core,normal,,,new,2009-04-29T00:17:35Z,2011-08-27T17:16:56Z,A wishlist feature for being able to save off the entire state of a currently executing interpreter and resume it later (or on a different machine).,allison
4,2.11 Release,624,pluggable everything,core,normal,,allison,new,2009-04-29T00:19:49Z,2012-01-04T10:40:43Z,A blanket wishlist item to change a substantial part of the core to dynamic extensions. The first step of the task is reviewing Parrot core to decide what parts might be good candidates for a pluggable architecture.,allison
4,2.5 Release,592,Add documentation for parrot_debugger,docs,normal,,allison,new,2009-04-28T21:03:28Z,2011-03-27T14:14:19Z,"Add documentation for the PIR debugger, 'parrot_debugger'. We need more examples.",allison
4,2.5 Release,593,"standard seed libraries (postgres, opengl, etc)",none,normal,,,new,2009-04-28T21:09:03Z,2010-10-16T22:21:39Z,"Improve existing libraries for Postgres, OpenGL, etc, so they are reliable, and relatively feature complete.

Explore other libraries that we should provide by default in a full Parrot install.

The goal is to provide a small set of working libraries, both as an example to other library implementors, and to make it easier for average developers to tackle everyday tasks in Parrot. The set of seed libraries can be small, and libraries already implemented in an existing HLL are reasonable to satisfy the ""everyday tasks"" goal.",allison
4,2.5 Release,1523,subroutine leave semantics/exit handlers,core,normal,2.2.0,,new,2010-03-22T22:13:22Z,2010-10-16T22:18:47Z,Various HLLs need the ability to attach arbitrary handlers on subroutine/scope exit. (e.g. tcl's [trace]),allison
4,2.6 Release,566,export conventions (cross hll),hll_interop,normal,,,new,2009-04-21T13:30:21Z,2010-04-06T21:32:00Z,From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.,coke
4,2.6 Release,567,pdd31-hll interop,hll_interop,normal,,whiteknight,new,2009-04-21T13:30:37Z,2010-11-22T15:51:46Z,From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.,coke
4,2.6 Release,568,hll interop,hll_interop,normal,,whiteknight,new,2009-04-21T13:31:01Z,2010-11-22T15:51:51Z,From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.,coke
4,2.6 Release,599,bytecode generation from post,none,normal,,bacek,new,2009-04-28T22:14:30Z,2011-02-20T23:50:26Z,"Hello.

Yes, in PIRATE and nqp_pct branches there is some initial work on generating PBCs from POST. Not finished yet.

I'll probably jump on new NQP train and implement it there with future importing into parrot tree.

-- 
Bacek",allison
4,2.6 Release,1522,sweep-free gc,none,normal,,,new,2010-03-22T22:04:58Z,2010-04-06T21:41:14Z,"Implement a sweep-free garbage collector. Useful, not high-priority.",allison
4,3.0 Release,565,"remove optional features from default config, refactor config probes",configure,normal,,,new,2009-04-21T13:29:50Z,2009-07-21T01:44:16Z,From https://trac.parrot.org/parrot/wiki/ParrotRoadmap.,coke
4,3.0 Release,598,bytecode migration tool,none,normal,,,new,2009-04-28T22:12:53Z,2010-03-30T21:12:29Z,"Write a tool to translate one bytecode format to another.

Extra advantage if the changes to make can be specified in a simple syntax, and if the translations can be chained. (That is, once you write a file that details the changes from 2.0 bytecode to 2.6 bytecode and another one with the details of 2.6 bytecode to 3.0 bytecode, the translation tool is smart enough to use the two files to translate 2.0 bytecode to 3.0 bytecode by translating it to 2.6 as an intermediate step.)

The tool will also have to give warnings about opcodes and PMCs that no longer exist, as these can't be mechanically translated. Tell the user to regenerate the bytecode from source instead.",allison
4,3.0 Release,600,bytecode testing framework,none,normal,,,new,2009-04-28T22:22:47Z,2010-03-30T21:13:21Z,A framework for directly testing bytecode examples. Somewhat similar to the PIR/PASM/C testing framework.,allison
4,3.0 Release,616,compacting/copying gc,GC,normal,,,new,2009-04-28T23:30:41Z,2010-06-13T23:18:12Z,Implement a compacting/copying garbage collection module for Parrot. This will require some changes to the Parrot core to make it possible to move objects.,allison
