We have ambitious plans for Evergreen 3.0. Not only will it mark the first release where the community will fully support production use of the web staff client, a number of new features are in the works, including copy tags, batch patron editing, and support for performing ebook circulation transactions directly in the public catalog. A full list of the planned features can be found on the roadmap. (And if you have any other features in the works, please add them to the roadmap by the end of the day on 14 April.)

In addition, some things will be going away. The open-ils.permacrud service, a Perl predecessor to open-ils.pcrud that is barely used, will be removed outright. The XUL staff client will still be present in 3.0, but it will be deprecated, and is slated to be removed in the Fall 2018 release.

Some changes to the project’s development infrastructure may happen as well during the 3.0 cycle. In particular, there was a discussion at the hackfest during the Evergreen International Conference last week about possibly replacing Launchpad for bug tracking with something that manages both our Git repositories and issue tracking. If you have thoughts on the matter, please add them to the wiki page where we’re discussing this.

Speaking of the conference, several presentations touched on development, documentation, and translation matters. Here’s a list of the ones for which slides are available as of this writing:

• ¿Cómo se dice? Experiences in Translating Evergreen
  • Adam Bowling (Emerald Data Networks), Terran McCanna (PINES), Chris Sharp (PINES, Ben Shum (Evergreener.net)
• ASCIIDOC: Everything You Need to Know
  • Lynn Floyd (SCLENDS)
• Happy Hatch’s Hoppalong Hootenanny
  • Bill Erickson (King County Library System)
• There’s Gold in Them Thar Nooks and Crannies: Unveiling Hidden Things in Evergreen
  • Galen Charlton (Equinox Open Library Initiative)
• We Aim to Misbehave: Making the Catalogue a Progressive Web App
  • Dan Scott (Laurentian University)

As of this writing, 13 patches have been committed to the master branch since 6 April 2017. It may be useful to mention how I arrived at this number. I ran git log --pretty="%cd %s" --date short --since '2017-04-06 23:59:59' origin/master. Breaking this down, git log is the command that lists the history of Git commits in a branch; --pretty="%cd %s" says to output the commit date (%cd) and subject line (%s); --date short says to format the date like YYYY-MM-DD; --since '2017-04-06 23:59:59' says to include only commits applied since that time; while origin/master is the branch to report on. (I did a git fetch origin first). The output ended up being:

2017-04-12 LP#1670425: RTL improvements to new advanced search limiter block
2017-04-12 LP#1670425: Adjust the release notes entry to reflect changes
2017-04-12 LP#1670425: New responsive design for advanced search limiters block
2017-04-12 LP#1670425: Moving display of advanced search limiters on search results page
2017-04-12 LP#1665933: describe the new -x option when running -h
2017-04-12 LP 1665933: Skip XUL staff client build in make_release.
2017-04-11 LP#1680624 Remove bower packaging bits
2017-04-11 LP#1680624 angular-ui-bootstrap stopped shipping minified files
2017-04-11 LP#1680624 Consolidate package dependencies into package.json
2017-04-11 LP#1680312: Fix IDs for 950.data.seed-values.sql for i18n
2017-04-11 LP#1680312 Ensure oils_i18n_gettext keys are unique
2017-04-10 LP#1677416: unbreak use of egOrgSelector by egEditFmRecord
2017-04-10 LP#1167541: Use Patron home org for pickup lib instead of staff's

Duck trivia

For 22 years, Cincinnati (across the river from where the 2017 Evergreen International Conference was held in Covington, Kentucky) has held a Rubber Duck Regatta benefiting a local food bank.

Submissions

Updates on the progress to Evergreen 3.0 will be published every Friday until general release of 3.0.0. If you have material to contribute to the updates, please get them to Galen Charlton by Thursday morning.