This is the Continuous Updating talk from the API Days in Berlin.

1. #ContinuousUpdating
!
@RobertReiz

2. 100 libraries per
project in avg.

3. How do you keep track
of your LIBRARIES?

4. How many DEPENDENCIES do
you have in your project?

5. Which LICENSES are
your dependencies
using?

6. You don’t know ?

7. Requirements
Analysis
Design
Coding
Testing
Accepting
15 years ago we used to work with the WATERFALL MODEL

8. But today we are AGILE

9. Everything the Waterfall Model used
to execute in one year ...
!
... we nowadays execute in 2 weeks!

10. The way we develop software
today totally changed!

11. Being AGILE got us
CONTINUOUS Testing
CONTINUOUS Refactoring
CONTINUOUS Integration
CONTINUOUS Delivery

12. But what about
CONTINUOUSUpdating

13. Why should I care about
Continuous Updating?

14. Core committers don’t release
new versions just for fun!

15. • BugFixes
• SecurityFixes
• Speed & Memory optimization
• New Features
They always have good reasons

16. If you can't fly then run,
if you can't run then walk,
if you can't walk then
crawl,
butwhateveryoudo
youhavetokeepmoving
forward.
Martin Luther King Jr.

17. How do you ensure that new
versions don’t break the system?

18. Semantic Versioning
Migration Paths
Continuous Testing

19. http://semver.org/

20. 1.MAJOR version when you make incompatible API changes
2.MINOR version when you add functionality in a backwards-compatible manner
3.PATCH version when you make backwards-compatible bug fixes.
MAJOR.MINOR.PATCH

21. Always follow the
MIGRATION PATH

22. Many small steps are
better than one big step
!
You can do SMALLMIGRATIONS on the fly.
!
BIGMIGRATIONS are risky and expensive.
!
If you miss versions, you miss migration paths, too.
And that leads to TROUBLE!

23. 1 2 3 4
migrate migrate migrate
big migration … expensive!
Don’t miss migration paths!

24. Always run your TESTS against new versions

25. Another reason for being current

26. Do you really believe
those young talents
wanna work with
COBOL?
Or other OLD SHIT?

27. Tracking versions is a pain!

28. SOFTWARELIBRARIES
are NOT like iPhone
Apps!

29. 100 libraries per
project in avg.
After 2 weeks the first libraries are OUT-DATED!

30. Developers are missing critical BUGFIXES
and important UPDATES!

31. Manually checking for
updates is no fun!
!
It cost TIME & MONEY!
!
NOBODY WANTS TO DO IT!

32. So, how do you wanna solve this
PROBLEM

33. You have to
AUTOMATE

34. You need a TOOL for that!

35. !
registry.npmjs.org
!
http://search.maven.org/#api
!
https://developer.github.com/v3/
!
gradle.artifactoryonline.com/gradle/libs/
!
http://guides.rubygems.org/rubygems-org-api/
APIsforSoftwareLibraries

36. GemNotifier Gemnasium VersionEye
Languages Ruby
Ruby, Node.JS,
Python
22 Languages
GitHub no yes yes
Bitbucket no no yes
Fileupload no no yes
URLparsing no no yes
Changelogs no yes in progress
Security no yes in progress
Licenses no no yes
API no no yes

37. www.VersionEye.com
Keeps an eye on more than 335K open source libraries!
Supports 22 Languages and 10 Package Managers!

38. https://www.versioneye.com/api
API

39. https://www.versioneye.com/statistics

40. 40VERSIONEYEENTERPRISE
M2
VersionEye
Enterprise
VM
VersionEye.com
CI
Intranet
E-Mail
data sync
LDAP

41. @RobertReiz #ContinuousUpdating
Questions?