Description

In the past several years, Git has become the version control system (VCS) of choice for Open Source Software (OSS) developers — both those directly contributing to OSS as well as those consuming it. For those coming from other VCS backgrounds, or those new to maintaining projects, Git is not the full answer to maintaining a project. In this session, we’ll look at some common problems that occur when maintaining a project. For example: how is maintenance separated from feature development, and how are changes kept in sync between them? How can you handle security patches when working on a public repository? What happens when you need to revert a patch? How do you indicate a release? How do you ensure quality for incoming patches? On top of this, many of these tasks are quite repetitive, and yet require verbose commands to accomplish. Each of these questions has several answers. In this session, we’ll look at the tools and processes that have enabled me to be successful as a top 10 GitHub maintainer, and how you can use them to make your repository maintenance simpler, whether you maintain an OSS project or your internal projects.