Hello all, In the past we were all putting bug numbers in our updatedatabase messages like this: Upgrade to 3.09.00.034 done (Bug 8207: correct typo in authority types) But more and more I'm seeing this: Upgrade to 3.09.00.035 done (Adding PrefillItem and SubfieldsToUseWhenPrefill sysprefs) When documenting new features I often need to refer to the bug report to get more information but without the bug number I have to do searches to find the right bug and it can sometimes be easy - but sometimes not so much. Can we start putting our bug references in our updates? Thanks in advance, Nicole C. Engard Documentation Manager
Hi, On Mon, Sep 24, 2012 at 12:15 PM, Nicole Engard <nengard@gmail.com> wrote:
When documenting new features I often need to refer to the bug report to get more information but without the bug number I have to do searches to find the right bug and it can sometimes be easy - but sometimes not so much.
Can we start putting our bug references in our updates?
+1 -- Galen Charlton Director of Implementation Equinox Software, Inc. / The Open Source Experts email: gmc@esilibrary.com direct: +1 770-709-5581 cell: +1 404-984-4366 skype: gmcharlt web: http://www.esilibrary.com/ Supporting Koha and Evergreen: http://koha-community.org & http://evergreen-ils.org
Can we start putting our bug references in our updates?
I agree, and would add that there's no reason to hold back in your database update description. If the bug number and title don't describe well enough, elaborate. -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
participants (3)
-
Galen Charlton -
Nicole Engard -
Owen Leonard