Our Technical Editing Team maintains a list of Words to Avoid (common misspellings, terms that tend to be unclear, passive voice verbs, etc.), and there was a time when someone would occasionally point out during review that I was using a Word to Avoid in my release note. I wasn’t familiar with the contents of the list, so I decided to write the following piece to brush up… and have some fun too! (In school, I always did like making the spelling words into a story instead of just standalone sentences…) The resulting release note features over 70 unique Words to Avoid, not counting the grammar anomalies and the fact that, though it is probably three times as long as a normal release note, it barely tells you what the (fictitious) task fixed!
I originally posted A Release Note to Avoid to our internal Twiki web in June of 2007.
Night job phone call cancelling boot bug
There is a bug that only displays as soon as you start up the program, when a collector is using a non-dialing dialing campaign to pick a non-responsible responsible party and tries to do a cancelation; as well as, it also unpredictably may happen when you simply wish to rebuild indices while also deleting dependant appendices. There are two main error boxes which the error that is shown is split up into, underneath each other, and when you choose the one error you get a third catchall error. This task may not fix any of these errors, but it enables you to see any errors that might occur grouped together, which is supposed to help you to go back and figure out what you did wrong better, and so on.
Being that there are a bunch of bugs in this area of the program (like when you try to utilize the log off menu after you print out promise to pays, you can not logout; in other words when you click, the mouse goes off of the button down to the right-hand corner and you don’t see anything on your screen, and in order to go back and logon you should type a lot of angled brackets in the little box and depress RETURN, which allows you to automatically re-login, which is obviously not very intuitive), so far we only did this stuff for NT, but perhaps in the next biannual release it will be fixed for other places where may be desired (if necessary), as long as we can figure out how.