4 ms·

He talks about maintenance and making releases. Otherwise people will still deal with bugs in the "current" release that have been fixed in the master branch fo

• casion 7y ago
  That would be mismanagement (and annoying of course), not "dead" I would think?
  • nwsm 7y ago
    There is no difference for the average user. I'm not going to use the code in master, I will use a package from pip, pipenv or otherwise.
    • setr 7y ago
      And even if you did, there's no guarantee that the work in master is actually in a sane state. Some try to follow models like master is always runnable, or tested/built by ci/cd, but it's often simply not the case. I've worked on atleast a few open source projects where I'd pull and build master, trying to obtain a particular bugfix, and it would fail, and I'd have to randomly rollback commits until I found a working build. In one case the project had a seperate repo for a library that wasn't kept entirely in sync with the parent project.. had to randomly move back both repos until I found a matching pair that built and ran successfully, but after the bugfix was implemented. Releases are important for anyone who isn't working on the repository directly -- they gaurantee the project is in a sane state.
      • namibj 7y ago
        There is git-bisect for that task, fyi. If you can quickly script the build and test process, it's an easy way to not be bothered manually.