Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • How has ponie been doing? I can't seem to find much recent news about it. Is it still alive? Has there been any progress? Where can I get a copy? I hope it's not dead, it was an interesting idea.
    • Ponie is progressing, athough progress seems to be stalls then jumps, even when the effort is applied smoothy. A development snapshot was released a couple of weeks ago, announced in Allison's state of the carrot at YAPC::NA. I sent an announcement to the ponie-dev mailing list, and it's also waiting in the use.perl story submission queue [perl.org] for a use.perl editor's tender loving care.

      Details of what's new are in the README [perl.org], and you can also view the most up-to-date version of the Roadmap [perl.org] in the subversion repostiory.

      The development snapshot is now out of date - if you want to get the most recent version check it out with subversion from http://svn.perl.org/ponie/trunk [perl.org]

      The trouble with Ponie in general is that because it's mostly a big, progressive refactoring exercise it keeps throwing up unexpected problems that need to be investigated and solved prior to completing a task. Quite a few of the problems so far have been in the perl 5 core code, and have been solved there first, before being merged over as a block. It's also tricky to declare any task as "finished", because most of them aren't, in the sense of being completed. Most need revisiting once other parts progress far enough, so I don't consider them finished, so I don't make grand sweeping pronouncements to that effect. Also I feel that given all the twists and turns, attempting to keep the roadmap/tasklist updated on a daily basis would eat up more time than the actual development work.

      I attempt to keep the commit messages both short and informative - possible the best way of tracking progress is by watching the commit list ponie-changes [perl.org]