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.
  • Michael,

    Thanks for that link. Word to whoever clicks on it: While the video quality is poor during the first 30 seconds, it becomes tolerable thereafter.

    While I've read a lot about the Perl 5 release process in the past two weeks, I have no personal familiarity with it. I can, however, make some comparisons with the Parrot project.

    Like OpenBSD, Parrot believes in releasing on pre-announced dates, though Parrot works on a monthly cycle rather than OpenBSD's 6-month cycle.

    While we don't submit people who break trunk to the same sort of mockery that Theo describes for OpenBSD, people who do so are expected to clean up the problem quickly.

    OpenBSD locks its code tree at a point a few weeks before the release data, then everyone goes into heavy testing mode. Parrot doesn't have a formal lock period per se, but we do expect people to stop making any significant commits three to four days before a release (i.e., today). And part of the reason we don't have a formal lock period is that the results we get from our Smolder reports -- many reports per day on our main OSes -- enable us to spot regressions and correct them quickly.

    Thank you very much.