1. VersionEye
Continuous 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.
● It's 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. VersionEye
Follow 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. API
http://marco-pivetta.com
https://github.com/Ocramius/VersionEyeModule

18. ???