Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
Bundler hit a big milestone this year with the release of Bundler 2 🎉, but not without its bumps and hurdles. We'll look into the problems that some of our users have been experiencing after the Bundler 2 release, what the core team has been doing to fix these issues and what we've since learned. Afterwards, We'll look at the upcoming Bundler 2.1 and Bundler 3 releases.
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
The video titled "Working towards Bundler 3" presented by Colby Swandale at RubyKaigi 2019 explores the recent developments and challenges faced by the Bundler tool following the release of Bundler 2. The talk highlights the importance of Bundler in project dependency management for Ruby applications, outlining its core functionalities, including the creation of a Gemfile and resolving dependencies through the 'bundle install' command. Key points discussed in the talk include: - **Bundler's Evolution**: The core team recently released Bundler 1.17, introducing features like 'bundler remove' and improvements to 'bundle doctor'. - **Bundler 2 Release Challenges**: Issues arose after the release of Bundler 2, particularly with CI systems and breaking changes that disrupted user environments. The team faced complaints regarding the requirement of 'gem update' for RubyGems, leading to a retraction of certain version requirements. - **Communication and Transparency**: Colby emphasizes the need for open communication with users, proposing that discussions about Bundler's progress and changes should happen in public forums such as GitHub. - **Future of Bundler**: As Bundler 3 approaches, the team seeks to enhance support for CI systems, improve compatibility across platforms, and create a smoother upgrade path for users transitioning from Bundler 1. - **User-Centric Improvements**: Feedback revealed the need for Bundler to read prior Bundler 1 lock files to streamline upgrades, and improved documentation to educate users about new requirements and changes. In conclusion, Swandale expresses gratitude for the community's patience and encourages users to reach out with questions as the Bundler team continues to refine their product. The overarching goal is to facilitate better user experiences, minimize disruption due to breaking changes, and maintain effective communication throughout the development process.
Suggest modifications
Cancel
