A discussion of DBIx-Class governance and future development

Due to a dispute on the exact nature of the future of DBIx-Class development after Peter Rabbitson's pending departure, a conversaton has been opened on the DBIx-Class mailing list to feel out what the users of DBIx-Class think.

If you have an interest in the module and its future, please have a read of the current sitation, and maybe leave a note on your position:


Please test MITHALDU/OpenGL-0.6704_05.tar.gz

Reaching out to the Perl community at large due to this release being hardware-sensitive and feedback being most useful to me when it comes from many various hardware combinations, particularly if the graphics cards involved are older or stranger.

Please test this CPAN developers release on your platforms to confirm that
there are no regressions from the last stable release. ... Actually,
please do report any and all errors you can see, i am VERY keen to see
what other issues this throws up on different platforms.

[BREAKING] [GPW 2015] German train drivers' union calls 5-day strike starting Tuesday

This is just a quick PSA to bring it to anyone's attention who needs to know and doesn't already yet: The association of german train drivers has announced a general strike of person transportation from tuesday to sunday (5.5. - 10.5.). No further details have been announced by Die Bahn yet, but this might call the German Perl Workshop this year in jeopardy. Organizers have been sent messages, but have not replied yet.

Edit: The GPW organizers have ="http://blogs.perl.org/users/max_maischein/2015/05/should-be-a-reply-to-gpw-2015-german-train-drivers-union-calls…

PPI 1.219_001 - please test - breaking ->prototype changes and parse improvements

I took some time today to prepare a number of pull requests by MOREGAN for release, and the tarball for 1.219_001 is now on CPAN. Please test it and let me know if you run into problems with your module. Most of the changes simply improve parsing, but the ->prototype changes might break things if you relied on the previously broken behavior.

If no problems crop up, this will be released as 1.220 on tuesday, 2014-11-11.

I am not picky about which way it is sent to me, but feedback is best provided here: Github Issue #92

PPI 1.218 has been released - bug fixes, speed optimizations, tests, doc improvements

On request of Neil Bowers i pushed this release back a day, so now on CPAN Day in 2014 the first update of PPI in 3.5 years has been released to CPAN and will be available on a mirror near you soon.

Since the release candidate only minor changes affecting the release process itself have been made.

The change log has a detailed listing and the git repository is even more detailed (it even has tags if you clone it). That said, the summary of the changes is:

  • a number of fixes to how Perl is parsed, notably around the x operator and some case sensitivity
  • many speed optimizations, allowing PPI to parse big files in reasonable time
  • the 1MB limit is now removed
  • many many doc fixes
  • many more tests for previously untested code
  • PPI is now on Github

I already posted this before too, but it bears repeating: This release has been made possible almost entirely by the contributions of Tom Wyant, Olivier Mengué, David Steinbrunner, Kevin Dawson (bowtie), Matthew Horsfall (alh), massive amounts of work by Mike O'Regan, more help and most importantly the blessing of Adam Kennedy and moral and substantial support by Matt Trout. Thanks to all of you.

Also, thanks to all of you who tested the release candidate and gave me the confidence to do this release.

Lastly, to address a question brought up by Buddy Burden and a few others: How does PPI deal with new syntax? At this point, no decision has been made on that. PPI is currently version-agnostic and simply regards what it parses as a perl document with indeterminate version requirements and global validity. There will need to be decisions made regarding two different kinds of version implications:

  • some syntax will only be parsable by perl executables with a specific version, even without explicit declaration
  • some syntax will change what it parses to, depending on declared version in the source code (see ~~)

PPI has a stated goal of "never die, even if the code is invalid, parse it as far as possible". This means new API features on PPI itself will need to be implemented to sanely handle things. Input in the PPI issues on github is very welcome on this matter.