VersionEyeContinuous Updating       Robert Reiz
https://twitter.com/RobertReiz    www.VersionEye.com
Waterfall Model
Waterfall Model● Waterfall is just not state of the art anymore!● Long time to market● Customer Feedback is coming too lat...
Agile● Short dev. cycles● Execute Waterfall Model weekly or 2 w.● Short time to market● Early customer Feedback● Big Goals...
Agile Software Development● Continuous Refactoring● Continuous Testing● Continuous Integration● Continuous Deployment
Agile Software Development    Continuous Updating !
Continuous Updating● In avg. 50 Libraries per project.● After 2 weeks the first libs are out-dated!● Software Libraries ar...
Continuous Updating● Big Migrations are risky and expensive● Small Migrations you can do on the fly● How hard it is to swi...
Continuous Updating● There are always migration paths to the next  higher version.● But there are no migration paths from ...
Continuous Updating● Manually checking if there are new versions  out there for your 50+ Libraries costs Time &  Money.● I...
Continuous Updating● You have to automate the updating process.● You need a tool for that!
VersionEye
VersionEyeFollow your Libraries and get notified about new versions. Never miss an update!
VersionEye  DEMO
API● https://www.versioneye.com/api● Hooks are coming soon.● RSS is coming soon.
APIhttp://marco-pivetta.comhttps://github.com/Ocramius/VersionEyeModule
???
Upcoming SlideShare
Loading in …5
×

VersionEye for PHP User Group Berlin

1,386 views

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,386
On SlideShare
0
From Embeds
0
Number of Embeds
469
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

VersionEye for PHP User Group Berlin

  1. 1. VersionEyeContinuous Updating Robert Reiz
  2. 2. https://twitter.com/RobertReiz www.VersionEye.com
  3. 3. Waterfall Model
  4. 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. 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. 6. Agile Software Development● Continuous Refactoring● Continuous Testing● Continuous Integration● Continuous Deployment
  7. 7. Agile Software Development Continuous Updating !
  8. 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. 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. 10. Continuous Updating● There are always migration paths to the next higher version.● But there are no migration paths from 1 to 5!
  11. 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. 12. Continuous Updating● You have to automate the updating process.● You need a tool for that!
  13. 13. VersionEye
  14. 14. VersionEyeFollow your Libraries and get notified about new versions. Never miss an update!
  15. 15. VersionEye DEMO
  16. 16. API● https://www.versioneye.com/api● Hooks are coming soon.● RSS is coming soon.
  17. 17. APIhttp://marco-pivetta.comhttps://github.com/Ocramius/VersionEyeModule
  18. 18. ???

×