dministrator
>> Equinox Open Library Initiative
>> phone: +1 (877) Open-ILS (673-6457)
>> email: jbo...@equinoxinitiative.org
>> web: https://EquinoxInitiative.org/
>>
>> On Jul 22, 2020, at 3:41 PM, Daniel Wells wrote:
>>
>> Our initial agreement
Our initial agreement was to keep 3.1 in at least a security-only support
mode until every "webstaffblocker" had been dealt with. I think we should
keep to our word on that.
There is just one open bug with that tag:
https://bugs.launchpad.net/evergreen/+bug/1773191
The bug has some movement, so
Bill,
I support these changes. It is hard to predict how much time I will have
to offer to the release, but I can at least /imagine/ I will not be totally
swamped in 15 days, so that makes it better by default than right now :)
Dan
On Tue, Mar 31, 2020 at 10:31 AM Bill Erickson wrote:
> Hi
We had talked about keeping 3.1 going until the "webstaffblocker"s were
gone. They almost are:
https://bugs.launchpad.net/evergreen/+bugs?field.tag=webstaffblocker
An alternative to fixing the remainder is to simply decide they aren't
blockers, but then we should be deliberate in doing so, I
Hello Ken,
The second argument to PCRUD should be an Evergreen JSON-style where
clause. Are you simply trying to get them all? I am actually not sure if
there is a canonical way to do that, but one thing you could do is use a
where clause which is always true, such as id != NULL, i.e.:
Hello Jane,
It looks like your issue is that the IDL is not correct. 'pickup_lib'
should be a 'has_a' relationship.
Despite the names, 'has_a' and 'might_have' are not for nullability, but
key directionality. 'might_have' would mean that 'pickup_lib' (aou) has a
key pointing back at bresv, but
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
Hello Ken,
This is an interesting problem and proposal. It might be possible to make
some improvements, but there will be certain headwinds. For example,
system-level flags (e.g. ->ischanged) are already appended to the end of
each fm object array, so even adding named fields to the "end" still
Dear Evergreen Community,
After some consideration, I am writing to offer myself as release manager
for 3.3.
Our library is an independent academic installation, and will be live on
Evergreen for 9 years this December. I served as Release Manager most
recently for 3.1, and previously for
Hello Eric,
I think you are going to need a conduit which allows you to have a stateful
OpenSRF session connection, and the OSRF gateway doesn't do that. You are
going to want to use either osrf-websocket-translator (more modern)
or osrf-http-translator to do what you are trying to do.
I'm +1 for removal. I think the 3.1 extension provides both a usable
safety valve and adequate incentive to clear the webstaff blockers in a
timely manner.
Dan
On Wed, Aug 29, 2018 at 1:40 PM, Boyer, Jason A
wrote:
> I'm also +1 for removal. We've been planning for it since 3.0; may as well
>
Dear Evergreen Community,
I am writing to offer myself as release manager for 3.1. The following
proposal may seem familiar, as it borrows heavily from my offer for 3.0 :)
Our library is an independent academic installation, and will be live on
Evergreen for 8 years this December. I served as
Dear Friends,
There have been, and may always be, a variety of paths for getting
Evergreen. Oldest and truest of these remains the (mostly) monthly builds
available from the evergreen-ils.org downloads page.
Despite being a community flush with automation experts of various sorts,
these builds
Hello all,
Since our project adopted the idea of "release managers" in 2012, we have
managed to select each by consensus. While we typically had elections, the
nominees until now have always run unopposed.
I find this tradition to be a beautiful thing, and one I would like to see
preserved for
[I apologize for possible duplication; my calvin.edu email is getting
"greylisted" by the mailing list, so I am sending this a second time from
Gmail.]
Dear Evergreen Community,
I am writing to offer myself as release manager for the upcoming 3.0
release.
Our library is an independent academic
15 matches
Mail list logo
