Your SlideShare is downloading. ×
0
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
VersionEye for PHP User Group Berlin
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

VersionEye for PHP User Group Berlin

1,059

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,059
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. VersionEyeContinuous Updating Robert Reiz
  • 2. https://twitter.com/RobertReiz www.VersionEye.com
  • 3. Waterfall Model
  • 4. Waterfall Model● Waterfall is just not state of the art anymore!● Long time to market● Customer Feedback is coming too late● Requirements are not flexible● Requirement Documents are to expensive
  • 5. Agile● Short dev. cycles● Execute Waterfall Model weekly or 2 w.● Short time to market● Early customer Feedback● Big Goals/Requirements can be changed.
  • 6. Agile Software Development● Continuous Refactoring● Continuous Testing● Continuous Integration● Continuous Deployment
  • 7. Agile Software Development Continuous Updating !
  • 8. Continuous Updating● In avg. 50 Libraries per project.● After 2 weeks the first libs are out-dated!● Software Libraries are passive!● Software Libraries are not like iPhone Apps.● Developers are missing important Bugfixes.● Developers are missing Updates.
  • 9. Continuous Updating● Big Migrations are risky and expensive● Small Migrations you can do on the fly● How hard it is to switch from Rails 2.1 to 3.2? ○ Very Hard !● How hard it is to switch from Rails 3.2.10 to 3.2.11? ○ Very easy !
  • 10. Continuous Updating● There are always migration paths to the next higher version.● But there are no migration paths from 1 to 5!
  • 11. Continuous Updating● Manually checking if there are new versions out there for your 50+ Libraries costs Time & Money.● Its not fun!● Nobody wants to do it!
  • 12. Continuous Updating● You have to automate the updating process.● You need a tool for that!
  • 13. VersionEye
  • 14. VersionEyeFollow your Libraries and get notified about new versions. Never miss an update!
  • 15. VersionEye DEMO
  • 16. API● https://www.versioneye.com/api● Hooks are coming soon.● RSS is coming soon.
  • 17. APIhttp://marco-pivetta.comhttps://github.com/Ocramius/VersionEyeModule
  • 18. ???

×