Whats up with companies?
Rails Upgrade to 4.2.2
why?
- Security
- Performance (Adequate Record, web console)
- Business Value
- Requested by Architects
Strategy
- Check the 4.2 Release Notes
- Read the Upgrade guides
- update the gems
- run the tests
Title Text
Strategy
- Get rid of all the warnings
- Map the rails changes to the broken tests and fix them
- Monkey patches
Title Text
Deployment
- QA passed
- Deployed to preview and monitor logjam for 36 hrs
- Merged to master
- Deploy
WTF?
Deployment got stuck right after trying to warm up the passenger
It took us about 2 days to
figure out what the problem was.
Broken code was already on master
Keeping master branch safe
- Deploy feature branch to production
- merge to master afterwards
So how much does an upgrade cost?
By putting off upgrades you run the risk of a security breach, you allow your application to be less performant, you hinder the ability of your developers to work quickly and effectively, and you add to your application’s future maintenance cost.
New Pagination Patterns
why?
- old pattern is about to be deprecated
- Nicer look
how?
- Short time to have it done
- Took a pull request from events as reference
- Got rid of ajax paginations (all into one pattern)
how does this looks?
deck
By Raul Galindo
