Perl 5.12.0
6 likes1,871 views
Perl 5.12 was recently released with several new features and improvements but no critical regressions reported so far. The "Pumpking" or project leader explained that development releases are now made monthly by release managers, reducing the workload on the Pumpking. Contributors now make the majority of changes to Perl, with over 70 unique authors contributing monthly.
Perl 5.12.0
- 1. Perl 5.12 Jesse Vincent jesse@perl.org
- 2. Hi!
- 3. I'm Jesse
- 4. I'm the Perl 5 “Pumpking”
- 5. Pumpking?
- 7. For now, just think of me as “project janitor”
- 8. Perl 5 is 16 years old
- 9. Perhaps you've heard that “Perl is Dead”
- 10. What they meant was “Perl Must Die”
- 11. They're on crack
- 12. Perl is very, very alive
- 13. Lots of exciting code on CPAN
- 14. Moose
- 15. Plack
- 16. Devel::Declare
- 17. AnyEvent
- 18. ...and a whole lot more
- 19. Two weeks ago, I made the scariest web post of my life
- 20. Pic of PAUSE
- 21. It had a happy ending
- 22. The stable version of Perl is now 5.12.0
- 23. Nobody has reported any critical regressions
- 24. ...so I haven't broken the Internet...yet
- 25. 5.12? What happened to Perl 6?
- 26. Perl 6 is a different language
- 27. Perl 6 is still being designed and built
- 28. rakudo.org
- 30. Perl 6 is the future
- 31. Perl 5 is the future, too
- 32. Perl 5 and Perl 6 are sisters
- 33. Perl 5 and Perl 6 are friends
- 34. “5” and “6” aren't versions of one language
- 35. “Perl 5” and “Perl 6” are names...
- 36. ...for two different languages
- 37. Perl 5's Creator
- 39. Perl 6's Creator
- 41. Perl 5 and Perl 6 have the same father
- 42. “5” and “6” are versions of Larry Wall's brain
- 43. We're looking forward to our “little sister” growing up
- 44. Perl 6 will not replace Perl 5
- 46. What was new in Perl 5.10?
- 47. given...when
- 48. given ($foo) { when (/^abc/) { $abc = 1; } when (/^def/) { $def = 1; } when (/^xyz/) { $xyz = 1; } default { $nothing = 1; } }
- 49. defined-or
- 50. $a // $b defined $a ? $a : $b
- 51. $c //= $d $c = $d unless defined $c
- 55. What's new in Perl 5.12?
- 56. You can use Perl 5.10 features
- 57. 5.10 isn't “too new to use” anymore
- 58. “use 5.12.0;” includes “use strict”;
- 60. “suidperl” is dead.
- 62. Y2038 Compliance
- 63. Unicode improvements and upgrade to version 5.2.
- 66. Dtrace Support
- 67. Modules deprecated from the core: ● Class::ISA ● Pod::Plainer ● Shell ● Switch
- 68. Don't worry, they're still on CPAN
- 69. Yadda yadda yadda...
- 70. (A new operator)
- 71. sub do_something { die “Unimplemented!”; } do_something();
- 73. j$ perl test.pl Unimplemented at test.pl line 3.
- 75. Lots of this was new in 5.10.1, too.
- 76. New release process
- 77. New pumpking
- 78. (Me)
- 79. So. That “Pumpking” thing
- 80. Pumpkin King
- 81. Keeper of the Patch Pumpkin
- 82. “Patch Pumpkin?”
- 83. David Croy once told me once that at a previous job, there was one tape drive and multiple systems that used it for backups. But instead of some high-tech exclusion software, they used a low-tech method to prevent multiple simultaneous backups: a stuffed pumpkin. No one was allowed to make backups unless they had the “backup pumpkin.” Chip Salzenberg
- 84. My job got its name because we didn't use a version control system 20 years ago.
- 87. ...otherwise, you may have to explain weird software development traditions to your children.
- 89. The Pumpking makes sure that the release of Perl doesn't suck.
- 90. ...and that it actually happens.
- 91. How it used to work
- 92. Perl 5.10
- 93. Perl 5.10.0
- 94. December 2007
- 95. It took 5 years
- 96. It burned through two pumpkings
- 97. Hugo van der Sanden (hvds)
- 98. Resigned in 2004
- 100. Resigned July 2009
- 101. Perl 5.10.1
- 102. Maintenance Release
- 103. 2800 commits changing over 350,000 loc in 2600 files
- 104. Only 700 or so blead commits weren't picked for 5.10.1
- 105. Before 5.12, maint releases: 1)include regression fixes 2)include general fixes 3)include build fixes (so it will compile on new/updated platforms) 4)include newer CPAN modules related to (3) 5)generally update CPAN modules where newer releases are available 6)include new features that aren't too scary and don't break backwards compatibility 7)maintain binary compatibility 8)don't break anything.
- 106. Dave Mitchell was the maint pumpking for Perl 5.10.1
- 107. He did all that work himself
- 108. “Doing all the above is *very* hard.” Dave Mitchell
- 109. Dave has a gift for understatement
- 110. That was a “maintenance” release
- 111. It included module updates...
- 115. It was a lot of work
- 116. It took too long
- 117. Maintenance release
- 118. That doesn't sound like “maintenance”
- 119. August 2009
- 120. Dave Mitchell (dapm)
- 121. Retired October 2009
- 122. Pumpkings are a precious commodity.
- 123. We can't keep burning them out.
- 124. The Pumpking's Job ● Hardcore C hacker ● Patch applier ● Release Engineer ● Language Designer ● Supreme Arbiter of Good Taste ● Project Manager ● HR Manager ● Dispute Resolver
- 125. Wow. That's a lot of stuff
- 126. Like I said before...
- 127. Project Janitor
- 128. Who have our pumpkings been?
- 129. Larry Wall, Andy Dougherty, Tom Christiansen, Charles Bailey, Nick Ing-Simmons, Chip Salzenberg, Tim Bunce, Malcolm Beattie, Gurusamy Sarathy, Graham Barr, Jarkko Hietaniemi, Hugo van der Sanden, Michael Schwern, Rafael Garcia- Suarez, Nicholas Clark, Richard Clamp, Leon Brocard, Dave Mitchell.
- 130. ...and now me
- 131. I don't want to burn out
- 132. How do you get to be pumpking?
- 133. (Traditionally)
- 134. Be a hardcore C hacker...
- 135. ...who loves Perl...
- 136. ...and has a responsibility complex
- 137. That's right
- 138. We take our best hackers...
- 139. ...and make them into managers
- 140. That is a complete waste of their talents
- 141. Nobody since Larry has been pumpking for two major versions
- 142. We can't keep losing pumpkings!
- 143. After rgs and dapm...
- 144. ...we ran out of qualified pumpkings!
- 145. This system is broken
- 146. How do you fix a broken system?
- 149. Like I said, earlier
- 150. Perl 6 is the future
- 151. Perl 6 is not Perl 5
- 152. How else do you fix a broken system?
- 153. Refactoring!
- 154. Role decomposition?
- 156. Hardcore C hacker
- 157. Delegate it!
- 158. Patch applier
- 159. Delegate it!
- 160. Release Engineer
- 161. Delegate it!
- 162. Language Designer
- 163. Delegate it!
- 164. (partially)
- 166. Core responsibility!
- 167. Dispute Resolver
- 168. Core responsibility!
- 169. “HR” Manager
- 170. Core Responsibility!
- 171. Project Manager
- 172. Core responsibility!
- 173. Ok.
- 174. Pumpkings don't need to be C hackers
- 175. Development releases leading to 5.10.0:
- 176. 5.9.0 2003-10-27
- 177. 5.9.1 2004-03-16
- 178. 5.9.2 2005-04-01
- 179. 5.9.3 2006-01-28
- 180. 5.9.4 2006-08-15
- 181. 5.9.5 2007-07-07
- 182. Development releases leading to 5.12.0:
- 183. 5.11.0 2009-10-02
- 184. 5.11.1 2009-10-20
- 185. 5.11.2 2009-11-20
- 186. 5.11.3 2009-12-20
- 187. 5.11.4 2010-01-20
- 188. 5.11.5 2010-02-20
- 190. 5.13.0 2010-04-20
- 191. Detect a trend?
- 192. Every Month
- 193. On the 20th
- 194. That sounds like a lot of work
- 195. I won't lie
- 196. 5.11.0 took me 4 days
- 197. 5.11.1 took me 2 days
- 198. 5.11.2 released by Leon Brocard
- 199. 5.11.3 released by me
- 200. 5.11.4 released by Ricardo Signes
- 201. 5.11.5 released by Steve Hay On Windows!!
- 202. Development releases now take hours instead of days.
- 203. The process is documented. See porting/release_manager_guide.pod
- 204. Release managers make dev releases See porting/release_schedule.pod
- 207. 4 1 0- 0 20 5.12.0 1 0 9- 1 20 6 0 9- 0 20 5.11.0 Unique authors per month 5.10.1 1 0 9- 0 20 5.10.0 8 0 8- 0 20 3 0 8- 0 20 0 0 7- 1 20 5 0 7- 0 20 2 0 6- 1 20 7 0 6- 0 20 2 0 6- 0 20 9 0 5- 0 20 4 0 5- 0 20 1 0 4- 1 20 5.9.0 6 0 4- 0 20 1 0 4- 0 20 8 0 3- 0 5.8.0 20 3 0 3- 0 20 0 0 2- 1 20 5 0 2- 0 20 n th Mo 70 60 50 40 30 20 10 0
- 208. 2 -1 09 20 7 -0 09 Commits per author per month 20 2 -0 09 20 9 -0 08 20 4 -0 08 20 1 -1 07 20 - 06 07 20 1 -0 07 20 8 -0 06 20 3 -0 06 20 0 -1 05 20 5 -0 05 20 2 -1 04 20 7 -0 04 20 2 -0 04 20 - 09 03 20 4 -0 03 20 1 -1 02 20 6 -0 02 20 1 -0 02 20 8 6 4 2 0 18 16 14 12 10
- 209. 800 700 600 500 400 300 200 100 0 1 0-0 201 Pumpking-authored-patches Pumpking vs Contributor Patches 9 -09 200 - 05 Porter Patches 9 200 9 - 01 200 8 - 09 200 8 - 05 200 1 8 -0 200 7 - 09 200 7 - 05 200 7 - 01 200 6 - 09 200 6 - 05 200 6 - 01 200 5 - 09 200 5 - 05 200 5 - 01 200 4 - 09 200 5 4-0 200 4 -01 200 3 - 09 200 3 - 05 200 3 - 01 200 2 - 09 200 5 2 -0 200 2 - 01 200 0 800 700 600 500 400 300 200 100
- 210. 800 700 600 500 400 300 200 100 0 0 - 01 201 Pumpking vs Contributor Patches 9 - 09 200 9 - 05 200 9 - 01 200 9 8 -0 200 8 - 05 200 8 - 01 200 7 - 09 200 7 - 05 200 7 - 01 200 6 -09 200 6 - 05 200 6 - 01 200 5 - 09 200 5 - 05 200 5 - 01 200 4 -09 200 4 - 05 200 4 - 01 200 3 - 09 200 3 - 05 200 3 - 01 200 2 -09 200 2 - 05 200 2 - 01 200 800 700 600 500 400 300 200 100 0
- 211. What about "Stable releases"?
- 212. Old maintperl policy
- 213. New releases of maint should contain as many changes as possible
- 214. New maintperl policy
- 215. New releases of maint should contain as few changes as possible
- 216. If there is any question about whether a patch should be backported to maint, then the answer is probably “No!”
- 217. What's OK
- 218. Portability fixes, like changes to Configure and hints/
- 219. Documentation updates
- 220. Fixes for crashes that don't change features or hurt performance
- 221. Patches to fix security issues
- 222. Minimal patches to fix crashes or security issues in CPAN modules
- 223. What's not OK
- 224. New warnings or errors
- 225. Deprecating features
- 226. New versions of dual-life modules
- 229. Ports to a new platform or OS
- 230. ...anything else
- 231. When's 5.12.1 coming?
- 232. Estimated: May 12, 2010
- 233. So, what's coming in 5.12.1?
- 234. Bugfixes
- 235. 5.12.x will come every 3 months
- 236. When's 5.14 coming?
- 237. Spring 2011
- 238. What's coming in 5.14?
- 239. I don't know
- 240. What I want in Perl 5.14
- 243. Better connectivity
- 244. HTTP Client
- 245. IPv6
- 246. SSL?
- 249. What do you want in Perl 5.14?
- 250. Trying out 5.12.0
- 251. perlbrew (gugod)
- 252. # install perlbrew curl -O -L http://xrl.us/perlbrew perl perlbrew install # setup perlbrew ~/perl5/perlbrew/bin/perlbrew init echo "source $HOME/perl5/perlbrew/etc/bashrc" >> ~/.bashrc # restart your shell exec $SHELL # install perl 5.12.0: this takes ~10 minutes perlbrew -v install perl-5.12.0 perlbrew switch perl-5.12.0
- 253. Thanks!
- 254. Questions? Jesse Vincent jesse@perl.org