Hi Scott,
Welcome to the Bug Squashing team!
1. Yes, you can test the fix on 2.9 as long as the bug is one that
affects 2.9. When you report back on the bug, you might want to mention
which release you tested it on.
2. Yes, once you're done you can either note any problems you found on
the Launchpad bug or, if it looks good to you, you can sign off on the
bug. There are two ways to sign off on the bug:
- If you're comfortable with git, you can perform a git sign off
following the instructions at
http://wiki.evergreen-ils.org/doku.php?id=dev:git#sign-offs
- Otherwise, you can sign off on a bug by adding this exact text as a
comment: "“I have tested this code and consent to signing off on it with
my name, [enter name or consistent alias] and my email address, [enter
email address].” Also, add a signoff tag to the bug because it's an easy
way for core committers to find bugs that have already gone through some
level of testing.
It's not required, but I also recommend that you assign yourself to the
bug before testing it so that others know you are looking at it. It's no
problem if two people test the same bug, but it helps reduce duplication
of work.
Feel free to let me know if you have any other questions!
Kathy
On 03/03/2016 08:28 AM, [email protected] wrote:
Hi Kathy,
I am a newbie when it comes to Bug Squashing Day and have two questions:
1. I have access to a test server running 2.9.3. Is it okay to test on that
instead of a sandbox?
2. When I do test something, do I enter the resulting of my test into Launchpad?
Thank you,
Scott
Scott Thomas
Executive Director
PaILS / SPARK
(717) 873-9461
[email protected]
-----Original Message-----
From: Open-ils-general
[mailto:[email protected]] On Behalf Of Kathy
Lussier
Sent: Thursday, March 03, 2016 8:14 AM
To: [email protected]
Subject: Re: [OPEN-ILS-GENERAL] First Bug Squashing Day of 2016
Hi Terran,
It looks like a couple of those were merged yesterday while Galen was reviewing
code for beta release. For those that weren't merged yesterday, I can load them
on a Sandbox and put them out for general review for people who want to help
out tomorrow.
Blake and I are preparing the Sandboxes today. If there are other bugs people
want to test, please contact me directly so that I can see if we have a Sandbox
available.
Thanks!
Kathy
On 03/02/2016 06:06 PM, McCanna, Terran wrote:
For anyone who is new to Bug Squashing Day and would like to sign up for
something that should be easy to test, here are some suggestions:
(Disclaimer: I may or may not be suggesting these because I submitted
them and I'm eager for someone to test them... but they really should
be pretty easy to test!)
KPAC - Hold results screen not showing title
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1548869
Wishlist: Selfcheck Hide UI Elements until patron auth
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1466173
Wishlist: Hide OPAC footer when viewed inside staff client
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1551451
Selfcheck "Print List" for Holds view does not work
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1370694
Selfcheck: Printing Fines Prints All Open Transactions
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1551447
Seed Data Typos (Two in One)
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1517232
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1519911
Metarecord Hold Request Title Display
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1454884
Holds history displays canceled holds as active
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1275118
TPAC: Holds history pager typo
Launchpad: https://bugs.launchpad.net/evergreen/+bug/1422932
Terran McCanna
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, GA 30345
404-235-7138
[email protected]
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
[email protected]
Twitter: http://www.twitter.com/kmlussier
