| Time |
Nick |
Message |
| 01:02 |
|
alynn26_away joined #evergreen |
| 03:40 |
|
alynn26 joined #evergreen |
| 06:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 06:40 |
|
alynn26 joined #evergreen |
| 07:15 |
|
rjackson_isl_hom joined #evergreen |
| 07:27 |
|
collum joined #evergreen |
| 07:46 |
|
Dyrcona joined #evergreen |
| 08:23 |
|
rfrasur joined #evergreen |
| 08:36 |
|
mmorgan joined #evergreen |
| 08:53 |
|
mantis1 joined #evergreen |
| 09:40 |
|
rfrasur joined #evergreen |
| 10:10 |
|
Cocopuff2018 joined #evergreen |
| 10:18 |
|
collum joined #evergreen |
| 10:45 |
|
Cocopuff2018 joined #evergreen |
| 11:05 |
Dyrcona |
Whee! Fun with autovacuum apparently impacting performance. We have a long running autovacuum on the hold copy map and people are having trouble printing their pull lists. If I cancel it, it comes right back. I suspect it may have something to do with transaction wraparound, but I've found no evidence of that in the database, logs, nor process titles. (It's supposed to be indicated if autovacuum runs to prevent TXID wraparou |
| 11:55 |
berick |
mmorgan++ |
| 12:02 |
|
jihpringle joined #evergreen |
| 12:07 |
|
dickreckard joined #evergreen |
| 12:47 |
|
rfrasur_ joined #evergreen |
| 13:22 |
|
tlittle joined #evergreen |
| 13:24 |
csharp |
Dyrcona: I've been there - yeah, it's probably approaching a thresholds, but that should be noted in the logs |
| 13:24 |
csharp |
er.. a *threshold* |
| 13:25 |
csharp |
it brought PINES to a crawl years ago when we were still on spinning rust and not hardware-optimized for PG |
| 13:26 |
Dyrcona |
csharp: Yeah. Nothing about "wraparound" in the logs, process titles, or pg_stat_activity. |
| 13:26 |
csharp |
also, I *think* autovac can be tweaked with a reload but I'm not sure |
| 13:27 |
Dyrcona |
It keeps coming back, though. I've got two autovacuums that run recurrently: action.hold_copy_map and action_trigger.event. |
| 13:27 |
Dyrcona |
The first runs just over an hour and the latter about 2.5 hours. I think we're just extra busy with holds today. |
| 13:29 |
csharp |
btw, https://bucardo.org/check_postgres/ is great for monitoring and ad hoc checking of PG health |
| 13:29 |
csharp |
in case you weren't familiar |
| 13:29 |
|
sandbergja joined #evergreen |
| 13:30 |
sandbergja |
We are seeing some patrons whose holds are Suspended, but they didn't necessarily mean them to be. Could they have just checked the "Suspend" box on the hold form without realizing what it did? Or are there other potential causes I should investigate? |
| 13:32 |
tlittle |
Is there any other EDI segment other than the NAD+BY where Evergreen might be pulling the buyer_san from? Or anything else that might be in play besides EDIReader.pm? Ingram is putting the account number in the NAD+BY::91, and I have multiple accounts where that's linking fine to the correct org unit, and one new one where it doesn't work and I |
| 13:32 |
tlittle |
cannot find any difference between them. Why does it work for almost all of them, when it looks like EDIReader.pm is only looking for the org unit SAN in the NAD+BY and that's not there? Gah. |
| 13:33 |
sandbergja |
tlittle: that sounds familiar, let me check my email |
| 13:34 |
Dyrcona |
sandbergja: Staff may have suspended them. Also, have you done any database updates to suspend holds because of the pandemic? |
| 13:34 |
tlittle |
Oh, thank you, sandbergja ! |
| 13:35 |
sandbergja |
tlittle: I see something about SANs in the :31B |
| 13:37 |
sandbergja |
Dyrcona: good point! Probably time for some staff education about suspended holds. I could see us clicking on that without really understanding it. We haven't done any mass hold suspending, but that doesn't mean that somebody else in the consortium didn't do something similar and it hit us by mistake... |
| 13:38 |
sandbergja |
tlittle: is that for ORDRSP or INVOIC messages? |
| 13:38 |
tlittle |
sandbergja hmm. This is for INVOIC messages |
| 13:40 |
sandbergja |
The issue we ran into was that our vendor was putting our SAN in NAD+BY+[SAN]::92 in INVOICs, which doesn't work |
| 13:40 |
sandbergja |
We asked them to do NAD+BY+[SAN]::31B instead, and then INVOICs started getting connected correctly |
| 13:41 |
sandbergja |
No idea if that is relevant to your situation or not... |
| 13:42 |
tlittle |
See, I don't see the SAN at all in the NAD+BY in these files. It's in the header, but not in the NAD+BY. And I have like 10 accounts where that works just fine and everything connects. But I add this one new account and it's not working. I see no difference in the way they've formatted this invoice message vs. those other accounts, or the way that |
| 13:42 |
tlittle |
the org units are set up. I am totally stumped (a) why it works at all, and (b) why it works for most of them but not this one |
| 13:43 |
sandbergja |
:-( :-( :-( |
| 13:43 |
tlittle |
Thank you for looking for me, though! EDI is just deciding to be a real special snowflake, bless its heart... |
| 13:43 |
sandbergja |
edi-- |
| 13:54 |
sandbergja |
tlittle: do you have access to run the edi_reader support script? |
| 13:54 |
sandbergja |
in the test folder |
| 13:54 |
sandbergja |
this doodad: https://github.com/evergreen-library-system/Evergreen/blob/master/Open-ILS/src/support-scripts/test-scripts/edi_reader.pl |
| 13:54 |
csharp |
pretty sure she does... |
| 13:55 |
tlittle |
Ooh, interesting. |
| 13:55 |
csharp |
I may have added a bash wrapper for that |
| 13:55 |
tlittle |
csharp oh, excellent |
| 13:55 |
sandbergja |
Oh, nice! I have only used it once or twice (putting the EDI message into a text file, and then running edi_reader.pl [edi_filename]) |
| 13:56 |
sandbergja |
but maybe it will help in seeing the EDI message through Evergreen's eyes, so to speak |
| 13:56 |
tlittle |
sandbergja That's a great idea, I will totally try that |
| 13:56 |
tlittle |
sandbergja++ |
| 13:56 |
csharp |
oh - I'm thinking of the EDI order pusher in test mode |
| 13:57 |
csharp |
easy enough to do though, probably |
| 13:58 |
pinesol |
[evergreen|Bill Erickson] LP1846042 Angular grid filters display streamlining - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=dfa5de2> |
| 13:58 |
pinesol |
[evergreen|Galen Charlton] LP#1846042: turn on grid filtering for Angular admin pages - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=770689d> |
| 13:58 |
pinesol |
[evergreen|Galen Charlton] LP#1846042: take advantage of ngbDropdown container="body" - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=33f9590> |
| 13:58 |
pinesol |
[evergreen|Bill Erickson] LP1846042 Angular grid filter dropdown improvements - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d179394> |
| 14:12 |
sandbergja |
tlittle: now that I look closer, that script is more or less the same as what you'd find in the JEDI column/field of the EDI messages interface |
| 14:15 |
tlittle |
sandbergja Ah, gotcha. I think csharp has solved it, though! And it's because I can't read, so...sorry for the shade, EDI. Ingram isn't sending a SAN in the NAD+BY, so it looks like it falls back on the vendacct in the EDI account, and the vendacct they're sending is wrong. *sigh* |
| 14:15 |
sandbergja |
csharp++ |
| 14:17 |
tlittle |
csharp++ |
| 14:20 |
csharp |
I'll confirm that for future log readers - if the buyer_san is undef, as it is in Ingram's case, it looks up the EDI account by the buyer_acct (NAD+BY+{buyer_acct}::91) which would be located in acq.edi_account.vendacct |
| 14:50 |
JBoyer |
FYI: Dev meeting in 10 mins |
| 14:55 |
|
terranm joined #evergreen |
| 15:04 |
JBoyer |
Fine, let's call it 15. |
| 15:04 |
berick |
:) |
| 15:04 |
csharp |
:-) |
| 15:04 |
mmorgan |
tick tock |
| 15:05 |
JBoyer |
#startmeeting 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05 |
| 15:05 |
pinesol |
Meeting started Tue Jan 5 15:05:10 2021 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:05 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:05 |
|
Topic for #evergreen is now (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 15:05 |
pinesol |
The meeting name has been set to '2021_01_05___developer_meeting__agenda_available_at_https___wiki_evergreen_ils_org_doku_php_id_dev_meetings_2021_01_05' |
| 15:05 |
JBoyer |
#topic Introductions |
| 15:05 |
|
Topic for #evergreen is now Introductions (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 15:05 |
JBoyer |
Hello, hello |
| 15:05 |
JBoyer |
#info JBoyer = Jason Boyer, Equinox |
| 15:05 |
csharp |
#info csharp = Chris Sharp, GPLS |
| 15:05 |
miker |
#info miker = Mike Rylander, EOLI |
| 15:05 |
sandbergja |
#info sandbergja = Jane Sandberg, Linn-Benton Community College |
| 15:05 |
mrisher |
#info mrisher = Mike Risher, KCLS / Catalyte |
| 15:05 |
csharp |
eeeeoooliolioliooo |
| 15:05 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:05 |
berick |
#info berick Bill Erickson, KCLS |
| 15:06 |
JBoyer |
ok, anyone coming in later feel free to info-in then. |
| 15:06 |
JBoyer |
#topic Action Items from Last Meeting |
| 15:06 |
|
Topic for #evergreen is now Action Items from Last Meeting (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 15:06 |
JBoyer |
#info Dyrcona to assign release dates in Launchpad for 3.6.2, 3.5.3, and 3.4.6 releases |
| 15:07 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
| 15:07 |
Dyrcona |
That's done, btw! |
| 15:07 |
JBoyer |
Dyrcona++ |
| 15:07 |
JBoyer |
I thought I remembered seeing that. |
| 15:08 |
JBoyer |
In the interest of time, are there any updates for Evergreen, OpenSRF, or Hatch releases? There's nothing on the agenda so unless someone has a last minute EUREKA I'm going to skip them all |
| 15:08 |
JBoyer |
(or Docs) |
| 15:08 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:09 |
berick |
just noting we're < 2 months from 3.7 feature freeze |
| 15:09 |
JBoyer |
Alright. I also see that where mmorgan did the thing and updated the agenda, I did not update it with my planned additions. Some people... |
| 15:09 |
JBoyer |
berick++ |
| 15:09 |
JBoyer |
So, |
| 15:09 |
JBoyer |
#topic New Business |
| 15:09 |
|
Topic for #evergreen is now New Business (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 15:10 |
JBoyer |
#link https://georgialibraries.markmail.org/message/w76isj7krseqvo3i?q=list:org%2Egeorgialibraries%2Elist%2Eopen-ils-dev Michele's latest top 10 bugs |
| 15:10 |
phasefx |
#info phasefx = Jason Etheridge, EOLI |
| 15:10 |
terranm |
mmorgan++ |
| 15:10 |
JBoyer |
anything you'd like to call out specifically mmorgan? |
| 15:11 |
mmorgan |
They're all important, just wanted to keep a good supply of low hanging fruit for folks that might have time to do some committing. |
| 15:11 |
JBoyer |
(I do know there's been interest expressed in bug 1857060 also if we want to turn it up to 11) |
| 15:11 |
pinesol |
Launchpad bug 1857060 in Evergreen "A few changes needed to accomodate 979 ISBNs" [Medium,New] https://launchpad.net/bugs/1857060 |
| 15:11 |
JBoyer |
Sounds good. mmorgan++ |
| 15:12 |
mmorgan |
I could certainly have included more :) but 10 seemed a reasonable number. |
| 15:12 |
JBoyer |
Well, this morning I was messing with LP searches and came up with these: |
| 15:12 |
JBoyer |
#link https://bugs.launchpad.net/evergreen/+bugs?orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.tag=pullrequest+-signedoff+-needsrepatch&field.tags_combinator=ALL LPs with pullrequests ready to test |
| 15:12 |
JBoyer |
and |
| 15:12 |
JBoyer |
#link https://bugs.launchpad.net/evergreen/+bugs?orderby=-importance&field.status%3Alist=NEW&field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.tag=pullrequest+signedoff+-needsrepatch&field.tags_combinator=ALL LPs with signedoff branches ready to look over + push if good |
| 15:13 |
csharp |
holy craznap |
| 15:13 |
JBoyer |
So if 10 bugs isn't enough challenge folks can look through around 130+ there, heh. |
| 15:13 |
JBoyer |
Those are, believe it or not, significantly shorter than they started. |
| 15:13 |
mmorgan |
JBoyer++ |
| 15:14 |
terranm |
Yeah, we tested a lot during the last few bugsquash/feedback fests |
| 15:14 |
JBoyer |
Which kind of winds us around to the topic I mentioned briefly in my email reminder this morning. |
| 15:15 |
JBoyer |
#topic How can these meetings be made more effective / beneficial |
| 15:15 |
|
Topic for #evergreen is now How can these meetings be made more effective / beneficial (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 15:16 |
JBoyer |
I know most of an afternoon is not a lot of time to really give this much thought, especially after the second day back to work for many / most folks, but even if you don't have any thoughts or suggestions today I'd like you all to think about where these may fall flat or how they may be even better than they already are in future. |
| 15:18 |
sandbergja |
These meetings can be particular helpful when we have a thorny (or controversial) issue on the docket to discuss |
| 15:18 |
sandbergja |
Maybe we could schedule some more of those? |
| 15:18 |
berick |
sandbergja: agreed. having a focus is helpful |
| 15:18 |
JBoyer |
Also bear in mind I'm not staking any claim on running these meetings. If someone has some Big Ideas and wants to take the wheel we can certainly see how that works out. Though I do find that it helps to make some assumptions about who is running things if nothing else so they can have their calendar prod them to prod the rest of us, heh |
| 15:18 |
sandbergja |
Also, I always look forward to these meetings because of JBoyer's jokes |
| 15:18 |
* JBoyer |
does what he can |
| 15:18 |
csharp |
I think having *something* scheduled is important since we can be a big disorganized blob of a dev community |
| 15:19 |
csharp |
so even if some months it's kind of looking at each other it's better than not doing anything |
| 15:19 |
dbwells |
#info dbwells = Dan Wells, Hekman Library (Calvin University) |
| 15:20 |
csharp |
also, I think we're more chatty when we're focused on the next bugsquash or other structured dev activity |
| 15:21 |
JBoyer |
sandbergja, I'm not sure I follow what you meant by "Maybe we could schedule some more of those?" More meetings like this, or more specialized discussions at a certain time, something else entirely, etc? |
| 15:21 |
csharp |
for my part, I'm straight off vacation and prepping for next weekend's PINES upgrade |
| 15:21 |
sandbergja |
More specialized discussions |
| 15:21 |
mmorgan |
Maybe each meeting, in addition to other business, we could look at a certain bug that's languishing, or a certain group of related bugs, so there's something on the agenda each month. |
| 15:21 |
sandbergja |
Say, have a topic of the month |
| 15:21 |
csharp |
(going to 3.6.1 in case people are curious) |
| 15:21 |
terranm |
+1 |
| 15:21 |
csharp |
new devs offer a model like that |
| 15:22 |
sandbergja |
If we want to have a lot of discussion sometime, we could always have a topic like "Should we move to Github, Gitlab, etc." :-) |
| 15:22 |
csharp |
or this agenda item: finally settle the self-hosted gitolite vs. other options thing |
| 15:22 |
csharp |
jinx |
| 15:23 |
sandbergja |
Or strategizing on improving test coverage, since that always comes up, but we never really make a plan about it |
| 15:23 |
JBoyer |
Ugh. Yeah. That one only seems to get real traction when discussed in person. |
| 15:24 |
csharp |
moving onto another git platform would offer built-in testing stuff too, which would affect sandbergja's idea there |
| 15:24 |
JBoyer |
There was a rough consensus around GitHub during the hackaway, so that's kind of progress. (*If* we're moving, we know where to. :D ) |
| 15:24 |
terranm |
It might be a good idea to have a status update on numbers of commits, new bug reports, etc. each month. |
| 15:25 |
mmorgan |
+1 |
| 15:25 |
terranm |
Last month we discussed each core committer having a goal of committing at least one patch per month - maybe that could be in the status update too |
| 15:26 |
mmorgan |
And also stats on open bugs, those with pullrequests and signoffs so we know how much work there is to do and how much gets done. |
| 15:26 |
terranm |
+1 |
| 15:26 |
sandbergja |
We also might need some coordination of large projects with tons of lp tickets (I'm thinking getting the bootstrap opac ready for 3.7) |
| 15:27 |
JBoyer |
Lots of good ideas. I might have to re-adjust my calendar reminders at this rate. ;) |
| 15:28 |
JBoyer |
sandbergja, Something like a Bootstrap-themed bug squashing week would be good. (doesn't have to be that specific event but similar in spirit I assume) |
| 15:28 |
JBoyer |
I do think there are several bootstrap bugs in that signedoff LP search link. |
| 15:28 |
sandbergja |
JBoyer: yeah, that sounds good! |
| 15:29 |
csharp |
also, we saw the value of video meetings for the EG conf and Hackaway - maybe every few months could be a hosted Zoom/Google/whatever call that gets recorded for the archives |
| 15:29 |
mmorgan |
Agree about coordination of large projects, we often find ourselves in the position of wanting to use a new feature after an upgrade, but finding there are too many bugs remaining to make it useful/possible to implement. |
| 15:30 |
csharp |
the main reason for IRC meetings is automatic minutes and ultimate transparency, but with good minute taking and a video record, maybe that would spirit would be preserved |
| 15:30 |
csharp |
er.. too many "would"s there |
| 15:31 |
terranm |
+1 |
| 15:31 |
mrisher |
It would be great to get more visibility on old pull requests. I sometimes come across old pull requests I submitted long ago that need a look. |
| 15:31 |
JBoyer |
I can also see people specifically avoiding video meetings, especially if they're recorded. So we shouldn't consider only those, but they would make a nice addition. |
| 15:31 |
JBoyer |
mrisher++ |
| 15:32 |
mrisher |
maybe make a special category of untested pull request that are older than a certain length. (6 months? 3?) |
| 15:33 |
JBoyer |
I feel like ~6 is a good time to call them out. Any branches would almost certainly require a rebase at that point. |
| 15:33 |
* mmorgan |
likes the idea of curated lists that are not so big that they are overwhelming to look at |
| 15:34 |
terranm |
+1 |
| 15:34 |
JBoyer |
True. My links above are maybe a little overwhelming. |
| 15:34 |
mmorgan |
JBoyer: They are comprehensive:) |
| 15:34 |
JBoyer |
So, it sounds like we have a lot of very good ideas. I am but one person who has made some poor choices re: time, does anyone have anything they feel passionately about and want to take an action item? |
| 15:35 |
JBoyer |
Noting that "action item" does not necessarily mean "done by 2021-02-02" |
| 15:35 |
JBoyer |
(though that would be nice also) |
| 15:36 |
Dyrcona |
Should we survey again about good times for these meetings? I"ve noticed a lack of certain names participating lately. |
| 15:36 |
JBoyer |
Probably not a bad idea. |
| 15:37 |
JBoyer |
#action JBoyer will poll the community about possible dev meeting times |
| 15:38 |
JBoyer |
I'll send a couple emails and drop notes in here a couple different times over the next week or two. |
| 15:38 |
berick |
JBoyer++ |
| 15:40 |
sandbergja |
What other action items are there? |
| 15:42 |
JBoyer |
Whatever anyone would like to commit to doing. :) Organizing a bootstrap-fest or something like it, mmorgan is handling a top 10 bugs list now and then, does someone want to re-surface specifically old bugs, or some other metric, etc. |
| 15:42 |
sandbergja |
I could make a list of cool old bugs! |
| 15:42 |
sandbergja |
Probably taking a lot of inspiration from mmorgan's lists |
| 15:43 |
JBoyer |
#action sandbergja will put together a list of older bugs that need attention |
| 15:43 |
mmorgan |
sandbergja++ |
| 15:43 |
JBoyer |
sandbergja++ |
| 15:43 |
* mmorgan |
will continue with the top ten list, and is open for nominations for said list |
| 15:43 |
terranm |
sandbergja++ |
| 15:43 |
terranm |
mmorgan++ |
| 15:43 |
JBoyer |
the nice thing about that is if there are any xul-related bugs (other than "strip out the rest of it") they can be marked won't fix, also helping. :) |
| 15:43 |
mrisher |
sandbergja++ |
| 15:44 |
sandbergja |
Oh, that's another large topic we should discuss at some point: getting rid of dead code (including xul) |
| 15:44 |
mmorgan |
+1 |
| 15:44 |
terranm |
+1 |
| 15:45 |
mmorgan |
It's frustrating when digging through code only to realize what you're looking at is not used anymore |
| 15:45 |
JBoyer |
And potential refactoring. Are there perl mods we're no longer using, are there any we're using very little of and can be written-out, etc. Fewer dependencies, fewer bugs we didn't write. ;) |
| 15:45 |
sandbergja |
Very true |
| 15:46 |
terranm |
Next Feedback Fest is Feb 8-12, and my goal is to load as many patches for testing as possible again |
| 15:46 |
JBoyer |
(to a point. Anyone that suggests "roll our own crypto!" gets put in time out.) |
| 15:46 |
JBoyer |
terranm++ |
| 15:46 |
sandbergja |
I nominate dead code removal + refactoring desires as a discussion item for the February meeting |
| 15:46 |
mrisher |
terranm++ |
| 15:46 |
sandbergja |
as in our wishes related to refactoring |
| 15:49 |
JBoyer |
#info Feedback Fest is February 8-12 |
| 15:50 |
JBoyer |
We can also continue to think about ways to improve these meetings. |
| 15:51 |
JBoyer |
Additionally, releases are scheduled for 2021-01-20 I believe, so now's the time to hit those lists good and hard (be they 10 or 100+). |
| 15:51 |
JBoyer |
I know gmcharlt has said that he would be able to help with that some though he's not able to be here today. |
| 15:52 |
Dyrcona |
The releases are going to be security releases, so we'll need some extra coordination. |
| 15:52 |
csharp |
reminder to make sure you "claim" each bug by assigning it to yourself |
| 15:52 |
JBoyer |
Dyrcona++ |
| 15:52 |
JBoyer |
csharp++ |
| 15:52 |
Dyrcona |
At some point, we'll need to declare a commit moratorium. |
| 15:53 |
JBoyer |
Ah, right. Hadn't thought about that, good point. |
| 15:53 |
JBoyer |
What has the timeframe been like on that in the past, a week, slightly more, slightly less? |
| 15:54 |
Dyrcona |
Nothing drastic, just a day or so around release time. |
| 15:54 |
JBoyer |
Oh, right. It's not like an RC release and all of that.. |
| 15:54 |
Dyrcona |
Though, it depends on how long it takes us to get the releases together. |
| 15:55 |
JBoyer |
Maybe to be on the safe side, if we're aiming for a 1/20 release we call a hold on the Thursday prior? |
| 15:55 |
JBoyer |
Eh, that is basically a week. |
| 15:56 |
Dyrcona |
We have been slow getting the last couple of releases out. |
| 15:56 |
Dyrcona |
Granted, the last one happened right before the US Thanksgiving holiday. |
| 15:57 |
sandbergja |
How about 1/18 as the cut-off? |
| 15:57 |
sandbergja |
Then we would have all of 1/19 and 1/20 to work on the release |
| 15:58 |
Dyrcona |
That sounds good for now. I suppose that we could change it if necessary. |
| 15:58 |
JBoyer |
I think that would work for me. |
| 15:59 |
Dyrcona |
Oh! I just realized that 1/18 is a US Holiday, and I'm supposed to do a bunch of O/S upgrades that day. |
| 16:00 |
JBoyer |
And I'm off, and csharp is upgrading, and, and. oops. |
| 16:00 |
Dyrcona |
Moving to Ubuntu 18. It should still be OK for me. |
| 16:00 |
sandbergja |
Hmmm... maybe we should change the date of the release? |
| 16:00 |
sandbergja |
That sounds like a lot, no matter when we have the commit cut-off |
| 16:00 |
Dyrcona |
Maybe. We've been consistently late anyway. |
| 16:02 |
JBoyer |
I think pushing back the release 1 week is no problem, especially since we have to include a 1-2 day commit freeze. I'm still good with a Monday freeze, Wednesday release on 1/27 if that works with everyone else. |
| 16:02 |
gmcharlt |
+1 |
| 16:02 |
Dyrcona |
That works for me. I was just about to suggest pushing it back a week. |
| 16:02 |
sandbergja |
+1 |
| 16:03 |
JBoyer |
#info January releases pushed back to 2021-01-27 |
| 16:03 |
JBoyer |
That much more time to squeeze in those bugs! :) |
| 16:04 |
JBoyer |
I just noticed it's past 4, and I thought this would be a shorter than usual meeting. Anything else to discuss before I shut it down? |
| 16:04 |
Dyrcona |
Yeahp. |
| 16:04 |
Dyrcona |
I updated the dev calendar, and I'll get the milestones in Lp. |
| 16:04 |
JBoyer |
Dyrcona++ |
| 16:04 |
sandbergja |
Dyrcona++ |
| 16:04 |
sandbergja |
JBoyer++ |
| 16:04 |
JBoyer |
#topic Announcements |
| 16:04 |
|
Topic for #evergreen is now Announcements (Meeting topic: 2021-01-05 - Developer Meeting, Agenda Available at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2021-01-05) |
| 16:05 |
Dyrcona |
JBoyer++ sandbergja++ |
| 16:05 |
terranm |
Dyrcona++ JBoyer++ |
| 16:05 |
gmcharlt |
JBoyer++ |
| 16:05 |
csharp |
JBoyer++ |
| 16:05 |
JBoyer |
(I guess the release change would have been a good announcement, oh well.) |
| 16:05 |
JBoyer |
#info Next Meeting is 2021-02-02 |
| 16:05 |
JBoyer |
#endmeeting |
| 16:05 |
|
Topic for #evergreen is now Welcome to the #evergreen library system channel! | We are publicly logged: http://irc.evergreen-ils.org/evergreen | Large pastes at http://paste.evergreen-ils.org | Can't speak? Make sure your nickname is registered and that you are identified to freenode services: https://freenode.net/kb/answer/registration |
| 16:05 |
pinesol |
Meeting ended Tue Jan 5 16:05:27 2021 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:05 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-01-05-15.05.html |
| 16:05 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-01-05-15.05.txt |
| 16:05 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2021/evergreen.2021-01-05-15.05.log.html |
| 16:05 |
JBoyer |
Thanks everyone. |
| 16:05 |
csharp |
squeezing_bugs++ |
| 16:06 |
mmorgan |
JBoyer++ |
| 16:06 |
gmcharlt |
sandbergja: random question for you - for the course materials module, is one of the ideas that students could get linked to courses? would that be to support access control in the future? and if so, would there need to be some sort of future data exchange with the course registration system? |
| 16:08 |
sandbergja |
gmcharlt: yes, the idea was that students could get linked to courses. Less for access control, and more with the hopes of a future OPAC display where students could log in and see all their course materials in one place. |
| 16:09 |
sandbergja |
And yes, that would rely on some kind of regular information-grabbing from the course registration system |
| 16:09 |
gmcharlt |
running every five minutes during drop/add, presumably ;) |
| 16:10 |
sandbergja |
hahaha yeah |
| 16:11 |
gmcharlt |
thanks - just wanted to make sure of the use case |
| 16:15 |
sandbergja |
Oh, one other thing we wanted to do was to send out automatic emails to students near the start of the term using A/T saying "You know the $300 textbook required for your class? Well, here are some copies available for you in the Library" |
| 16:15 |
|
mantis1 left #evergreen |
| 16:16 |
gmcharlt |
ah |
| 16:16 |
* gmcharlt |
imagines the potential for internecine warfare between library and campus bookshop ;) |
| 16:17 |
sandbergja |
Yeah, your political mileage may vary with that one |
| 16:17 |
sandbergja |
Fortunately, we have a very good relationship with our bookstore. :-) |
| 16:17 |
gmcharlt |
cool :) |
| 17:00 |
|
sandbergja_ joined #evergreen |
| 17:13 |
|
mmorgan left #evergreen |
| 17:36 |
|
rjackson_isl_hom joined #evergreen |
| 18:01 |
pinesol |
News from qatests: Testing Success <http://testing.evergreen-ils.org/~live> |
| 19:15 |
|
sandbergja_ joined #evergreen |
| 20:13 |
pinesol |
Showing latest 5 of 14 commits to Evergreen... |
| 20:13 |
pinesol |
[evergreen|Bill Erickson] LP1889128 Clear patron barcode on staff hold - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9c1b15d> |
| 20:13 |
pinesol |
[evergreen|Bill Erickson] LP1889128 Support user settings for SMS prefs - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9b683dd> |
| 20:13 |
pinesol |
[evergreen|Bill Erickson] LP1889128 <eg-date-select/> clearable via model - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=044b4de> |
| 20:13 |
pinesol |
[evergreen|Bill Erickson] LP1889128 Activation date repair and form reset handling - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9ff0d6f> |
| 20:13 |
pinesol |
[evergreen|Jane Sandberg] LP1889128 (follow-up) associating inputs and labels - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=d8666c0> |
| 20:29 |
|
sandbergja_ joined #evergreen |
| 21:49 |
|
sandbergja_ joined #evergreen |
