Hello everyone, Participants in previous Evergreen Bug Squashing Days have mentioned that it's difficult for many problems to be resolved, tested, and merged in a single day, and I've also heard from people who have work conflicts on the selected dates, so we're going to try the next one for a week!
(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.) So, our first Bug Squashing Week will be *Monday, February 27 through Friday, March 3*. 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 I will send out info regarding sandboxes for testing and how to assign yourselves to bugs two weeks before Bug Squashing Week begins. Please let me know if you have any questions. Thank you!
_______________________________________________ OPEN-ILS-DOCUMENTATION mailing list OPEN-ILS-DOCUMENTATION@list.georgialibraries.org http://list.georgialibraries.org/mailman/listinfo/open-ils-documentation
