Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Philip Bauer
Starzel.de
Migrations
Upgrades
Relaunches
irc & github: pbauer
twitter: StarzelDe
"I'm not sure we can launch
without the preview-button."
Align Expectations
Communication and Project-Management
Update
Upgrade
Migration
Redesign
Rewrite
Relaunch
if len(terms) >= 2:
print("It's a relaunch!")
• Ease Development
• Cool new Features
• Learn new Things
Why devs want to upgrade
Selling migrations
• Design
• Functionality
• Usability
• Speed
• TinyMCE in IE9
Which will it be?
• What about the content?
• What about the design?
How to migrate
• Make a Plan
• Make generous Timeline
• Present Changes before they happen
• Know the Upgrade-Guide
• Migr...
• Lot‘s of Disk-Space
• /tmp
• Keep Original for Comparison
• Make Snapshots
Pittfalls
• Remove Customisations
• Cleanup Add-ons & Design
• Clear & Rebuild
• Copy DB to new Buildout
• Startup
• Fix all Errors
• Document
• Disable irrelevant stuff
• Remove obsolete stuff
• Work hard
• Migrate the DB
• Integrate Customisations
• Write Migration-Steps
• Automate almost Everything
• collective.upgrade
• ft...
Test the Hell out of it
Add shiny new stuff
Repeat
Challenges and Pitfalls
• The customer
• Your big mouth
• Design
• Legacy
• Multilingual
• Relations
Lessons
• Bad Communication and PM kill Projects
• Every Case is different
• Every non-trivial Upgrade should be
approache...
Questions
• How do you estimate time & cost?
Philip Bauer
Starzel.de
irc & github: pbauer
twitter: StarzelDe
Migrations, Upgrades and Relaunches
Upcoming SlideShare
Loading in …5
×

Migrations, Upgrades and Relaunches

650 views

Published on

Selling an update to a client who is clinging to their ages-old Plone-site is only the first of many problems you face when it comes to updates. This talk is a collection of best-practices and lessons-learned during many migrations from "cosmetic designs-changes" that ended up in complete relaunches to "minor version upgrades" that ended up in large-scale coding-horrors. Audience-participation to trade tips and tricks is highly encouraged.
Topics covered include:
- Explaining reasons to upgrade to humans
- Why almost everything is a relaunch
- "What did you do to my pixel?" - Surviving design-upgrades
- Content-Migration: Tools, Tactics and Troubles
- When every feature becomes a bug
- What can break?
- What to migrate and what you might want to loose
- How to keep your own developments upgrade-safe(ish)

See a video of thetalk at http://www.youtube.com/watch?v=1Qx0JALp3lQ

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

Migrations, Upgrades and Relaunches

  1. 1. Philip Bauer Starzel.de Migrations Upgrades Relaunches irc & github: pbauer twitter: StarzelDe
  2. 2. "I'm not sure we can launch without the preview-button."
  3. 3. Align Expectations Communication and Project-Management
  4. 4. Update Upgrade Migration Redesign Rewrite Relaunch
  5. 5. if len(terms) >= 2: print("It's a relaunch!")
  6. 6. • Ease Development • Cool new Features • Learn new Things Why devs want to upgrade
  7. 7. Selling migrations • Design • Functionality • Usability • Speed • TinyMCE in IE9
  8. 8. Which will it be? • What about the content? • What about the design?
  9. 9. How to migrate • Make a Plan • Make generous Timeline • Present Changes before they happen • Know the Upgrade-Guide • Migrate your Code • Migrate Add-ons
  10. 10. • Lot‘s of Disk-Space • /tmp • Keep Original for Comparison • Make Snapshots
  11. 11. Pittfalls
  12. 12. • Remove Customisations • Cleanup Add-ons & Design • Clear & Rebuild • Copy DB to new Buildout
  13. 13. • Startup • Fix all Errors • Document • Disable irrelevant stuff • Remove obsolete stuff • Work hard
  14. 14. • Migrate the DB • Integrate Customisations • Write Migration-Steps • Automate almost Everything • collective.upgrade • ftw.upgrade
  15. 15. Test the Hell out of it
  16. 16. Add shiny new stuff
  17. 17. Repeat
  18. 18. Challenges and Pitfalls • The customer • Your big mouth • Design • Legacy • Multilingual • Relations
  19. 19. Lessons • Bad Communication and PM kill Projects • Every Case is different • Every non-trivial Upgrade should be approached as a Relaunch • Don‘t experiment
  20. 20. Questions • How do you estimate time & cost? Philip Bauer Starzel.de irc & github: pbauer twitter: StarzelDe

×