Evergreen ILS

Open Source Library Software

Downloads

Download files, Git repositories, installation instructions...

Downloads →

Documentation

Official documentation, community wiki, and other resources...

Documentation →

Get Involved

Events, mailing lists, IRC, and more. Join our community!

Community →

Evergreen 2.7.0 has been released!

Evergreen 2.7.0 has been released!

Small delay in announcing, but here we go…

Cheers and many thanks to everyone who helped to make Evergreen 2.7.0 a reality, our first official release of the 2.7 series! After six months of hard work with development, bug reports, testing, and documentation efforts, the 2.7.0 files are available on the Evergreen website’s downloads page: http://evergreen-ils.org/egdownloads

So what’s new in Evergreen 2.7? You can see the full release notes here: http://evergreen-ils.org/documentation/release/RELEASE_NOTES_2_7.html. To briefly summarize though, there were contributions made for both code and documentation by numerous individuals. A special welcome and acknowledgement to all our first-time contributors, thanks for your contributions to Evergreen!

Some caveats now… currently Evergreen 2.7.0 requires the use of the latest OpenSRF 2.4 series, which is still in its alpha release (beta coming soon). As folks help to test the OpenSRF release, this will no doubt help to make Evergreen 2.7 series better. Also, for localization/i18n efforts, there was some last minute bug finding and we plan to release updated translation files in the next maintenance release 2.7.1 for the 2.7 series.

Evergreen 2.7.0 includes a preview of the new web-based staff client code. The instructions for setting this up are being finalized by the community and should be expected for release during the next maintenance version 2.7.1 later in October.

See here for some direct links to the various files so far:
http://evergreen-ils.org/downloads/Evergreen-ILS-2.7.0.tar.gz
http://evergreen-ils.org/downloads/Evergreen-ILS-2.7.0.tar.gz.md5
http://evergreen-ils.org/downloads/evergreen-client-2.7.0_i686.tar.bz2
http://evergreen-ils.org/downloads/evergreen-client-2.7.0_i686.tar.bz2.md5
http://evergreen-ils.org/downloads/evergreen-client-2.7.0_x86_64.tar.bz2
http://evergreen-ils.org/downloads/evergreen-client-2.7.0_x86_64.tar.bz2.md5
http://evergreen-ils.org/downloads/evergreen-setup-2.7.0.exe
http://evergreen-ils.org/downloads/evergreen-setup-2.7.0.exe.md5
http://evergreen-ils.org/downloads/ChangeLog-2.6-2.7.0

Once again, a huge thanks to everyone in the community who has participated this cycle to contribute new code, test and sign-off on features, and work on new documentation and other ongoing development efforts.

Cheers,

— Ben

Evergreen to Participate in Outreach Program for Women

The Evergreen project will participate in the Outreach Program for Women, a program organized through the GNOME Foundation to improve gender diversity in Free and Open Source Software projects.

The Executive Oversight Board voted last month to fund one internship through the program. The intern will work on a project for the community from December 9, 2014 to March 9, 2015. The Evergreen community has identified five possible projects for the internship: three are software development projects, one is a documentation project, and one is a user experience project.

Candidates for the program have started asking questions in IRC and on the mailing list as they prepare to submit their applications, which are due on October 22, 2014. They will also be looking for feedback on their ideas. Please take the opportunity to share your thoughts with them on these ideas since it will help strengthen their application.

If you are an OPW candidate trying to decide on a project, take some time to stop into the #evergreen IRC channel to learn about our project and to get to know the people responsible for the care and feeding of Evergreen. We are an active and welcoming community that includes not only developers, but the sys admins and librarians who use Evergreen on a daily basis.

To get started, read through the Learning About Evergreen section of our OPW page. Try Evergreen out on one of our community demo servers, read through the documentation, and sign up for our mailing lists to learn more about the community. If you are planning to apply for a coding project, take some time to download and install Evergreen. Each project has an application requirement that you should do before submitting the application. Please take time to review that application requirement and find some way you can contribute to the project.

We look forward to working with you on the project!

Bug Squashing Day Wrap-Up

We Came, We Saw, We Squashed Bugs.

The Evergreen community held its first Bug Squashing Day August 26. The day was an opportunity for the entire community to focus on bugs: confirming bugs, coding bug fixes, testing patches, and merging signed-off patches into the core code. By the end of the day, eleven bug fixes were merged into the Evergreen core code. There were also several other bugs they made forward progress as testers provided feedback and contributors created patches. You can see a synopsis of the day’s activities in our August 2014 Evergreen Bug Squashing Day Activity sheet.

Here are some highlights from the day:

  • A total of 17 people participated in some form of bug activity during some point in the 24 hour period of August 26.
  • Six people requested sandboxes to test 11 bugs.
  • Of the seven people who were able to sign off on bug fixes, three had not previously signed off on code.
  • One patch merged into Evergreen on Bug Squashing Day came from a new contributor. Blake Henderson of MOBIUS had written fix for a bug where Fast Item Add was no longer opening a record after an item was created.
  • Another patch created during Bug Squashing Day came from new contributor, Terran McCanna, who fixed an issue where KPAC wasn’t pulling in holds notification information. Although the code was not merged on August 26, it has since been added to the core Evergreen code.
  • The oldest bug that received attention was Owning lib of asset.copy_location not visible in Item Attributes Editor UI. Chris Sharp tested the bug fix, and both he and Thomas Berezansky continued to work on code to improve the fix. This bug was initially reported in May 2011.
  • The bug with the most heat that received attention was No error message when using duplicate barcodes in Serials Batch receive interface. Jennifer Pringle tested and provided feedback on the proposed fix for this bug.

Although Bug Squashing Day officially ended August 26, the momentum continued through the 27th as patches worked on during Bug Squashing Day continued to make their way to the Evergreen working repository.

Special thanks go to Blake Henderson (MOBIUS) and Thomas Berezansky (MVLC) for setting up the Sandboxes that made it easy for many in the community to test these bug fixes, and to Justin Hopkins (MOBIUS) and Jason Stephenson (MVLC) for volunteering them. The hardware for the sandboxes was provided by MOBIUS and MassLNC.

Also, a big thank you to the people listed below who participated in Bug Squashing Day and to the institutions that employ them for supporting their efforts to improve Evergreen for everyone.

  • Thomas Berezansky, MVLC
  • Steve Callendar, Equinox
  • Sarah Childs, Hussey-Mayfield Memorial Public Library
  • Garry Collum, Kenton County Public Library
  • Martha Driscoll, NOBLE
  • Kathy Lussier, MassLNC
  • Terran McCanna, Georgia PINES
  • Christine Morgan, NOBLE
  • Michele Morgan, NOBLE
  • Dan Pearl, C/W MARS
  • Jennifer Pringle, BC LIbraries Cooperative
  • Chris Sharp, Georgia PINES
  • Ben Shum, Bibliomation
  • Remington Steed, Hekman Library, Calvin College
  • Yamil Suarez, Stan Getz Library, Berklee College of Music
  • Dan Wells, Hekman Library, Calvin College
  • Liam Whalen, BC Libraries Cooperative

Although Bug Squashing Day is over, the bug wrangling, fixing and testing doesn’t need to end. Sandboxes will continue to be available to the community beyond Bug Squashing Day. Anyone interested in testing a bug fix can submit a request with our Sandbox Request Form.