Every feature on the Acrobat list had been merged by 14 October, and each had left a short tail of review comments that were accepted as follow-ups rather than blockers. With the owner’s standing order to keep working, the manager dispatched them all at once: one branch each for editing, signing, and scanning, plus the fill-from-saved-answers feature and a sweep of the first build the owner had actually used.
The follow-ups that merged
The editing branch landed first. Comments, stamps, print, and export each picked up the fixes their reviewers had asked for, none of them individually worth an entry and all of them the kind of thing a user notices on the second day.
The sweep
The quality sweep was the first time anyone sat down with a shipped build and used it as a person would, rather than testing a feature. It found six bugs and nine smaller observations. Deleting a double space ate one character too many. A file locked by a certificate was described as damaged, which it is not. Toast messages that should have cleared themselves stayed on screen. All of it was fixed in one branch and merged the same day.
Still in review
Two branches are on their second round of fixes. The scanning one changes how Compare pairs pages, by text rather than position, makes the batch runner fail closed, and lets compression work on an encrypted file. The signing one adds a checker for changes made to a document after it was certified. Its reviewer found several ways a later change could hide behind a certified signature, and every one has been closed. The details stay in the review record, not here.
A note on the tooling
The project’s manager keeps each builder in its own working copy of the repo. On 15 October a cleanup in one of those copies reached through a link into the main checkout and emptied its installed dependencies, which cost an hour and a reinstall. It is the kind of mistake that is only made once.