General Dickimaw Books FAQ
Sometimes a bug looks like it can be quickly fixed by just adding or modifying one line of code. However, there can be a delay in fixing the issue for one or more reasons.
Any change made needs to be evaluated to determine whether or not it will have unwanted side-effects. Whenever I update a package, I run a suite of tests to make sure none of my test documents break following the change. Once the package is ready, there are further tasks, such as ensuring the version number and date is updated for every file in the distribution as well as updating the CHANGES file. The package then needs to be bundled up for distribution and double-checked before uploading to CTAN.
For a simple one-line edit, the entire process can take around 15 minutes in total. The problem is, this issue may not be the only issue that needs fixing and this package may not be the only package that has a little issue that needs fixing.
The bug report may have come in after I had started working on a new version of the package. The bug may well be quick to fix, but the package can’t be uploaded until the updates that have been started have been completed, otherwise the new version of the package will be broken.
The bug report may have come in while I’m away, ill, busy with higher-priority tasks, or otherwise too tired to have the concentration to ensure I don’t break things while making modifications.
If you’re working on a mission-critical document, consider hiring a consultant rather than relying on a hobbyist.
2022-02-28 15:33:05
Permalink: https://www.dickimaw-books.com/faq.php?id=264
Alternative link: https://www.dickimaw-books.com/faq.php?itemlabel=bugfixing
Category: General Dickimaw Books
Topic:
(La)TeX