VersionEyeContinuous Updating

Robert Reiz

https://twitter.com/RobertReizwww.VersionEye.com

Waterfall Model

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

Agile

● Short dev. cycles

● Execute Waterfall Model weekly or 2 w.

● Short time to market

● Early customer Feedback

● Big Goals/Requirements can be changed.

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 are passive!

● Software Libraries are not like iPhone Apps.

● Developers are missing important Bugfixes.

● Developers are missing Updates.

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 !

Continuous Updating

● There are always migration paths to the next

higher version.

● But there are no migration paths from 1 to 5!

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!

Continuous Updating

● You have to automate the updating process.

● You need a tool for that!

VersionEye

VersionEye

Follow 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.

API

http://marco-pivetta.comhttps://github.com/Ocramius/VersionEyeModule

? ? ?