[OPEN-ILS-DEV] Big pull request - Angular acquisitions search
Hi, I would like to call people's attention to the pull request I opened just now for the Angular rewrite of acquisitions search: https://bugs.launchpad.net/evergreen/+bug/1850547 The branch (user/gmcharlt/lp1850547-angular-acquisitions-search) includes a number of changes to core Angular components, including: * a new eg-file-reader * a new eg-interval-input * various improvements to eg-combobox, including teaching it how to consistently generate display labels for certain IDL classes * various improvements to eg-grid * tweaks to eg-org-select and eg-date-select This is a big branch, but as a starting point, I would like to suggest getting the changes to the core components reviewed and merged sooner rather than later. I'm of course happy to answer questions and to help sort out any conflicting proposed changes to those components. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Supported releases
Hi, On Thu, Jul 23, 2020 at 9:34 AM Galen Charlton wrote: > - remove the 3.1.8 milestone in LP > I meant 3.3.8, of course. In any event, that milestone is now gone. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Supported releases
Hi On Thu, Jul 23, 2020 at 9:02 AM Daniel Wells wrote: > Based on feedback here and on the bug as well, I have removed the > webstaffblocker tag. Better throw that 3.1 retirement party quick before > another blocker pops up ;) > Looks like we have a consensus. Based on that, I'm going to take the following steps: - remove 3.1, 3.2, and 3.3 as active versions on the downloads page - remove the 3.1.8 milestone in LP - send a note to open-ils-general Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Supported releases
Hi, I've updated the list of supported releases at https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule 3.3 has technically hit end of life for both features and security fixes, but I have a mild itch to suggest that we do a final release of 3.3.8 to scoop up the various backports to rel_3_3, then call it a day. Thoughts? As 3.2 is now definitely out of support, I've removed it from the downloads page. I'm leaving 3.3 on the page for now pending resolution of my question above. That leaves 3.1, which is ostensibly hanging around as an LTS. Is there somebody who is interested in continuing to actively maintain it? If not, I suggest that we drop it as well. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Proposal for Evergreen 3.6
Hi Michele, On Wed, Jul 15, 2020 at 8:57 AM Morgan, Michele wrote: > Galen's message got me thinking that it might be useful if the release > team could offer an apprentice-type role, so that folks who don't feel > qualified to dive in as a manager or co-manager could gain some experience > and help out, hopefully taking a bit of pressure off the release manager(s). > > If there's room for one more in such a role I would be interested in > helping out. > Thanks for volunteering, Michele! Terran, Jason, and I would be happy to have you join the release team for 3.6. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Proposal for Evergreen 3.6
Hi, On Tue, Jul 14, 2020 at 11:34 AM Galen Charlton wrote: > On Wed, Jul 8, 2020 at 11:25 AM Galen Charlton > wrote: > >> I further propose to act as a co-release manager, and hereby issue a >> request for anybody who would be interested in acting as co-RM with me to >> get in touch. >> > > Following up on this, Jason Boyer has offered to serve as a co-RM, and > I've accepted his offer for the purpose of this proposal. However, I would > like to continue to extend the call for co-RMs, as I would like to treat > this as an opportunity for me to help mentor new release managers and > release maintainers. As a reminder, a release manager does not have to be > a core committer, but does need to be familiar with Git and have already > contributed substantially to the Evergreen project whether it be code or > documentation. In particular, one of the things that I hope to accomplish > during the 3.6 cycle is to have more RM communication take place, so > somebody with coordination and communication experience (in addition to > familiarity with the code) would be of great help. > As a further follow-up, Terran McCanna from GPLS will be joining Jason and me as co-RM. So, at this point, I propose that Jason, Terran and myself proceed as co-RMs on the schedule I suggested on 7/8. Any feedback, questions, or counter-proposals before we get started? Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Proposal for Evergreen 3.6
Hi, On Wed, Jul 8, 2020 at 11:25 AM Galen Charlton wrote: > I further propose to act as a co-release manager, and hereby issue a > request for anybody who would be interested in acting as co-RM with me to > get in touch. > Following up on this, Jason Boyer has offered to serve as a co-RM, and I've accepted his offer for the purpose of this proposal. However, I would like to continue to extend the call for co-RMs, as I would like to treat this as an opportunity for me to help mentor new release managers and release maintainers. As a reminder, a release manager does not have to be a core committer, but does need to be familiar with Git and have already contributed substantially to the Evergreen project whether it be code or documentation. In particular, one of the things that I hope to accomplish during the 3.6 cycle is to have more RM communication take place, so somebody with coordination and communication experience (in addition to familiarity with the code) would be of great help. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Proposal for Evergreen 3.6
Hi, Following up on my note last month on planning the 3.6 cycle, I propose that we adopt the following schedule for the release of Evergreen 3.6: * 2020-07-13: Formal start of 3.6 cycle * 2020-08-17 to 2020-08-21: Feedback Fest * 2020-09-08: Feature slush * 2020-09-14: Feature freeze + string slush * 2020-09-16: Beta 1 release * 2020-09-21 to 2020-09-25: Bug Squashing Week * 2020-09-30: Beta 2 release * 2020-10-07: Release candidate and string freeze * 2020-10-14: General release I further propose to act as a co-release manager, and hereby issue a request for anybody who would be interested in acting as co-RM with me to get in touch. Thoughts? Anybody else who would like to throw their hat in the ring to serve as RM? Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Leaving Calvin
Hi Remington, Thank you for all you've done for dev and DIG, and best wishes for the future. Please don't be a stranger. On a statistical note, I see that you've authored at least 183 commits in the main branch, touching 448 files. You also signed off on at least 119 patches authored by other people. Regards, Galen On Tue, Jun 30, 2020 at 11:10 AM Remington Steed wrote: > Hi Evergreen Devs, > > Today is my last day at Calvin University, and I wanted to say goodbye and > thanks. It's been great working with you all, and I've learned a lot from > you. Thanks for taking the time to answer my questions and to review my > code. Keep up the good work, and God bless. > > Remington > > -- > Remington Steed > Electronic Resources Specialist > Hekman Library, Calvin University > http://library.calvin.edu/ > -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Thoughts on Evergreen 3.6
Hi, Now that Evergreen 3.5.0 is nearly out the door, I have some thoughts on planning for 3.6. First, I suggest that we plan on a general release in October, though perhaps more like the middle of the month rather than than the beginning of it. Doing so would allow us to keep to a twice-a-year tempo and not lose momentum like we might if we skipped the fall release entirely this year. Pushing general release into November or December would run into the winter holidays. An October release would of course mean a shorter cycle, but I think we can actually work that to our advantage by having the focus of 3.6 be catching up with the backlog of pull requests, particularly ones implementing new features. At the moment, there are 52 pull requests that are signed off and 155 that are not signed off; a release that did nothing but merge a good chunk of these would nonetheless be a featureful one indeed. I'm not suggesting that 3.6 be just about the backlog; I know that Bill is suggesting that the Angular catalog become the default and that Equinox is planning on putting out big branches for the Angular acquisitions work over the next few weeks. However, an emphasis on reducing the backlog would both tidying up the bug list and deal with the fact that some features have been waiting months or years for review and merging. What do folks think? And are there people interested in proposing to become RM or co-RM for this cycle? Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Curbside pickup in Evergreen
Hi, On Wed, Jun 10, 2020 at 2:52 PM Galen Charlton wrote: > As I mentioned in the bug, we are not applying the pullrequest tag just yet pending testing by > the sponsoring library and the community, but the branch is suitable for detailed code > review and independent testing of the functionality. That testing has now concluded, so I've produced a rebased branch and added a pullrequest tag to bug 1879983: collab/gmcharlt/lp1879983_curbside_pickup_pr https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1879983_curbside_pickup_pr Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Curbside pickup in Evergreen
Hi, On Tue, Jun 9, 2020 at 4:10 PM Mike Rylander wrote: > There are currently 68 commits on the branch linked from > https://bugs.launchpad.net/evergreen/+bug/1879983 but we anticipate > creating a new, easier to follow branch in the next couple days that > will squash most of those down to just a few. We'll follow up here > again when that's complete. In the meantime, please poke at the test > server, and the extant branch if you want to see how it's working > under the covers. The clean branch is now available: working/collab/gmcharlt/lp1879983_curbside_pickup https://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1879983_curbside_pickup As I mentioned in the bug, we are not applying the pullrequest tag just yet pending testing by the sponsoring library and the community, but the branch is suitable for detailed code review and independent testing of the functionality. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Web team update request
And done! --gmc On Fri, Dec 13, 2019 at 4:11 PM Galen Charlton wrote: > Hi, > > Unless somebody just beat me to it, I'll make the update now. > > Regards, > > Galen > > On Fri, Dec 13, 2019 at 4:06 PM Bill Erickson wrote: > >> Hi >> >> Could someone with web server access please update the Evergreen >> downloads page to reflect the new version of Hatch? It's compatible with >> all versions of Evergreen, so it can replace the existing Hatch link. >> >> The new version is 0.3.2. >> >> https://evergreen-ils.org/downloads/Hatch-Installer-0.3.2.exe >> >> TIA >> >> -b >> > > > -- > Galen Charlton > Implementation and Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: g...@equinoxinitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 > -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Web team update request
Hi, Unless somebody just beat me to it, I'll make the update now. Regards, Galen On Fri, Dec 13, 2019 at 4:06 PM Bill Erickson wrote: > Hi > > Could someone with web server access please update the Evergreen downloads > page to reflect the new version of Hatch? It's compatible with all > versions of Evergreen, so it can replace the existing Hatch link. > > The new version is 0.3.2. > > https://evergreen-ils.org/downloads/Hatch-Installer-0.3.2.exe > > TIA > > -b > -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] UX - Angular grid header stickiness
Hi, I wrote a little patch for LP#1855457 [1] to make Angular grid headers in the admin interfaces sticky. Since some admin grids could have dozens, hundreds, or even thousands of rows, I think it's a nice little usability improvement. However, I'd like to raise a broader question: is there any reason why Angular grids should not default to having sticky headers? If not, changing the default value of eg-grid's stickyHeader attribute to "true" is a one-liner change that could be readily overridden for any specific grids where we don't want a sticky header for whatever reason. [1] https://bugs.launchpad.net/evergreen/+bug/1855457 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Rebooting development meeting: meeting today at 3 p.m. ET
Hi, After some months of it falling by the wayside, we will actually have a development today today at 3 p.m. ET / 1 p.m. PT in the #evergreen IRC channel. The draft agenda is here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2019-12-03 Please feel free to add to it. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] New core committer: Jeff Davis
Hi, I am pleased to announce that Jeff Davis of the BC Libraries Co-op has accepted an invitation to join the team of core committers. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Call for Release Manager nominations - Evergreen 3.5
Hi, It's now time to decide who will be Release Manager for the spring 2020 release of Evergreen, Evergreen 3.5. The Release Manager does not have to be a core committer, but does need to be familiar with Git and have already contributed substantially to the Evergreen project whether it be code or documentation. For this release, I would like to especially encourage people to put in proposals to be co-RMs. A pair of people acting as RM can of course help spread out the work, but it would also be a mechanism for somebody who has previously acted as RM to help mentor somebody who is acting as RM for the first time. Nominations (including self-nominations) are due by 11:59 PM EDT on Friday, 25 October 2019. Nominations should be made by email to open-ils-dev@list.georgialibraries.org with a Cc: to open-ils-gene...@list.georgialibraries.org. Replying to all on this email will also work. Nominees should send an email to both of the above mailing lists a statement about their relationship to the Evergreen community and their goals for the next release. The elected release manager will be expected to follow the typical schedule for a spring release but should provide information on when they intend to set specific milestones such as the beta release. If more than one candidate is nominated, an election will be held in the #evergreen IRC channel on freenode.net on 30 October at 15:00 EDT / 12:00 PDT. Everyone is invited to participate in the voting. Evergreen core committers who cannot make the meeting may submit their vote via email to the open-ils-dev mailing list. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Web Self Check Interface - Keyboard as only input
Hi, On Fri, Oct 18, 2019 at 11:17 AM Josh Stompro wrote: > Or maybe there is another approach that detects 0-9 a-z key presses/input And for users of the Code 39 symbology, '-', '.', '$', '/', '+', '%' and (*shakes fists at the heavens*) the space character. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.1 and 3.2 end of life
Hi, While editing https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule to reflect the release of 3.4.0, I noted that 3.1.x and 3.2.x have hit their official end of life. Since a number of bugfixes have already been pushed for bugs targetted to 3.1.16 and 3.2.10, I propose that the mid-October maintenance releases be the final full releases of 3.1.x and 3.2.x, with security support running through January. Are there any objections to this? I note that 3.1.x is the last release series for which we've been distributing official staff clients. I also note that it's been over 18 months since a non-incidental bugfix has been made for the XUL client. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evergreen 3.4.0 and OpenSRF 3.2.0 released
Hi, The Evergreen community is proud to announce the release of Evergreen 3.4.0. Evergreen is highly-scalable software for libraries that helps library patrons find library materials and helps libraries manage, catalog, and circulate those materials, no matter how large or complex the libraries. Evergreen 3.4.0 is a major release that includes the following new features of particular note: - Integrated carousels for the public catalog - Billings and payments can now be aged, allowing the link between a patron and their billings to be severed when a circulation is aged. - A new feature for generating print content via a server-side web service is now available that allows for centralized management of print templates. - The Booking module has been redesigned with most of its interfaces rewritten in Angular. This redesign adds - The ability to edit reservations in many screens - A new notes field for the reservations record - A calendar view in the Create Reservations Interface - A number of improvements in cataloging, including - A new ‘Cancel Edit’ button in the record merge interface - The ability to export records from a staff catalog record basket - Additional options for controlling the overlay of items during MARC Batch Import/Export - The Physical Characteristics Wizard now displays both code and label for coded values - A number of circulation improvements, including - Enhancements to the Mark Item functions - A new Action Trigger notification is available for when a patron exceeds their fines and fees limit - A new permission to control whether a staff user can create pre-cats - Improvements to the Billing Details screen - Various improvements to the experimental Angular staff catalog, including - A new record holds tab - Support for call number browsing - Support for storing a list of recent searches - Support for named catalog search templates, allowing staff to create predefined searches - A new flat text MARC editor - A variety of staff client interfaces have been rewritten in Angular, including - The Organizational Units and Org Unit Types administration pages - The Permission Group administration page - The Standing Penalties administration page - A number of Local Administration pages - A number of improvements have been made to Angular grids in the staff interface, including - support for filtering grid contents per-column - making the grid header for long/tall grids sticky - It is now possible to configure LDAP authentication to allow a user’s institutional/single-sign-on username to be different from their Evergreen username. - A new mechanism for defining configurable APIs for patron authentication, allowing external services to more flexibly and securely use Evergreen to authenticate users. The release is available on the Evergreen downloads <https://evergreen-ils.org/egdownloads/> page. For more information on what’s included in Evergreen 3.4.0, please consult the release notes <https://evergreen-ils.org/documentation/release/RELEASE_NOTES_3_4.html> or the tabular release notes summary <https://docs.google.com/spreadsheets/d/1YSYmasaqKnQBfv-2Ez4v0ZkA3KtDWWY__41QB6LQs4c/edit#gid=890440129> . Evergreen 3.4.0 requires PostgreSQL 9.6 or later and OpenSRF 3.2.0 <https://evergreen-ils.org/opensrf-downloads/> or later. The Evergreen community is also pleased to announce the release of OpenSRF 3.2.0, which adds support for Debian 10 Buster and removes support for the deprecated Apache WebSockets backend. For more information on the OpenSRF release, please consult its release notes <http://evergreen-ils.org/documentation/release/OpenSRF/RELEASE_NOTES_3_2_0.html> . Evergreen 3.4.0 and OpenSRF 3.2.0 include contributions from at least 32 individuals and 16 institutions. -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evergreen 3.4-rc available
Hi, The first (and hopefully only) release candidate for Evergreen 3.4 is now available at <https://evergreen-ils.org/egdownloads/>. Evergreen 3.4 now declares that its minimum version is OpenSRF 3.2 (for which I released a beta earlier today). This minimum requirement is mostly on account of Debian 10 Buster support, which is new in OpenSRF 3.4 and Evergreen 3.4. I would appreciate testing of the release candidate at this point, particularly for the following cases: - on Debian Buster - on a system upgraded from Evergreen 3.3.3 Because this is a release candidate, I request that commits to master be restricted to (a) patches that fix release-critical bugs and (b) updates to documentation and release notes. I have not branched rel_3_4 off yet, and will do so either when I release 3.4.0 or if a second RC becomes necessary (so as to not keep master under freeze for very long). I intend to release 3.4.0 tomorrow unless a blocker arises, but as I said, I would really appreciate thorough testing of the RC. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] OpenSRF 3.2.0-beta released
Hi, The 3.2.0-beta release of OpenSRF is now available from < https://evergreen-ils.org/opensrf-downloads/>. This release: * adds support for Debian 10 Buster * removes support for the mod_websocket backend for the WebSockets gateway * fixes a bug that cased passwords containing percent signs to not work in Evergreen Because of the addition of Debian Buster support, OpenSRF 3.2.x will become the notional minimum version of OpenSRF required for Evergreen 3.4.x. This beta release also serves as a release candidate for OpenSRF 3.2.0, which I hope to make tomorrow. At this time I would appreciate testing, particularly on Debian Buster. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Problem loading report inteface
Hi, I may have finally tracked this down. I've written up some details and put out a work-in-progress patch for testing in bug https://bugs.launchpad.net/evergreen/+bug/1845050. Regards, Galen On Sat, Jun 8, 2019 at 10:45 AM Linda Jansova wrote: > Hi,, > > We have eventually tried Evergreen 3.3.1 with Ubuntu 16.04 LTS (end of > life April 2021) and the interface loads okay (as the attached screenshot > confirms). > > So to avoid seeing a broken interface we will probably go for Ubuntu 16.04 > LTS (instead of Debian 9 or Ubuntu 18 as originally planned) on our > production server - unless there is a (hopefully simple) change to > configuration which would make the reports interface usable in Debian 9 or > Ubuntu 18 (?). > > Linda > On 6/6/19 6:41 AM, Linda Jansova wrote: > > Hi Galen, > > have you managed to sum up your findings to Launchpad yet? > > Or could you recommend a particular Ubuntu or Debian version which works > fine with the report interface and is recommended for the current Evergreen > version? > > Thank you! > > Linda > On 5/30/19 6:51 AM, Linda Jansova wrote: > > One more thing - we have also tested Evergreen 3.3.0 on Debian 9 > (Stretch), getting the same results (but this testing was performed using > our own database data and localized Evergreen, making it difficult to tell > whether either of the two aren't to blame). > > Linda > On 5/30/19 6:43 AM, Linda Jansova wrote: > > Hi Galen, > > Thank you very much for looking into this! > > Linda > On 5/30/19 12:14 AM, Galen Charlton wrote: > > Hi Linda, > > On Wed, May 29, 2019 at 2:48 PM Linda Jansova wrote: > >> So the question is - has anyone tried 3.3.1 and tried to create a report >> template folder? Or does anyone have any idea what could be wrong? (We use >> the concerto database without localization at this moment. Also, we keep >> reloading the interface and clearing the browser cache.) >> >> Thank you in advance for any ideas! >> > > In my own testing I'm seeing cases where on Debian Stretch the combination > of the Apache mod_include and mod_xmlent modules, which are used to render > the reports interface, are no longer returning the full page. Enough of it > gets returned so that you see an apparently complete interface, but not > enough of it for it to be fully functional. I am working on a writeup for > Launchpad and and hope it post it tomorrow. > > Regards, > > Galen > -- > Galen Charlton > Implementation and Services Manager > Equinox Open Library Initiative > phone: 1-877-OPEN-ILS (673-6457) > email: g...@equinoxinitiative.org > web: https://equinoxInitiative.org > direct: +1 770-709-5581 > cell: +1 404-984-4366 > > -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evergreen security releases: 3.1.15, 3.2.9, 3.3.4, and 3.4-beta2
On behalf of the Evergreen contributors, we are pleased to announce the release of Evergreen 3.1.15, 3.2.9, 3.3.4, and 3.4-beta2. The new releases can be downloaded from: http://evergreen-ils.org/egdownloads/ THESE RELEASES CONTAIN SECURITY UPDATES. It is recommended that all Evergreen sites upgrade to one of the new releases as soon as possible. These releases fix two bugs related to cross-site scripting (XSS) vulnerabilities in the public catalog. Bug 1559239: Mitigates a potential risk of having a web page location changed when opening a link in a new tab. Evergreen administrators should review whether the following templates have been customized or overridden. If so, either the template should be replaced with the stock version or the rel="noopener" attribute added to all anchor () tags with a target="_blank" attribute. Open-ILS/src/templates/opac/parts/record/summary.tt2 Open-ILS/src/templates/opac/parts/result/table.tt2 Bug 1822630: Resolves a problem with not properly sanitizing user input. When upgrading, Evergreen administrators should review whether any of the following templates have been customized or overridden. If so, either the template should be replaced with the stock version or the XSS fix (which entails adding the | html filter in several places) applied to the customized version. Open-ILS/src/templates/opac/browse.tt2 Open-ILS/src/templates/opac/parts/ebook_api/base_js.tt2 Open-ILS/src/templates/opac/parts/header.tt2 Open-ILS/src/templates/opac/parts/place_hold.tt2 Open-ILS/src/templates/opac/parts/place_hold_result.tt2 Open-ILS/src/templates/opac/parts/result/adv_filter.tt2 All of these new releases also contain bugfixes that are not related to the security issues. For more information on the changes in these releases, please visit https://evergreen-ils.org/security-releases-evergreen-3-1-15-3-2-9-3-3-4-and-3-4-beta2/ -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 beta1 available
Hi, The beta release of Evergreen 3.4 is available from https://evergreen-ils.org/egdownloads/ 3.4 is a feature release that includes: * the ability to age billings and payments when a loan is aged * the conversion of various administrative interfaces to Angular * server-managed print templates for the Angular staff interface * a variety of improvements to various Angular widgets * configurable APIs for patron authentication and retrieval * the ability to export records from staff catalog baskets * new options for importing copies via MARC Batch Import * a refresh of the Booking module that ports most of its interfaces to Angular * a new permission for creating pre-cats * various improvements to the experimental Angular staff catalog, including adding a record holds tab * carousels as a configurable built-in feature for the public catalog * various other improvements At this time, I would appreciate folks testing the beta and using Launchpad to report any problems with it. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 feature freeze
Hi, I have finished pushing the enhancements I'm going to for the feature freeze today, although other committers remain free to do any last-minute feature merges through the end of their day today. I will release the 3.4 beta tarball on Monday. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Updating feature slush deadline
Hi, To allow a bit more to make it into the release, I'm pushing the feature slush deadline back from today to Friday, 8/30 (with a practical deadline of 9/3 given the Labor Day holiday). Feature freeze (and the release of the beta) will remain as 9/6, allowing Bug Squashing Week to proceed as planned the following week. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Results of Feedback Fest #2
Hi, My thanks to all who participated in last week's Feedback Fest. A total of 140 bugs with a pullrequest tag but no signoff were on the list. Of those, 55 got substantive action and 25 bugs got their patches committed. As of now, we're at 102 pull requests without signoffs. I would like to thank the following folks who participated in Feedback Fest bugs: Jason Boyer Galen Charlton Bill Erickson Rogan Hamby Kyle Huckins Linda Jansova Tiffany Little Andrea Neiman Mike Risher Mike Rylander Jane Sandberg Chris Sharp Remington Steed Jason Stephenson Apologies if I've missed anybody. I would also like to acknowledge two people who had their first Evergreen code patch accepted during the Fest: Dan Briem Tiffany Little Details of the Fest can be found at https://wiki.evergreen-ils.org/doku.php?id=dev:3.4:feedback_fest_2 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feedback Fest #2 midweek update
Hi, As of the moment, a total of 30 of the 140 bugs on the fest's list have received substantive action and 9 have had their patches committed. My thanks to those who have participated so far. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 Feedback Fest #2: The Festening
Hi, The second and final Feedback Fest for the 3.4 cycle will take place next week (29 July through 2 August). The goal of the fest is to give feedback on each and every outstanding pull request. Feedback can take many forms, including: * rebasing older pull request branches against the current master * commenting on the bug and the proposed patches * deciding if the bug no longer applies * testing and signing off on the patches * writing automated test cases for pull requests that need them * writing human test plans * writing release notes entries While some or many of the pull requests will hopefully get signed off and merged during the fest, the primary goal is advancing each and every pull request by providing feedback. The wiki page https://wiki.evergreen-ils.org/doku.php?id=dev:3.4:feedback_fest_2 lists the 140 open bugs that have the pullrequest tag but not the signoff tag as of this afternoon. At this time I would like to ask each of the thirteen active core committers to give feedback on at least one bug a day from this list next week. That by itself would take a good chunk out of the list, but the committers can't do it alone! There are many more folks active in development work, and I ask you all to pitch in. I also encourage folks to participate loudly. What do I mean by that? Sometimes, it would be enough just to add comments in Launchpad, but sometimes a patch may have broader implications. If so, talk about it! #evergreen and open-ils-dev are available. At minimum, though, please make liberal use of Launchpad's bug assignment feature to indicate when you are working on a given bug. I'll be posting updates as the week progresses, and will not be shy about tagging people if I think they would be in a particularly good position to give feedback on a given bug. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Reminder: Evergreen Development meeting tomorrow (4 June) at 3 p.m. EDT
Hi, As a reminder, the next development meeting in #evergreen is tomorrow at 3 p.m. EDT / 12 p.m. EDT. Please feel free to update the agenda here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2019-06-04 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Problem loading report inteface
Hi Linda, On Wed, May 29, 2019 at 2:48 PM Linda Jansova wrote: > So the question is - has anyone tried 3.3.1 and tried to create a report > template folder? Or does anyone have any idea what could be wrong? (We use > the concerto database without localization at this moment. Also, we keep > reloading the interface and clearing the browser cache.) > > Thank you in advance for any ideas! > In my own testing I'm seeing cases where on Debian Stretch the combination of the Apache mod_include and mod_xmlent modules, which are used to render the reports interface, are no longer returning the full page. Enough of it gets returned so that you see an apparently complete interface, but not enough of it for it to be fully functional. I am working on a writeup for Launchpad and and hope it post it tomorrow. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Time to increase the minimum required version of PostgreSQL?
Hi, Thanks, folks. I've opened https://bugs.launchpad.net/evergreen/+bug/1830749 for bumping up the minimum to 9.6. Regards, Galen On Tue, May 28, 2019 at 9:58 AM Bill Erickson wrote: > +1 for PG 9.6 for EG 3.4. > > -b > > On Tue, May 28, 2019 at 9:06 AM Daniel Wells wrote: > >> Here's a third vote for upping to 9.6. We've been on 9.6 on Ubuntu 16.04 >> since December. No complaints. >> >> Dan >> >> On Tue, May 28, 2019 at 8:33 AM Boyer, Jason A >> wrote: >> >>> I would also shy away from making 10 the minimum for 3.4 because I worry >>> that we haven't shaken out the last compatibility issues, but I think we >>> should definitely aim for 10 or 11 for 3.5. I've been running 9.6 in >>> production since November so I would say it's a pretty safe choice to carry >>> us through 3.4. After our local upgrade to 3.3 I'm planning to hammer on >>> U18.04 and Pg10 more thoroughly. >>> >>> Jason >>> >>> -- >>> Jason Boyer >>> MIS Supervisor >>> Indiana State Library >>> http://library.in.gov/ >>> >>> > -Original Message- >>> > From: Open-ils-dev [mailto: >>> open-ils-dev-boun...@list.georgialibraries.org] On >>> > Behalf Of Jason Stephenson >>> > Sent: Thursday, May 23, 2019 3:41 PM >>> > To: open-ils-dev@list.georgialibraries.org >>> > Subject: Re: [OPEN-ILS-DEV] Time to increase the minimum required >>> version of >>> > PostgreSQL? >>> > >>> > This is an EXTERNAL email. Exercise caution. DO NOT open >>> attachments or >>> > click links from unknown senders or unexpected email. >>> > >>> > >>> > Galen, et al., >>> > >>> > I think it is too soon to require Pg 10. While we advertise Evergreen >>> as >>> > working with Pg 10, we don't actually install it on Ubnuntu 18.04 via >>> > the prerequisites. We install Pg 9.6 instead. >>> > >>> > We've found a few places already where set returning functions have >>> > caused us hangups in Pg 10. I suspect that there are more of these >>> > hanging about in the database and in the storage and possibly other >>> > code. I've been meaning to do a lot more testing with Pg 10 lately, >>> but >>> > I've been busy with other things as well. >>> > >>> > I think we should add a more comprehensive test suite to exercise all >>> of >>> > the database code, including that in the Perl. I know this overly >>> > ambitious, and I don't have a lot of time to spare to work on it, >>> > myself, so it's easy to say, isn't it? >>> > >>> > Anyway, I don't have a problem with making Pg 9.6 the minimum required >>> > version for Evergreen 3.4, even thought that means that I will have to >>> > upgrade Pg as well. >>> > >>> > Just my thoughts, >>> > Jason >>> > >>> >>> -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 Feedback Fest #1 results
Hi, My thanks to all who participated in last week's Feedback Fest. A total of 149 bugs with a pullrequest tag but no signoff were on the list. Of those, 55 got substantive action and 18 bugs got their patches committed. As of now, we're down to 121 pull requests without signoffs. I would like to thank the following folks who participated in Feedback Fest bugs: John Amundson Galen Charlton Garry Collum Dawn Dale Bill Erickson Lynn Floyd Rogan Hamby Kyle Huckins Dan Pearl Jane Sandberg Ben Shum Remington Steed Jason Stephenson Meg Stroup Cesar Velez Dan Wells Apologies if I've missed anybody. The second Feedback Fest for the 3.4 cycle is scheduled for the week of 29 July 2019. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 Feedback Fest #1 status
Hi folks, As of today, 40 of the 149 pull requests on the list for this week's Feedback Fest have received substantive feedback and/or action. Of those, 9 have been committed. Many thanks to those who have been participating in Feedback Fest and Bug Squashing Week so far. As a reminder, the list of pull requests that are part of the fest can be found at https://wiki.evergreen-ils.org/doku.php?id=dev:3.4:feedback_fest_1 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Time to increase the minimum required version of PostgreSQL?
Hi, The patch for bug 1789679 has inspired me to pose a question: is it time to bump up the minimum required version of PostgreSQL? Currently the minimum required Pg version for all supported versions of Evergreen is 9.4. The last time we changed that requirement was in September of 2017. Pg 9.4 has official PostgreSQL community support through February of 2020, less than a year away [1]. 9.5 ends in February 2021 and 9.6 in November of 2021. Here's what is currently offered by Linux distributions we care about: Debian oldstable (Jessie): 9.4 * though Jessie LTS will go end of life in June 2020 Debian stable (Stretch): 9.6 Debian testing (Buster): 11 Ubuntu 16.04LTS (Xenial): 9.5 Ubuntu 18.04LTS (Bionic): 10 However, for both Debian and Ubuntu, it's a very viable choice to use Pg's APT repositories. While the use of GROUP BY ROLLUP proposed in 1789679 is interesting, there are also more compelling reasons to upgrade: - Parallel execution of sequential scans, joins, and aggregates as of Pg 9.6 - Significant performance increases as of 9.6 - Improved query parallelism and performance improvements as of 10 - Parallelized hash joins and parallelized sequential scans - Embedded transaction support in stored procedures as of 11 I propose that for Evergreen 3.4 we increase the minimum required version to at least 9.6. We should also give serious thought to setting the minimum to 10 or even 11. Thoughts? [1] https://bugs.launchpad.net/evergreen/+bug/1789679 [2] https://www.postgresql.org/support/versioning/ Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] ON YOUR MARKS: 3.4 feedback fest #1
Hi, As previously mentioned, I'm calling a feedback fest to run next week (20-24 May) in conjunction with Bug Squashing Week. The goal of the fest is to give feedback on each and every outstanding pull request. Feedback can take many forms, including: * rebasing older pull request branches against the current master * commenting on the bug and the proposed patches * deciding if the bug no longer applies * testing and signing off on the patches * writing automated test cases for pull requests that need them * writing human test plans * writing release notes entries While some or many of the pull requests will hopefully get signed off and merged during the fest, the primary goal is advancing each and every pull request by providing feedback. The wiki page https://wiki.evergreen-ils.org/doku.php?id=dev:3.4:feedback_fest_1 lists the 149 open bugs that have the pullrequest tag but not the signoff tag as of this morning. At this time I would like to ask each of the thirteen active core committers to give feedback on at least one bug a day from this list next week. That by itself would take a good chunk out of the list, but the committers can't do it alone! There are many more folks active in development work, and I ask you all to pitch in. Of course, since many of the pull requests in question are for bugfixes, Bug Squashing Week participants will be helping out with the Feedback Fest! Feedback Fest participants will be helping out with BSW! I also encourage folks to participate loudly. What do I mean by that? Sometimes, it would be enough just to add comments in Launchpad, but sometimes a patch may have broader implications. If so, talk about it! #evergreen and open-ils-dev are available. At minimum, though, please make liberal use of Launchpad's bug assignment feature to indicate when you are working on a given bug. I'll be posting updates as the week progresses, and will not be shy about tagging people if I think they would be in a particularly good position to give feedback on a given bug. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Next development meeting: 7 May 2019
Hi, Let's get back on track with the monthly development meetings. The next one is scheduled for tomorrow, 7 May 2019, at 3 p.m. EDT / 12 p.m. PDT. The draft agenda can be found at: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2019-05-07 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3.4 release schedule
Hi, Here is the schedule I'm proposing for the 3.4 release, including feedback fests and bug squashing weeks: 2019-05-20 to 2019-05-24: combined Feedback Fest and Bug Squashing Week During this week, the idea is to hold a typical Bug Squashing Week as well as ensuring that every pending pull request gets looked it. 2019-07-29 to 2019-08-02: Feedback Fest #2 The goal of the second feedback fest is to reduce the size of the pull request queue prior to feature slush. 2019-08-23: feature slush By feature slush, every significant new enhancement meant for 3.4 should have a LP bug with a 3.4-beta1 target and have an active pull request. I reserve the right to stretch the feature slush deadline a bit for branches that are close to being ready for review. 2019-09-06: feature freeze / string slush + beta1 release After feature freeze, no additional patches that add new features should be merged. On this date, updated templates will be made available for translators; while string changes between feature freeze and the release candidate are permitted, they should be avoided if possible. A beta release will be cut that day (or if need be, on the following Monday) for the sake of the Bug Squashing Week, so unlike previous releases, the feature freeze deadline will _not_ extend into the weekend. 2019-09-09 to 2019-09-13: Bug Squashing Week 2019-09-16 beta2 release Once the second beta is released, only patches that fix bugs, resolve issues with the release, or improve translations should be merged. 2019-09-25: release candidate / string freeze Once the RC is released, only patches that resolve serious issues with the release or that improve translations will be accepted. Ideally, I18N aside, the release candidate would be identical to the general release. 2019-10-02: general release Many thanks to Terran for reviewing drafts of the schedule and confirming dates for the next two Bug Squashing Weeks. Please let me know if you have any questions or concerns about the proposed schedule. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Call for entries for the 3.4 roadmap
Hi, I've started the 3.4 roadmap page on the Evergreen wiki: https://wiki.evergreen-ils.org/doku.php?id=faqs:evergreen_roadmap:3.4 I've carried over some entries from the 3.3 roadmap that were not released with 3.3 but look likely to make it into 3.4. If you are working on a project that you expect to be ready for 3.4, please add it to the wiki page or email me the details. As a reminder, the roadmap is for projects that have people actively working on them, not wishlist items. Please submit your roadmap entries by May 4th; note that I'll start nudging the usual suspects towards the end of next week. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] New core committers named
Hi, I am pleased to announce that the Evergreen core committers have chosen to add two more people to their ranks: Jane Sandberg and Jason Boyer. Jane Sandberg works for the Linn-Benton Community College and has been active in the Evergreen community since 2015, contributing to DIG and most recently taking ownership of the booking module and spearheading its conversion to Angular. Jason Boyer works for the Indiana State Library, supporting Evergreen Indiana, and has been active for years testing and writing patches. Please join me in congratulating them. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Launchpad tags
Hi, On Tue, Apr 23, 2019 at 4:59 PM Morgan, Michele wrote:> > Regarding the tag for workstation settings, here are some example bugs it would apply to: > [snip] I think there's enough of them to warrant a separate tag. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Development hackfest at the 2019 Evergreen Conference
Hi, A development hackfest is scheduled for Wednesday, 24 April 2019, during the Evergreen Conference. It will be held in-person from 9:00 a.m. to 4:30 p.m. EDT in the Quaker Room at the Valley Forge Casino Resort. All who are interested in Evergreen Development are welcome to attend; the hackfest is not just for developers. If you are new to Evergreen development or if this would be your first hackfest, please feel free to reach out to me if you have any questions. I have created a page on the wiki for adding topics that people would like to discuss: https://wiki.evergreen-ils.org/doku.php?id=dev:hackfest:eg2019 Please feel free to edit that wiki page or email me if you would like me do so for you. If you would like to do a brief presentation during the hackfest, please indicate it on the wiki as well. Folks can participate remotely using the #evergreen IRC channel. Internet at the venue permitting, I will also set up a video conference using GoToMeeting: https://www.gotomeet.me/GalenCharlton I am planning on having the camera on the laptop that is running the videoconference be on, but I will place it so that folks can easily sit outside of the view of the camera. I will _not_ be recording the stream. If presentations get scheduled, I will announce them as far in advance as possible via #evergreen, open-ils-dev, and Twitter so that folks who may not necessarily want to hang out on the videoconference all day will have an opportunity to attend specific presentations remotely. If you have any questions about these arrangements, please let me know. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Proposal: Server Managed Print Templates
Hi Bill, On Tue, Apr 16, 2019 at 12:12 PM Bill Erickson wrote: > I have jotted some notes here: > > https://wiki.evergreen-ils.org/doku.php?id=dev:server_print_templates > > I would love hear feedback. If it the idea holds water, I'll open an LP. I think the general idea makes good sense. Some specific thoughts that occur to me: - Consistent formatting of dates and times should be considered, perhaps by adding a helper function - What are your thoughts on having (selected) additional helper functions be available to do things like fetch OU names and addresses? On the one hand, this could reduce the need to touch Angular[JS] code to add new fields to a given printout and might add some useful consistency with what's available to A/T templates. On the other hand, for the sake of responsiveness I could see an argument for making the client completely responsible for supplying all necessary data. - It occurs to me that this could readily become a basis for printing sheets of barcodes and labels, though if we go down that path, it may be necessary to teach it how to emit PDFs that are capable of having a block to print precisely positioned on the resulting sheet of paper. - Automatic migration of existing templates is probably not possible, but _something_ to help admins keep track of how far along they are with the migration would be helpful. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Proposal to serve as release manager for 3.4
Hi, I am throwing my hat in the ring to serve as release manager for Evergreen 3.4, the autumn 2019 release. I have previously served as RM for 2.10 and 3.0. I expect that one focus for 3.4 will be continuing the work of converting web staff client interfaces to Angular. I will support and encourage that work, and I have a particular interest in making the process of updating Angular and NPM dependencies be more frequent and systematic. Another topic I would like to explore during the 3.4 cycle is taking steps to make the Evergreen API easier to use for developers outside of the project. Another goal I would like to pursue is removing more of the vestiges of the XUL client. As I did during the 3.0 release cycle, I propose to post biweekly development updates to the Evergreen blog and the development mailing list. I also intend to call at least one feedback fest. As a reminder, a "feedback fest" is a week during which every pending pull request gets reviewed to either merge it or provide substantive feedback if it's not ready to be merged yet. Feedback fest would be a complement to the bug squashing weeks. As far as the release schedule is concerned, I anticipate no particular deviations from the normal autumn release schedule. If elected, I will propose a detailed release schedule during the Evergreen Conference. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Call for Release Manager Proposals - Evergreen 3.4
Hi, It's now time to decide who will be Release Manager for the autumn 2019 release of Evergreen, Evergreen 3.4. The Release Manager does not have to be a core committer, but does need to be familiar with Git and have already contributed substantially to the Evergreen project whether it be code or documentation. Proposals to serve as release manager are due by 11:59 PM EDT on Friday, 19 April 2019. Proposals should be made by email to open-ils-dev@list.georgialibraries.org with a Cc: to open-ils-gene...@list.georgialibraries.org. Replying to all on this email will also work. Proposers should send an email to both of the above mailing lists a statement about their relationship to the Evergreen community and their goals for the next release. The elected release manager will be expected to adhere to the established schedule for the release milestones. The election will be held in the Evergreen IRC channel on freenode.net on 24 April at 13:00 EDT / 10:00 PDT. I'm choosing this time to allow anybody who is attending the workshop day at the Evergreen Conference an opportunity to vote near the tail end of the lunch break. Since there will be limited time to discuss competing proposals before workshops resume at 13:30 EDT, I urge folks to use the mailing lists to ask questions of any of the proposers. Everyone is invited to participate in the voting. Evergreen core committers who cannot make the meeting may submit their vote via email to the open-ils-dev mailing list. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Remote patron authentication
Hi, On Thu, Apr 11, 2019 at 4:20 PM Jeff Davis wrote: > On 2019-04-10 2:34 p.m., Galen Charlton wrote: > "Don't allow Overdrive auth on my account" makes sense to the patron, > but gets tricky if multiple vendors are using the same HTTP basic auth > endpoint or something like that. I suppose we could add a nullable > opt_out_usr_setting field to config.remoteauth_profile and let libraries > sort out something that works for their implementation. I think that's a reasonable approach, and I agree that patrons are much more likely to think of opt-out in terms of specific services (or _all_ external service), but certainly not in terms of the endpoints. > > Two changes I would suggest are: > > > > - tossing together an Angular admin interface for managing > > config.remoteauth_profile > > I was leaving this for last, but I'll put something together. :) Thanks! > > - adding a user activity type for tracking authentication from the new > > interface > > Right now all requests are using the "remoteauth" activity type. On > reflection, you ought to be able to specify the activity type in the > authentication profile, so I'll do that. Thanks! Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Evergreen 3.2.2 OSRF search returns way more data than I need
Hi, On Wed, Apr 10, 2019 at 6:02 PM Ken Cox wrote: > The 3.2.2 server returns a lot of additional data in the search response, > like "highlight_map". The mobile apps don't need this data, and it bloats > the response substantially. Is there a customer for this additional data, > or should I file a ticket to squelch it? Can I avoid receiving it? > The consumer for the data about the query structure, including the new highlight map, is the Evergreen OPAC itself, which as the name of the key implies, uses it as part of highlighting the search term in results and details displays; it wasn't added capriciously. That said, a search API that returns just the list of bib IDs with minimal additional metadata is a reasonable request. It would be straightforward to add a key to the argument hash in the first parameter of open-ils.search.biblio.multiclass.query and friends to request that the query_struct structure not be included in the response. Such an approach should be backwards compatible, as older versions of Evergreen would just ignore a (say) suppress_query_struct:0 in the argument hash. I would be curious to hear other's feedback, including whether we might be better off in the long run providing a wrapper around open-ils.search.*.multiclass.query that just returns IDs and is explicitly designed for external clients who don't necessarily want to use the existing SuperCat APIs (as none of them to my knowledge just return bib IDs). Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Remote patron authentication
Hi, On Thu, Apr 4, 2019 at 8:10 PM Jeff Davis wrote: > > I'd like to draw attention to a new feature I've been working on, namely > improved support for remote patron authentication and retrieval: > > https://bugs.launchpad.net/evergreen/+bug/1817645 Thank you, this looks like it will be very useful. > It should be easy enough to add support for other services and > authentication methods, like EZProxy, PatronAPI, or even NCIP Lookup > User requests. It could also be extended to support more sophisticated > auth schemes. Ideally, the most common vendors and services would be > supported out of the box. Before I proceed, though, I'd appreciate any > feedback from the community on the code, the design, or the basic > approach. In particular, I have the following questions: > > - I used mod_perl to avoid introducing new dependencies. Is it the >right tool? I think it is for now. Of course, a patron authentication gateway doesn't need to be a full-blown mod_perl application, and I could envision an approach that used a lighter-weight PSGI server, but that discussion is likely best deferred until (and if) we start thinking about moving away from mod_perl entirely. > - Currently, all auth endpoints use OpenILS::WWW::RemoteAuth as the >mod_perl handler. Would it make more sense for each authentication >type to use a different handler? Using the same handler simplifies >some configuration and hopefully allows Apache processes to be reused >by different endpoints, but maybe distinct handlers are preferable. I'm in favor of a unified approach that shares as much configuration as possible. In particular, I think that might encourage tightly controlling the patron attributes that are allowed to be returned for any given authentication type. I applaud the fact that by returning only the identifier, OpenILS::WWW::RemoteAuth::Basic currently is effectively just returning a Boolean yes/no about whether the patron is authorized to use the resource. While I suspect we'll not be able to insist that a Boolean authorization decision is the /only/ response that all authentication clients will get (and LIKE IT! ;) ), centralizing retrieval of patron data in OpenILS::WWW::RemoteAuth and adding attributes to config.remoteauth_profile to control what patron fields are given to a handler may help to keep a lid on data exposure. > - Will the current design handle a high volume of patron auth requests? I would think so, at least as much as any other non-TPAC mod_perl handler. In the worst case, if the startup cost of forking Apache backends and initializing TPAC gets to be too much for a given site, the authentication handlers could be moved to a separate Apache instance similar to the old apache2-websockets instances. > - Are there any reasonable use cases that can't be accommodated by the >current design? So far, authentication profiles can restrict auth >based on home library, usergroup (by requiring a perm that is only >granted to certain usergroups), blocks/standing penalties, and >active/expired status. The only addition that immediately comes to mind might be adding a user setting that allows a patron to opt out of allowing their account to be used for remote authentication of anything else. > - To make live tests work, an endpoint for Basic HTTP authentication >will be made available at /api/basicauth by default, restricted to >local access only. Is that OK (and if not, how do we do live tests)? >Do we want to use a different URL path? I think that's OK as is. > - Is there a better way to manage the disparate authentication >requirements of library vendors? I think simply having a HTTP basic authentication handler would be huge as a first step. Two changes I would suggest are: - tossing together an Angular admin interface for managing config.remoteauth_profile - adding a user activity type for tracking authentication from the new interface Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Python binding for OpenSRF and Evergreen
Hi, Similar to the question Jason Stephenson asked about the Java bindings [1], I would like to know if anybody is actively using OpenSRF's and Evergreen's Python binding. I do know that the Python binding is a bit less dusty than the Java binding, as srfsh.py does still work. I also know that Syrup [2] uses the binding and has at least a couple active installations, although to my knowledge nobody is actively maintaining that project. I would also like to know whether anybody has any interest in becoming a maintainer for the Python binding. If so, projects include adding support for Python 3.x (and deprecating Python 2 support?) and updating the binding to support new OpenSRF features such as bundling and chunking. Regards, Galen [1] http://libmail.georgialibraries.org/pipermail/open-ils-dev/2019-February/010659.html [2] http://git.evergreen-ils.org/?p=Syrup.git;a=tree -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Maintenance on git.evergreen-ils.org
Hi, We will be performing maintenance on the community Git server ( git.evergreen-ils.org) this week to upgrade its operating system. The maintenance will take place on Tuesday, 12 February starting at 8 a.m. EST and on Thursday, 14 February starting at 8 a.m. EST. There will be outages of both Gitweb and Gitolite during the upgrades. The expected outage tomorrow is expected to be about an hour and the outage on Thursday about two hours. During the upgrades, I will provide updates in #evergreen. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] OpenSRF 3.1 beta now available.
Hi, The beta of OpenSRF 3.1 is now available for testing. Release notes: http://evergreen-ils.org/documentation/release/OpenSRF/RELEASE_NOTES_3_1_0_beta.html Download: https://evergreen-ils.org/opensrf-downloads/ This is a beta of a significant feature release, so I request careful testing across multiple platforms. Assuming no showstoppers arise, I plan to release 3.1.0 on Wednesday, 16 January 2019. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Moved: Evergreen Development Meeting - 11/6 at 2 p.m. EST
Hi, After discussion at the Hack-A-Way, I propose that we move the development meeting in #evergreen from Wednesday to tomorrow (Tuesday), 6 November 2018 at 2 p.m. EST / 11 a.m. PST / 19:00 UTC. The agenda page for the meeting can be found here; please feel free to add items: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2018-11-06 Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Call for Release Manager nominations - Evergreen 3.3
Hi, It's now time to decide who will be Release Manager for the spring 2019 release of Evergreen, Evergreen 3.3. The Release Manager does not have to be a core committer, but does need to be familiar with Git and have already contributed substantially to the Evergreen project whether it be code or documentation. Nominations (including self-nominations) are due by 11:59 PM EDT on Friday, 26 October 2018. Nominations should be made by email to open-ils-dev@list.georgialibraries.org with a Cc: to open-ils-gene...@list.georgialibraries.org. Replying to all on this email will also work. Nominees should send an email to both of the above mailing lists a statement about their relationship to the Evergreen community and their goals for the next release. The elected release manager will be expected to follow the typical schedule for a spring release but should provide information on when they intend to set specific milestones such as the beta release. If more than one candidate is nominated, an election will be held in the #evergreen IRC channel on freenode.net on 31 October at 15:00 EDT / 12:00 PDT. Everyone is invited to participate in the voting. Evergreen core committers who cannot make the meeting may submit their vote via email to the open-ils-dev mailing list. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Making 3.1 support extension plans concrete
Hi, We've discussed [1][2] the notion of extending the community support period for Evergreen 3.1 as part of easing the transition away from the XUL staff cilent, but I cannot find anywhere that we set a date on that extension. I think we should do so so that we can update the EOL page [3]. So, I've got two questions. First, are we (in particular, folks doing backports, documentation updates, and builds) ready to commit time to that? Second, what should the end date be for general support of 3.1? To make a concrete suggestion, I propose adding six months, meaning that general support would end on 2019-10-05 and security fixes would end on 2020-01-05. [1] http://evergreen-ils.org/meetings/evergreen/2018/evergreen.2018-08-08-15.00.log.html#l-117 [2] http://libmail.georgialibraries.org/pipermail/open-ils-dev/2018-August/010558.html [3] https://wiki.evergreen-ils.org/doku.php?id=dev:release_process:schedule Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] 3.2 Getting back on schedule
Hi, On Mon, Sep 17, 2018 at 4:50 PM Bill Erickson wrote: > A few web staff blockers remain. Most of them have been there for months, > though, so I don't think another few days here or there is going to make much > difference. > > If that's an unfair assessment, let me know. Of the remaining open webstaffblocker bugs, I can commit to having patches by Friday for the following ones: * https://bugs.launchpad.net/evergreen/+bug/1745427 (predict new issues defaults to previous pattern) * https://bugs.launchpad.net/evergreen/+bug/1791340 (Web Client Hourly Loan Checkin Time Wrong) * https://bugs.launchpad.net/evergreen/+bug/1789442 (Web client: When editing an hourly due date the time is automatically changed to 12:00 am) * https://bugs.launchpad.net/evergreen/+bug/1552778 (Web client check-in "effective date" and check-out "specific due date" should also include times) Note that for the two above that the fix I'm thinking of would either require an OpenSRF update, as the main change is a fix to cleanse_ISO8601, or (my preferred approach) copying cleanse_ISO8601 over to Evergreen as (say) clean_ISO8601 and updating references everywhere -- straightforward, but obviously would require a fair amount of testing across the board. I think that amelioration, if not total fixes, should be straightforward for: * https://bugs.launchpad.net/evergreen/+bug/1773191 (Untranslatable Last Billing Type values) * https://bugs.launchpad.net/evergreen/+bug/1791335 (Transferring items and vol/items does not maintain stat cats) One that has a good start by Cesar, but looks like needs more discussion is: * https://bugs.launchpad.net/evergreen/+bug/1746536 (web client: cannot edit vol/call number in item status) If folks can commit to helping out with the last three in particular and with testing patches for the first four, I think there would be benefit to delaying the RC to the 24th to make it a true release candidate. That said, this is a position I hold at +0.75, as it would be reasonable for us to also choose to make 3.2.1 a hard target for those bugs. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Informal vote to apply XUL-removal patch to 3.2
Hi, Here's my classification of the current open bugs tagged as webstaffblocker: Small (i.e., likely can be fixed in two weeks) --- https://bugs.launchpad.net/evergreen/+bug/1773191 Untranslatable Last Billing Type values https://bugs.launchpad.net/evergreen/+bug/1770959 Web staff client: strings translated via staff client are displayed untranslated https://bugs.launchpad.net/evergreen/+bug/1781641 Web Client: Cannot Override Patron Message Block https://bugs.launchpad.net/evergreen/+bug/1781235 Web Client: Sometimes Unable to Change Primary Patron Barcode within "See All" Box https://bugs.launchpad.net/evergreen/+bug/1746536 web client: cannot edit vol/call number in item status https://bugs.launchpad.net/evergreen/+bug/1745427 Web Client: Serials - Predict New Issues Defaults to Previous Pattern https://bugs.launchpad.net/evergreen/+bug/1552778 Web client check-in "effective date" and check-out "specific due date" should also include times Higher-effort - https://bugs.launchpad.net/evergreen/+bug/1511742 webclient: Need ability to type to selection in some menus Patch exists, may need some tweaks -- https://bugs.launchpad.net/evergreen/+bug/1755258 webclient: LDAP not working -- but works for stand alone client Overall, I think we can reasonably hope to resolve these over the next couple weeks, although I specifically want to call out LP#1511742 as the one bug that I think will require the most effort. Consequently, I am +1 for planning on disabling the XUL client in 3.2, especially in light of plans for extending the support period for 3.1, but do think that this decision needs to be evaluated and finalized at the end of the upcoming bug-squashing week. Regards, Galen On Wed, Aug 29, 2018 at 11:57 AM Bill Erickson wrote: >> Devs, > > I'd like to have an informal vote on whether we should remove (well, disable) > the XUL client in 3.2. Delaying the decision is complicating the release > process. If it's clear which way the wind is blowing, we can set a date for > the final vote and patching. > > Knowing what you know today about outstanding webstaff blockers (a few were > just added), would you vote to proceed with XUL removal? Can I get a show of > hands, yea or nay? > > Thanks, > > -b > -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] OpenSRF 3.1: call for roadmap entries
Hi, As discussed during the last couple dev meetings, I would like to plan on a fallish feature release of OpenSRF to be called 3.1. I've started a place for roadmap entries on the wiki: https://wiki.evergreen-ils.org/doku.php?id=dev:opensrf_roadmap The one big enhancement targeted in Launchpad is LP#1777180, Websocketd gateway support, and I believe that Mike has code underway to implement client-side chunking. Regards, Galen -- Galen Charlton Implementation and Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Dev meeting at the conference
Hi, I would like to call a brief in-person meeting tomorrow (Wednesday), say during the 3:20 p.m. afternoon break, to work out who is going to be doing what during the developers' update Thursday morning. Let's meet by the conference registration desk. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] [OPEN-ILS-GENERAL] Call for Release Manager nominations - Evergreen 3.2
Thanks, Bill. In light of the fact that Bill was the only person to put in a proposal and has served as release manager in the past, my view is that no election is needed and that Bill should be named 3.2 release manager by acclamation. Regards, Galen On Fri, Apr 20, 2018 at 11:28 AM, Bill Erickson <beric...@gmail.com> wrote: > Hi, > > I'd like to toss my hat in the ring as the Evergreen 3.2 release manager. I > have served as release manager in the past for Evergreen 2.8. It's been a > little while and the process has evolved, but I look forward to the > challenge. > > Evergreen 3.0 and 3.1 marked the transition period from the XUL client to > the browser client. For 3.2, we'll be saying farewell to the XUL client > [1]. As release manager, my primary goal will be to define the process for > retiring the XUL client and helping to see that process through. That will, > of course, include confirming that the browser client is fully up to the > task of replacing the XUL client. > > Another goal of mine is to solidify a plan for upgrading our version of > AnguarJS to Angular. This project will span multiple release cycles. For > 3.2, I hope to reach consensus on the upgrade strategy, define a project > time line, and maybe make headway on some of the code changes. > > And finally, I would like to do another Feedback Fest this summer. This is > where everyone, core committers in particular, are asked to review > outstanding pull requests and help nudge them along in a variety of ways. I > found last year's fests [2][3] to be a great way to score a lot of small > victories -- and they add up. > > As far as scheduling goes, I would follow examples from releases past, with > a September release, preceded by the various slushes, freezes, betas, and > release candidates. > > I'm happy to answer questions. > > Thanks, > > -b > > [1] > http://libmail.georgialibraries.org/pipermail/open-ils-dev/2017-August/010400.html > [2] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1 > [3] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_2 > > On Thu, Apr 5, 2018 at 3:07 PM, Galen Charlton <g...@equinoxinitiative.org> > wrote: >> >> Hi, >> >> It's now time to decide who will be Release Manager for the autumn >> 2018 release of Evergreen, Evergreen 3.2. >> >> The Release Manager does not have to be a core committer, but does >> need to be familiar with Git and have already contributed >> substantially to the Evergreen project whether it be code or >> documentation. >> >> Nominations (including self-nominations) are due by 11:59 PM EDT on >> Friday, 20 April 2018. Nominations should be made by email to >> open-ils-dev@list.georgialibraries.org with a Cc: to >> open-ils-gene...@list.georgialibraries.org. Replying to all on this >> email will also work. >> >> Nominees should send an email to both of the above mailing lists a >> statement about their relationship to the Evergreen community and >> their goals for the next release. The elected release manager will be >> expected to adhere to the established schedule for the release >> milestones. >> >> If more than one candidate is nominated, an election will be held in >> the #evergreen IRC channel on freenode.net on 25 April at 15:00 EDT / >> 12:00 PDT. >> >> Everyone is invited to participate in the voting. Evergreen core >> committers who cannot make the meeting may submit their vote via email >> to the open-ils-dev mailing list. >> >> Regards, >> >> Galen >> -- >> Galen Charlton >> Infrastructure and Added Services Manager >> Equinox Open Library Initiative >> phone: 1-877-OPEN-ILS (673-6457) >> email: g...@equinoxinitiative.org >> web: https://equinoxInitiative.org >> direct: +1 770-709-5581 >> cell: +1 404-984-4366 > > -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Today's development meeting
Hi, The minutes and log of today's meeting are now available: Minutes: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-12-13-15.02.html Log: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-12-13-15.02.log.html The next meeting is scheduled for 10 January 2018 at 15:00 ET / 12:00 PT. To submit items for the agenda, please update <https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2018-01-10>. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evergreen development meeting, 2017-12-13
Hi, The meeting that was originally scheduled for this week has been rescheduled for 13 December 2017 at 12:00 PT / 15:00 ET. If you would like to add to the agenda, please visit: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-12-13 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] For hack-a-way: Copy Alert Persistence and Suppression Matrix
Hi, Just to give folks a heads-up on something I'll be looking for testing and feedback on during Hack-a-way next week, please take a gander at LP#1676608, Copy Alert Persistence and Suppression Matrix: https://bugs.launchpad.net/evergreen/+bug/1676608 The current branch for this is http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/collab/gmcharlt/lp1676608_copy_alerts_rebase_2017_11 This has been hanging out there for a while, but missed getting baked just enough to fit into 3.0; given the implications it has for alert modals during the circulation process, I'd like to see if we can get this into master sooner rather than later to allow for plenty of testing during the 3.1 cycle. Look forward to see folks in Indy! Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Release manager election tomorrow, 25 October 2017
Hi, We have received one nomination for release manager for 3.1: http://libmail.georgialibraries.org/pipermail/open-ils-general/2017-October/014327.html We will still plan on meeting at 3:00 ET / 12:00 PT in the #evergreen IRC channel, but obviously the meeting will be a ratification rather than an election. However, please note that Dan Wells will be specifically available during the meeting to answer questions about his proposal. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Rescheduling next development meeting
Hi, On Mon, Oct 9, 2017 at 10:23 AM, Galen Charlton <g...@equinoxinitiative.org> wrote: > Normally, the next development meeting would occur on 1 November, but > since we have the hack-a-way the following week, I propose that we > move the IRC development meeting to Wednesday, 8 November at 15:00 EDT > / 14:00 CDT / 12:00 PDT — and plan on giving a general update on how > the hack-a-way has been going for the benefit of folks not physically > present in Indianapolis. Having heard no objections, I've updated the calendar. The agenda page for the November meeting can be found here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-11-08 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Rescheduling next development meeting
Hi, Normally, the next development meeting would occur on 1 November, but since we have the hack-a-way the following week, I propose that we move the IRC development meeting to Wednesday, 8 November at 15:00 EDT / 14:00 CDT / 12:00 PDT — and plan on giving a general update on how the hack-a-way has been going for the benefit of folks not physically present in Indianapolis. Please let me know if today if you have objections or counter-proposals; if there are no objections, I'll plan on updating the calendar tomorrow. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Call for Release Manager nominations - Evergreen 3.1
Hi, It's now time to decide who will be Release Manager for the spring 2018 release of Evergreen, Evergreen 3.1. The Release Manager does not have to be a core committer, but does need to be familiar with Git and have already contributed substantially to the Evergreen project whether it be code or documentation. Nominations (including self-nominations) are due by 11:59 PM EDT on Friday, 20 October. Nominations should be made by email to open-ils-dev@list.georgialibraries.org with a Cc: to open-ils-gene...@list.georgialibraries.org. Replying to all on this email will also work. Nominees should send an email to both of the above mailing lists a statement about their relationship to the Evergreen community and their goals for the next release. The elected release manager will be expected to adhere to the established schedule for the release milestones. The election will be held in the Evergreen IRC channel on freenode.net on 25 October at 15:00 EDT / 12:00 PDT. Everyone is invited to participate in the voting. Evergreen core committers who cannot make the meeting may submit their vote via email to the open-ils-dev mailing list. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Reminder: development meeting tomorrow, 4 October
Hi, Just a reminder that a development meeting is scheduled in #evergreen for tomorrow, 4 October, at 12:00 PDT / 15:00 EDT / 20:00 UTC. If you would like to add items to the agenda, please edit https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-10-04 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Freeze on master lifted
Hi, Now that Evergreen 3.0.0 is out the door, the freeze on the master branch is hereby lifted. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Last call for 3.0.0
Hi, This afternoon, I will release OpenSRF 3.0.0 and branch of rel_3_0 in preparation for the Evergreen 3.0.0 release tomorrow. If you know of any showstoppers, please speak up. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Bug targeting and merges for 3.0-rc, 3.0.0, and 3.0.1
Hi, I've sorted through the bugs currently targeted to 3.0-rc and created milestones for 3.0.0 and 3.0.1, moving most of the 3.0-rc bugs that were not already marked as fix-committed to 3.0.1. Patches I expect to merge today before handing it off to Dan Wells to build the release candidate tarball include: * updates to monolithic schema update: https://bugs.launchpad.net/evergreen/+bug/1719726 * patch to come soon to address a discrepancy in the reification of the 1069 schema update to the base schema (I'll fold this into bug 1719726) * patches to resolve other discrepancies between base and upgraded schemas (again, to be folded into bug 1719726) * the about page (bug 1718036) * release notes updates Forthcoming patches I expect to land in master between the RC and general release on Tuesday include: * a patch that will have the effect of speeding up the authority reingest * patches to resolve further minor variations between the base 3.0 schema and the results of upgrading 2.12.5 to 3.0 At this point, I am declaring a freeze on the master branch between now and general release with the following exceptions: - documentation and release notes patches - patches related to installation and upgrade issues - fixes for truly showstopper bugs Similarly, please do not target bugs to the 3.0.0 milestone unless their fixes would fall onto the list of exceptions above. I will plan on releasing 3.0.1 along with the other maintenance releases on 18 October. Also, I plan on branching rel_3_0 on Monday or Tuesday as part of the road to general release. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Olly olly oxen free - upgrade updates
Hi, On Tue, Sep 26, 2017 at 11:08 AM, Kathy Lussier <kluss...@masslnc.org> wrote: > Also, do we need to include an authority reingest in the upgrade script for > the MADS work? Yes, although it's (fortunately) something that can be deferred and run outside of the main portion of the upgrade. Regarding the general question: thanks for the feedback, folks! I've created a branch with additional improvements to the monolithic schema update script; it's available for review here: https://bugs.launchpad.net/evergreen/+bug/1719726 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Olly olly oxen free - upgrade updates
Hi, In preparation for the release candidate tomorrow, I am sending out a call for changes needed for the installation and upgrade process, particularly the schema update. I'm aware of the following so far: - a change in the works by Mike to sync up the base schema and schema updates for action.fieldset_group - chatter about adjustments for record reingest Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] OpenSRF 3.0.x and ABI changes
Hi, Following up on the vote, I've now established milestones for OpenSRF 3.0.x: 3.0-alpha = for tomorrow, 21 September 3.0.0 = for 2 October 2017 In between now and then is our chance to make C ABI changes for OpenSRF 3.0.x; while they shouldn't be invasive, given that OpenSRF 3.0.0 is going to the minimum version required for Evergreen 3.0.x, low-impact ones could go in. I'm specifically thinking of https://bugs.launchpad.net/opensrf/+bug/1702978, but if there are others that are gleams in your eye, please speak up. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Survey - version number of next major OpenSRF release
Hi, On Mon, Sep 18, 2017 at 11:25 AM, Galen Charlton <g...@equinoxinitiative.org> wrote: > Please use this brief survey to express a preference in the version numbering; > when I cut the next OpenSRF release, I will run with whatever option has the > majority of responses by 09:00 EDT on Wednesday, 20 September. The results are in; by a vote of 18 to 1, 3.0.0 was the preference. I will plan on cutting an OpenSRF 3.0-alpha to go with the Evergreen 3.0-beta2 that will be released tomorrow. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Reminder: next development meeting on 6 September
Hi, The next development meeting is tomorrow, 6 September 2017, at 15:00 EDT / 12:00 PDT in the #evergreen IRC channel. The agenda can be found here; please edit the wiki page if you'd like to add additional items: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-09-06 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feature freeze deadline is today
Hi folks, Happy Friday! Feature freeze is today, so by the end of the day in a timezone of your choosing, any new features that are going into 3.0 should be merged to master. There may be a /tiny/ amount of leeway if something that would not be generally destabilizing might not be 100% baked but could be reviewed and go in over the weekend. If you expect to need that leeway, please check in with me. There are a few potential new-featurish things that at this time I'm inclined to grant specific exceptions for and allow to be merged through mid-September. * Debian Stretch support See https://bugs.launchpad.net/evergreen/+bug/1708048. This one is a bit trickier than normal because of ldconfig changes apparently introduced in Debian 9, and might require that we have to release an OpenSRF 2.6.0 as a minimum required version for Evergreen 3.0, at least on Stretch. Nonetheless, I'm keen to have this for 3.0 rather than wait until 3.1. * General improvements to I18N tooling * Improvements to support for HTTPS-only operations (these are arguably bugfixes anyway) * Potential changes for better Hatch integration. * Cases where a (small, non-destabilizing) new feature may need to be added to the web staff client to retain parity with the XUL client. We need to be cautious about these, though. I am not planning to branch of rel_3_0 at this point, but since there already at least a couple significant branches that would benefit from thorough review during the 3.1 cycle, I may create rel_3_0 if those branches get to the point where they're ready to be merged to master. We've had a flurry of big merges the past month and will have some today, so after the dust settles, the main focus during September will need to be stabilizing master and addressing showstopper bugs in the web staff client. Today also marks string slush. After feature freeze passes, POT files will be updated so that translators can start doing their work. Once that happens, string changes should be minimized, but they are not forbidden (e.g., if a string addition is needed as part of fixing a browser client showstopper). Full string freeze will be on 27 September. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Consider a duck donning a sweater
Hi, Today marks the feature slush deadline -- by the end of the day, please have branches for non-trivial new features and/or enhancements marked with plausible pull requests. (Note that in honor of the eclipse, I will not actually be checking LP for the final set of pull requests until Tuesday morning). The purpose of feature slush is to ensure that there's (at least) about two weeks for significant or complicated branches to be tested and reviewed prior to being merged, so the deadline can be considered a bit fuzzy even beyond the leeway I'm granting until Tuesday... but the leeway isn't infinite for anything that looks like it might destabilize master too much. If you have questions about a particular branch you want to get in, please let me know. Friday, 1 September, marks feature freeze and string slush. After that day, no patches for new enhancements or features should be merged to master, though if it looks like there's stuff for destined 3.1 that shouldn't sit unmerged for too long, I may branch off rel_3_0 around that time. "String slush" means that we'll be updating strings in LP for the translators and that further string changes in master/rel_3_0 should be minimized. The full string freeze for 3.0.0 will occur on 27 September, coinciding with the release candidate. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feedback fest #2 -- Tuesday update
Hi, Today, five bugs on the feedback fest list got feedback and two of them were merged. An additional three pull requests have been added: * LP#1655158 - patron search by date of birth * LP#1624443 - Adding a duplicate title to a Temporary List causes an "Internal Server Error" * LP#1145213 - bibliographic record merge Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feedback fest #2 -- Monday update
Hi,
As of this email, between yesterday and today a total of 9 pull
requests for Evergreen (and one for OpenSRF) have received substantive
feedback and updates, with a total of 8 pull requests getting merged.
Two additional pull requests have been added to the tracker [1]:
* LP#1704873 - webstaff item print labels
This was subsequently tested and merged by Bill Erickson.
* LP#1661688 - Want easy way to clear a hold when picked up by other patron
A subtle UI issue that I'd like to highlight is getting uib-dropdown
menus to display the correct mouse cursor. Most of the time the cursor
should be a pointer, but this only happens if the menu item has a href
attribute. In particular, if the menu item only has an ng-click
attribute, the cursor defaults to a text selector (usually an I-beam).
As exemplified by Kathy Lussier's commit for bug 1706365 (and
elsewhere), adding an empty href attribute forces the correct cursor,
e.g.,
[% l('Overlay Target') %]
or
[% l('Items ...
Now that Dan Scott's patch for bug 1681095 is merged, another thing to
be aware of is that links to static assets in the public catalog and
the kid's catalog should have a cache-busting key added. For example:
https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_2
Regards,
Galen
--
Galen Charlton
Infrastructure and Added Services Manager
Equinox Open Library Initiative
phone: 1-877-OPEN-ILS (673-6457)
email: g...@equinoxinitiative.org
web: https://equinoxInitiative.org
direct: +1 770-709-5581
cell: +1 404-984-4366
[OPEN-ILS-DEV] NEXT WEEK: Second 3.0 feedback fest
Hi, Time has flown on to the second feedback fest, which is next week from 7 to 11 August! As with the May feedback fest, the goal of the fest is to give feedback on each and every outstanding pull request. Feedback can take many forms, including: * rebasing older pull request branches against the current master * commenting on the bug and the proposed patches * deciding if the bug no longer applies or (as might be the case with some XUL interfaces) can be left alone * testing and signing off on the patches * writing automated test cases for pull requests that need them * writing human test plans * writing release notes entries The wiki page https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_2 lists the 42 open bugs that have the pullrequest tag but no signoff yet. Deadlines are fast approaching for 3.0 -- with feature slush on 18 August and feature freeze on 1 September -- so this feedback fest is particularly important. I strongly encourage everybody to participate, and particularly all available committers. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond
Hi, On Thu, Aug 3, 2017 at 11:40 AM, Kathy Lussier <kluss...@masslnc.org> wrote: > This was briefly discussed during yesterday's meeting, but to properly > identify these showstopper issues, should we be setting showstopper web > client bugs to a priority of 'high' in Launchpad? Or is there another way we > should be identifying them? For now, I suggest marking them as high. There may also be a use for a releaseblocker tag or the like, but not until after the beta. >> A further implication is >> that if you want to get a particular XUL-only bugfix into Evergreen, >> you have until the 3.0.0 release candidate is cut on 27 September to >> get it in. > > I recently used a xulclient tag for bugs with a pullrequest tag where the > fix only applied to the xul client. I thought it would be useful for > identifying these bugs during the Feedback Fest where quicker action might > be needed so that they are merged before the 3.0 release. There were only > two bugs at the time, and one has since been merged. If future XUL-only bug > fixes are submitted, it might be useful to use this tag to bring some > attention to the bug before the September 27 cutoff. Sounds like a good idea to me. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Proposed XUL bugfix merge policy for 3.0 and beyond
Hi, Following the discussion during the development meeting today, here's a draft of a policy on merging XUL bugfixes once 3.0 is released, in conjunction with the planned deprecation of the XUL staff client: START Starting with the release of 3.0.0, patches that fix XUL bugs will not be merged into master or backported unless they meet one or more of the following conditions: (a) the bug is a security issue (b) the bug involves the destruction of data (c) the bug is a regression of functionality in the XUL staff client introduced by other work done to Evergreen Under no circumstances will XUL staff client feature enhancements be merged. This policy will continue through the 3.0.x and 3.1.x maintenance release cycles, and will become moot upon the release of 3.2.0, when the XUL staff client is slated to be entirely removed. --- END --- One goal of a policy like this is to minimize scarce developer time spent on fixing XUL issues in favor of having that time spent on improving the web staff client. A secondary goal is to encourage Evergreen sites to upgrade to 3.0 or 3.1 as soon as they can. An implication of this, particularly if we adhere to a strict interpretation of this policy (as I recommend we do) is that any XUL client bugs on Launchpad that don't meet any of those criteria would have their status changed to "won't fix". A further implication is that if you want to get a particular XUL-only bugfix into Evergreen, you have until the 3.0.0 release candidate is cut on 27 September to get it in. Of course, a strict interpretation of this policy presumes that showstopper issues with the web staff client are addressed by 3.0.0, or at least early in the 3.0.x maintenance release cycle. Your feedback is requested. I am intentionally circulating this to open-ils-dev first, but will subsequently make a broader announcement once we have achieved consensus here. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Today's developers meeting
Hi, On Wed, Jul 5, 2017 at 2:05 PM, Kathy Lussier <kluss...@masslnc.org> wrote: > Do people have business to discuss that would warrant rescheduling the > meeting for later in the month or should we just plan on meeting next on > August 2? The only item of business I had to discuss was the Core > Infrastructure Initiative Badge Program > (http://markmail.org/message/clei6p57ok4jcouu), but there's no reason it > can't wait until August or even just get discussed via email. I agree that we don't have (necessarily) much to discuss today, and I'm happy with skipping this month. I'm also fine with rescheduling for later this month. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Development meeting - 7 June 2017
Hi, As a reminder, the next development meeting is on Wednesday, 7 June 2017 at 15:00 EDT / 12:00 PDT in the #evergreen IRC channel. The agenda is can be found here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-06-07 Please feel free to add to the agenda. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Web Client fixes and AngularJS Best Practices
Hi, On Fri, Jun 2, 2017 at 1:48 PM, Boyer, Jason A <jbo...@library.in.gov> wrote: > To avoid being surprised by this there is a semi-official best practice of > always having a '.' in your ng-model directives (mentioned in the above > link). ([] also works because a JS array is an instance of an Array object) > So the above example would work fine if it were type="checkbox" ng-model="uiState.enabled"/> instead. Thanks for the clear description of the problem and its solution. > SO, rather than fix these on a case by case basis I thought I'd do two > things: 1, ask if there are strong opinions for / against wrapping ALL > variables used in an ng-model in an enclosing object like uiState or > similar, and 2, ask for some help in either transitioning everything over to > that OR at least fixing all of this list of 72 that are contained within a > directive that creates a child scope (it's not just ng-if!). I don't think we can avoid looking at them on a case-by-case basis (e.g., there are a few instances of ng-model="ngModel" that I don't think can just be wrapped, but I do agree that we should avoid passing primitives in via ng-model and that we should make an effort to get rid of that pattern. I suggest that you open a metabug in LP for this, include the results of a current grep of ones that should be looked at, and do a pass to see if you find ones that have user-visible consequences, as those should be prioritized. I note that the -B flag to grep (e.g., git grep -B3 -P 'ng-model="[a-zA-Z_]+"' ) can help identify cases where ng-if or other scope-creating directives are in play. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feedback fest update #2
Hi, We've made good progress. As of the moment, 29 of the 57 pullrequests on the list [1] have received feedback, and 13 of them have had their patches merged. Let's keep up the effort. I will be publishing today's weekly development blog post this evening, and 5 p.m. EDT today will be my (arbitrary) cutoff for my final report on the fest. [1] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Feedback fest update #1
Hi, As of this morning, nine of the pullrequests on the target list [1] have received substantive feedback, including two that were merged. Thanks, folks! [1] https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] NEXT WEEK: 3.0 feedback fest #1
Hi Bill, On Mon, May 15, 2017 at 1:17 PM, Bill Erickson <beric...@gmail.com> wrote: > Thanks for setting this up! Are you looking for us to update the bug list > (at https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1) as > we go or will you be maintaining that separately? Your updating the wiki as you go along would be nice (and in part, I'm hoping the achieve a solid mass of crossed-off entries, in case updating the wiki was sounding a little redundant to folks), but Andrea and I will also be maintaining it as emails come in from LP when bugs get substantive feedback. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] New feature for consideration: copy tags
Hi, I want to call attention to a new feature, copy tags/digital bookplates, that was completed by us just now. Details, including a link to the pullrequest branch, release notes, and a test plan can be found on Launchpad: https://bugs.launchpad.net/evergreen/+bug/1673857 This feature teaches Evergreen the notion of a tag that can be applied to copies; tags are distinguished from copy notes by the former being a controlled vocabulary. Copy tags are searchable in the public catalog. The particular impetus for this work is implementing a way to acknowledge donors of items in the public catalog, but I would expect that other applications can be found for this feature. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] NEXT WEEK: 3.0 feedback fest #1
Hi, As I mentioned a while back, I'm declaring next week, 15 to 19 May 2017, the inaugural feedback fest for the 3.0 cycle. The goal of the fest is to give feedback on each and every outstanding pull request. Feedback can take many forms, including: * rebasing older pull request branches against the current master * commenting on the bug and the proposed patches * deciding if the bug no longer applies or (as might be the case with some XUL interfaces) can be left alone * testing and signing off on the patches * writing automated test cases for pull requests that need them * writing human test plans * writing release notes entries While some or many of the pull requests will hopefully get signed off and merged during the fest, the primary goal is advancing each and every pull request by providing feedback. The wiki page https://wiki.evergreen-ils.org/doku.php?id=dev:3.0:feedback_fest_1 lists the 57 open bugs that have the pullrequest tag but not the signoff tag as of this morning. That's... a manageable number. At this time I would like to ask each of the eleven active core committers to give feedback on at least one bug a day from this list next week. That by itself would take us nearly all the way... but of course, there are many more folks active in development work, and I ask you all to pitch in. I also encourage folks to participate loudly. What do I mean by that? Sometimes, it would be enough just to add comments in Launchpad, but sometimes a patch may have broader implications. If so, talk about it! #evergreen and open-ils-dev are available. At minimum, though, please make liberal use of Launchpad's bug assignment feature to indicate when you are working on a given bug. I'll be posting updates as the week progresses, and will not be shy about tagging people if I think they would be in a particularly good position to give feedback on a given bug. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Evaluating alternatives to Launchpad
Hi, On Mon, May 8, 2017 at 3:43 PM, Jason Stephenson <ja...@sigio.com> wrote: > While I have been using Gitolite, I think Galen meant to say that I have > been experimenting with Gitlab: https://about.gitlab.com/ Indeed, I meant GitLab. Thanks for the correction! Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evaluating alternatives to Launchpad
Hi, During the hackfest at the Evergreen Conference there was some discussion about dissatisfaction with Launchpad, which we currently use for several project functions: * reporting and tracking bugs * managing translations, both as an interface for translators to enter their translations as well as tools for the translations to make their way into Evergreen releases The dissatisfaction, which has been building up for years, is now at the point where several folks, including myself, have decided to investigate replacing Launchpad. There is now a wiki page where folks have described both what they do and do not like about Launchpad: https://wiki.evergreen-ils.org/doku.php?id=dev:2017_new_tools This page also lists some potential alternatives for Launchpad itself as well as the combination of Gitolite and Gitweb that we currently use to manage access to our GIt repositories. The discussion thus far has been mostly among developers, but there are a number of constituencies who would be affected by a change of tools, which is why I've CCed both open-ils-dev and open-ils-general. These constituencies include: * anybody who reports bugs or wishes to know the status of them * translators and folks who manage the translation process * anybody who contributes code or documentation Consequently, I would like folks to weight in, preferably on the wiki, regarding whether Launchpad works for them or whether they seek alternatives. I would also like to send out a call for folks to stand up test systems for the alternatives that have been proposed. I know that Jason Stephenson has been experiment with Gitolite recently. The Evergreen community VM server is available as well to run test systems. The next development meeting is on 7 June 2017; I'd like to set that as an initial deadline for feedback with an aim towards getting a sense of whether to continue with the investigation. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] 3 May 2017 development meeting
Hi, The minutes and logs from today's meeting are available: http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-05-03-15.01.html http://evergreen-ils.org/meetings/evergreen/2017/evergreen.2017-05-03-15.01.log.html During the meeting we agreed to adopt a statement of the individual and collective responsibilities of the project's core committers: https://wiki.evergreen-ils.org/doku.php?id=contributing:core_committer_responsibilities Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
Re: [OPEN-ILS-DEV] Reminder: next development meeting - 3 May 2017 at 15:00 EDT
Hi, On Mon, May 1, 2017 at 4:59 PM, Galen Charlton <g...@equinoxinitiative.org> wrote: > As a reminder, the next development meeting is scheduled for this > coming Wednesday. If you have items you would like to discuss, please > add them to the agenda here: > > https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-05-03 And to correct a mistake I made in the original subject line, the meeting is at 15:00 EDT (3 p.m.) today. Apologies for any confusion I caused. Your humble and apparently innumerate RM, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Reminder: next development meeting - 3 May 2017 at 13:00 EDT
Hi, As a reminder, the next development meeting is scheduled for this coming Wednesday. If you have items you would like to discuss, please add them to the agenda here: https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2017-05-03 Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Evergreen 2.10.11, 2.11.,4 and 2.12.1 released.
The Evergreen community is pleased to announce three maintenance releases of Evergreen, 2.10.11, 2.11.4, and 2.12.1. If you upgraded to 2.12.0 from an earlier version of Evergreen, please note that Evergreen 2.12.1 contains an important fix to the new geographic and chronological term browse indexes and requires that a browse reingest of your bibliographic records be run. If your Evergreen database started at 2.12.0, the browse reingest can be skipped; if you have not yet upgraded to 2.12.x, you need run the browse reingest only once, after applying the 2.12.0 to 2.12.1 database updates. Evergreen 2.10.11 is the final regular release in the 2.10.x series. Further releases in that series will be made only if security bug fixes warrant, and community support will end on 17 June 2017. Please visit the downloads page at <https://evergreen-ils.org/egdownloads/> to view the release notes and retrieve the server software and staff clients. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Kicking off discussion on replacing Launchpad and/or Gitolite
Hi, As you all know, we have been using Launchpad for several years for bug/feature request tracking and managing our translations. Separately, we have been using Gitolite and Gitweb to manage our Git repositories. However, some dissatisfaction has been building up over the years, and during the hackfest at the 2017 EIC, we decided to start exploring alternatives. To help support that discussion, I've started a page on the wiki: https://wiki.evergreen-ils.org/doku.php?id=dev:2017_new_tools Although some potential replacements have already been identified, in the short term I suggest we focus on requirements-gathering, including identifying what we like and don't like about the current setup. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
[OPEN-ILS-DEV] Putting together the development update
Hi, For folks wanting to help out with compiling the development update for Saturday morning, let's meet in the lobby tomorrow around 11:50 or so and find a spot for a working lunch. I will also be around in the hotel lobby Friday evening after dinner to work on the slidedeck for the update. Regards, Galen -- Galen Charlton Infrastructure and Added Services Manager Equinox Open Library Initiative phone: 1-877-OPEN-ILS (673-6457) email: g...@equinoxinitiative.org web: https://equinoxInitiative.org direct: +1 770-709-5581 cell: +1 404-984-4366
