Slideshare.net (beta)

 
Post: 
Myspace Hi5 Friendster Xanga LiveJournal Facebook Blogger Tagged Typepad Freewebs BlackPlanet gigya icons

All comments

Add a comment on Slide 1

If you have a SlideShare account, login to comment; else you can comment as a guest


Showing 1-50 of 3 (more)

Managing Modules Without Going Crazy (NPW 2007)

From brian_d_foy, 2 months ago

How to be the maintainer of many modules without killing yourself, more

286 views  |  0 comments  |  0 favorites
 

Privacy InfoNew!

This slideshow is Public

 
Embed in your blog
Embed (wordpress.com)

Slideshow Statistics
Total Views: 286
on Slideshare: 286
from embeds: 0* * Views from embeds since 21 Aug, 07

Slideshow transcript

Slide 1: Managing Modules Without Going Crazy brian d foy Nordic Perl Workshop 2007

Slide 2: Just Get Work Done

Slide 3: Less time maintaining modules Fewer complaints More time doing anything else Learn to live with “Good Enough” Have a life

Slide 4: ß

Slide 5: Just be yourself Don’t follow the leader (not even me) Finished work is the priority Playing with new tools is not the goal

Slide 6: Maintain modules Don’t spend time maintaining maintenance Avoid sysadmin monkey work Make reports, do meta-checks Script releases Use developer releases

Slide 7: Use old tools New OS’s / distros are nice, but generally a waste of time Same with new tools Don’t upgrade until you need to Don’t get rid of something that works

Slide 8: Avoid non-module work Don’t spend your time being a sysadmin Schemas come later Tolerate shaggy yaks Feeling good vs. useful work

Slide 9: Don’t let others host it Individuals, that is Avoid single points of failure Use Sourceforge, Google Project Hosting, et alia

Slide 10: Makemaker Module::Build has some problems Module::Build is not core Most people don’t need anything fancy Who cares what Schwern says? :) Unfortunately, Makemaker breaks a lot now

Slide 11: Avoid dependencies Code re-use is good You can go to far, e.g. Class:: If When dependencies break, so do your modules

Slide 12: Delete old versions Keep old versions out of user’s reach http://pause.perl.org Everything kept on BackPAN (backpan.cpan.org)

Slide 13: Scripted checks Automatically monitor module health Periodic smoke tests Nightly reports

Slide 14: Scripted releases Do everything the same way Check for common problems Have a consistent process

Slide 15: Module::Release • Won’t release anything until all checks pass • Checks... • test, disttest • kwalitee • VCS status • anything else you like • Uploads to right places

Slide 16: Developer releases $VERSION ends in /_d+z/ PAUSE won’t index CPAN tools won’t install Still in CPAN Search (http://search.cpan.org)

Slide 17: Changes files Avoid questions from users New features Fixes to bugs Should I upgrade?

Slide 18: CPAN Testers http://testers.cpan.org Almost every platform / Perl version Sometimes broken, but don’t sweat it

Slide 19: RT rt.cpan.org A pain, but adequate Collect all comments in one place Mention ticket numbers in Changes

Slide 20: The End