Discussion:
[OPEN-ILS-GENERAL] Evergreen Bug Squashing: July 17-21
Terran McCanna
2017-07-05 17:17:53 UTC
Permalink
Hello everyone,

Our next community-wide Bug Squashing Week is scheduled for *Monday, July
17 through Friday, July 21, 2017*.

(Don't worry, you don't need to set aside the entire week to participate -
you can participate however much that you can fit into your schedule.)

You may participate in Bug Squashing Day by:

- Submitting new bug fixes for reported bugs
- Testing bug fixes that others have submitted (these should have the
"pullrequest" tag)
- Confirming bug reports that haven't been reviewed yet (this is a great
way to participate if you're not a coder!)
- Pushing bug fixes into Evergreen (for core committers)
- Assisting with documentation updates

Bug Squashing Day Info and Guidelines:
http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing

If you would like to request a sandbox (test server) to test bug fixes on
please fill out the this form by Wednesday, July 12:
http://bit.ly/2tMCXiD


Please let me know if you have any questions.

Thank you!
Jennifer Weston
2017-07-05 19:40:21 UTC
Permalink
Hi Terran,

I am getting my stuff together to be able to participate next week. I just created a Launchpad account and requested to be added to the Bug Wranglers Team. I think this is what I need to be able to mark a bug as confirmed during testing or to add myself to the “Assigned To” field on bugs that are ready for testing. Is there any other kind of permission I need to request at this time? I am delaying my request for a sandbox until my permissions are place.

Thanks for the guidance,
Jennifer

Jennifer Weston
Davidson County Public Library
Technical Services Manager
***@davidsoncountync.gov<mailto:***@davidsoncountync.gov>
(336) 242-2941

From: Open-ils-general [mailto:open-ils-general-***@list.georgialibraries.org] On Behalf Of Terran McCanna
Sent: Wednesday, July 5, 2017 1:18 PM
To: Group, Evergreen <open-ils-***@list.georgialibraries.org>; List, Evergreen <open-ils-***@list.georgialibraries.org>
Subject: [OPEN-ILS-GENERAL] Evergreen Bug Squashing: July 17-21

Hello everyone,
Our next community-wide Bug Squashing Week is scheduled for Monday, July 17 through Friday, July 21, 2017.
(Don't worry, you don't need to set aside the entire week to participate - you can participate however much that you can fit into your schedule.)
You may participate in Bug Squashing Day by:

- Submitting new bug fixes for reported bugs
- Testing bug fixes that others have submitted (these should have the "pullrequest" tag)
- Confirming bug reports that haven't been reviewed yet (this is a great way to participate if you're not a coder!)
- Pushing bug fixes into Evergreen (for core committers)
- Assisting with documentation updates

Bug Squashing Day Info and Guidelines:
http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
If you would like to request a sandbox (test server) to test bug fixes on please fill out the this form by Wednesday, July 12:
http://bit.ly/2tMCXiD


Please let me know if you have any questions.
Thank you!

________________________________

If you are not the intended recipient, you must destroy this message and inform the sender immediately. This electronic mail message and any attachments, as well as any electronic mail message(s) sent in response to it may be considered public record and as such subject to request and review by anyone at any time. It also may contain information which is confidential within the meaning of applicable federal and state laws.

Davidson County Government, PO Box 1067, Lexington, NC, USA, www.co.davidson.nc.us
Kathy Lussier
2017-07-05 20:07:09 UTC
Permalink
Hi Jennifer,

Anyone with a Launchpad account can mark a bug confirmed or assign
themselves to the bug. No special permissions are required,

I hope this helps!

Kathy
Post by Jennifer Weston
Hi Terran,
I am getting my stuff together to be able to participate next week. I
just created a Launchpad account and requested to be added to the Bug
Wranglers Team. I think this is what I need to be able to mark a bug
as confirmed during testing or to add myself to the “Assigned To”
field on bugs that are ready for testing. Is there any other kind of
permission I need to request at this time? I am delaying my request
for a sandbox until my permissions are place.
Thanks for the guidance,
Jennifer*
*Jennifer Weston
Davidson County Public Library
Technical Services Manager
(336) 242-2941
*From:*Open-ils-general
Of *Terran McCanna
*Sent:* Wednesday, July 5, 2017 1:18 PM
*Subject:* [OPEN-ILS-GENERAL] Evergreen Bug Squashing: July 17-21
Hello everyone,
Our next community-wide Bug Squashing Week is scheduled for *Monday,
July 17 through Friday, July 21, 2017*.
(Don't worry, you don't need to set aside the entire week to
participate - you can participate however much that you can fit into
your schedule.)
- Submitting new bug fixes for reported bugs
- Testing bug fixes that others have submitted (these should have the "pullrequest" tag)
- Confirming bug reports that haven't been reviewed yet (this is a
great way to participate if you're not a coder!)
- Pushing bug fixes into Evergreen (for core committers)
- Assisting with documentation updates
http://wiki.evergreen-ils.org/doku.php?id=dev:bug_squashing
If you would like to request a sandbox (test server) to test bug fixes
http://bit.ly/2tMCXiD
Please let me know if you have any questions.
Thank you!
------------------------------------------------------------------------
If you are not the intended recipient, you must destroy this message
and inform the sender immediately. This electronic mail message and
any attachments, as well as any electronic mail message(s) sent in
response to it may be considered public record and as such subject to
request and review by anyone at any time. It also may contain
information which is confidential within the meaning of applicable
federal and state laws.
Davidson County Government, PO Box 1067, Lexington, NC, USA,
www.co.davidson.nc.us
--
Kathy Lussier
Project Coordinator
Massachusetts Library Network Cooperative
(508) 343-0128
***@masslnc.org
Twitter: http://www.twitter.com/kmlussier
Loading...