| Time |
Nick |
Message |
| 02:25 |
|
akilsdonk joined #evergreen |
| 02:25 |
|
tsadok joined #evergreen |
| 06:51 |
|
collum joined #evergreen |
| 07:29 |
|
rjackson_isl_hom joined #evergreen |
| 07:40 |
|
rjackson_isl_hom joined #evergreen |
| 07:50 |
|
rfrasur joined #evergreen |
| 08:27 |
|
mantis1 joined #evergreen |
| 08:32 |
|
Dyrcona joined #evergreen |
| 08:41 |
|
mmorgan joined #evergreen |
| 09:08 |
|
jvwoolf joined #evergreen |
| 09:50 |
pinesol |
News from commits: LP#1980257: add release notes entry <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=52ceabcf8dddaace7ac65590cf5f3435b8cf4917> |
| 09:50 |
pinesol |
News from commits: LP#1980257: (follow-up) add balance owed to the pending grid as well <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=bcbfb2640d69124bb5283999a587b31dc95484e8> |
| 09:50 |
pinesol |
News from commits: LP#1980257: Patron bucket money summary <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=7c6eab39823275e8a69091c51a4b6b7d896c5605> |
| 09:50 |
pinesol |
News from commits: LP1975879 Holdings editor allows owning lib changed <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=e369f74bcec0399b3c9fab2c1985d5d42d70fc29> |
| 10:17 |
|
rjackson_isl_hom joined #evergreen |
| 10:20 |
pinesol |
News from commits: Staff banner added to the staff portal local administration page. <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=fe918be61727790ac0b875f91d0aa28b3d885c77> |
| 10:20 |
pinesol |
News from commits: LP1956790 Support applying item alerts via templates <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=c41c881ac5ee4b91e5fd5f1db595daa7b12d2ebf> |
| 10:23 |
|
rjackson_isl_hom joined #evergreen |
| 10:25 |
mantis1 |
Has anyone ran into issues with DOB not filling in correctly after confirming a pending patron? We had one library report it but no one else has. |
| 10:25 |
mantis1 |
Could be user error |
| 10:29 |
mmorgan |
mantis1: Bug 1814150? There are a couple of other bugs referenced in that report also. |
| 10:29 |
pinesol |
Launchpad bug 1814150 in Evergreen "Self-registration: system accepts wrong DOB format" [Medium,Confirmed] https://launchpad.net/bugs/1814150 |
| 10:32 |
Dyrcona |
We applied a local patch to patron self-registration to make the DOB format be the same as patron registration in the staff client. IIRC, the back end assumes that they are the same, but they are not in a default installation. |
| 10:37 |
mantis1 |
mmorgan++ |
| 10:50 |
pinesol |
News from commits: LP1958573 PMC messages created by action triggers not patron-visible <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=ba2fc41399e9723361245a95e64d78a6c1eb2e59> |
| 12:15 |
mmorgan |
berick++ gmcharlt++ # fixing :) |
| 12:32 |
Dyrcona |
DBD::Pg++ |
| 13:03 |
Dyrcona |
Hrm.. URIs aren't displaying correctly on my test VM, and I just merged my production branch into my test branch.... |
| 13:04 |
Dyrcona |
And, there are no differences in the OPAC according to git diff.... |
| 13:13 |
Dyrcona |
Grr... Thought maybe a git clean -xfd and a rebuild would help, but no.... |
| 13:14 |
Dyrcona |
In production, the link is on subfield z and subfield 3 appears after it. On my test VM it is the opposite in both ways. |
| 13:21 |
Dyrcona |
Not even wiping out the installed bootstrap templates and reinstalling them helped.... |
| 13:22 |
|
jvwoolf left #evergreen |
| 13:29 |
Dyrcona |
Ah, wait a minute.... I recall something now about a difference between the ttopac and bootstrap opac and I had to patch it. However the patch doesn't seem to be missing from the git branch AFAICT. |
| 13:32 |
Dyrcona |
Neither branch shows the change, nor does my old branch for 3.7.2.... |
| 13:32 |
berick |
might be a few mins late to dev mtg |
| 13:34 |
Dyrcona |
I may also be late. I have a 2:00 PM meeting on zoom. |
| 13:35 |
Dyrcona |
Ugh... Looks like I might have a change that didn't make it into git.... |
| 13:48 |
Dyrcona |
The file installed in production doesn't look any different than the one in git.... |
| 13:48 |
Dyrcona |
But the results are definitely different.... |
| 13:53 |
* Dyrcona |
is perplexed, but this will have to wait, I guess. |
| 14:46 |
|
shulabear joined #evergreen |
| 14:46 |
Dyrcona |
The training server looks like production, but I can't find any relevant differences between the test vm branch and those for training or production. The installed files also match those from the branches. Is there some server cache that I'm overlooking? |
| 14:50 |
|
terranm joined #evergreen |
| 14:50 |
Dyrcona |
Found the eg_template_cache in the systemd temp files and deleted it just in case. Makes no difference on training. |
| 14:53 |
Dyrcona |
Oh... I see one thing. There's a bug in a program that I'm running to update 856s. That might be the culprit... |
| 14:54 |
|
dbriem joined #evergreen |
| 14:55 |
|
BDorsey joined #evergreen |
| 14:58 |
|
BDorsey joined #evergreen |
| 14:59 |
|
BDorsey joined #evergreen |
| 15:00 |
|
smorrison joined #evergreen |
| 15:00 |
JBoyer |
The third bell chimes in the Eastern Times. Who wants to developers, developers, developers? |
| 15:00 |
* phasefx |
throws a chair |
| 15:01 |
JBoyer |
phasefx++ |
| 15:01 |
Dyrcona |
JBoyer++ phasefx++ |
| 15:01 |
JBoyer |
#startmeeting 2022-07-12 - Developer Meeting |
| 15:01 |
pinesol |
Meeting started Tue Jul 12 15:01:12 2022 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:01 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:01 |
pinesol |
The meeting name has been set to '2022_07_12___developer_meeting' |
| 15:01 |
JBoyer |
#info Agenda at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2022-07-12 |
| 15:01 |
JBoyer |
#topic Introductions |
| 15:01 |
JBoyer |
Old joke, who dis? |
| 15:01 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CWMARS |
| 15:01 |
phasefx |
#info phasefx = Jason Etheridge, EOLI |
| 15:01 |
gmcharlt_ |
#info gmcharlt = Galen Charlotn, EOLI |
| 15:01 |
phasefx |
calla wha? |
| 15:01 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:01 |
shulabear |
#info Shulabear = Shula Link, GCHR in PINES |
| 15:01 |
collum |
#info collum = Garry Collum, KCPL |
| 15:02 |
JBoyer |
#info JBoyer = Jason Boyer, EOLI |
| 15:03 |
JBoyer |
And anyone coming in later can feel free to throw an #info down |
| 15:03 |
JBoyer |
#topic Action Items from Last Meeting |
| 15:03 |
JBoyer |
#info Dyrcona will build 3.7.4 point release |
| 15:03 |
JBoyer |
#info Dyrcona will investigate improvements to make_release and upgrade scripts |
| 15:03 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:03 |
gmcharlt_ |
I've updated the agend under the Evergreen section |
| 15:04 |
JBoyer |
I didn't expect these to both be done yet, but any luck on either of them to date Dyrcona? |
| 15:04 |
JBoyer |
gmcharlt_++ I'll grab it |
| 15:04 |
Dyrcona |
Well, I plan to do the 3.7.4 release either this week or next. |
| 15:04 |
jeff |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
| 15:04 |
JBoyer |
Dyrcona, well, how does 7/20 look? :) |
| 15:05 |
JBoyer |
Well, given where things are on the agenda, |
| 15:05 |
JBoyer |
#topic Evergreen Release Updates |
| 15:05 |
Dyrcona |
It looks fine to me. I might want to get a jump start on the branch, so I did send an email to the development list that I was closing rel_3_7 and 3.7.4 on Lp. |
| 15:05 |
JBoyer |
#topic Evergreen maintenance releases |
| 15:05 |
JBoyer |
#info Galen targeting 20 July; seeking volunteers to help |
| 15:06 |
JBoyer |
Dyrcona++ |
| 15:06 |
terranm |
Dyrcona++ |
| 15:06 |
JBoyer |
I don't think there will be much resistance to wrapping up 3.7 |
| 15:06 |
phasefx |
I'm willing to help with releases, but need to be given tasks to be useful |
| 15:07 |
Dyrcona |
#info There's a signup spreadsheet here: https://docs.google.com/spreadsheets/d/1gZayHfF7qK0zwLMEAXt-PbKBMiAM_F6EZguqzIYceBY/edit#gid=0\ |
| 15:07 |
JBoyer |
gmcharlt_, anything you'd like to add to your call to keyboards? |
| 15:07 |
JBoyer |
Dyrcona++ |
| 15:07 |
JBoyer |
That's one of the things I was thinking of. |
| 15:08 |
phasefx |
I've never seen that before :D :D |
| 15:08 |
gmcharlt_ |
yes, please sign up on the spreadsheet; I'll start bugging people by Thursday |
| 15:08 |
shulabear |
gmcharlt++ Dyrcona++ |
| 15:09 |
JBoyer |
I know a few people may be in late or may not make the meeting, I can send something to the dev list unless you're planning to. |
| 15:09 |
gmcharlt_ |
and I think otherwise, given the spurt of activity the past couple days, that help testing pending Angular holdings and item editor bugs would be Good Thing |
| 15:09 |
gmcharlt_ |
JBoyer: I'll coordinate it |
| 15:09 |
JBoyer |
gmcharlt_++ |
| 15:09 |
terranm |
gmcharlt_++ |
| 15:10 |
JBoyer |
It sounds like point releases are on their way, any discussion before moving on to LP stats updates? |
| 15:10 |
shulabear |
gmcharlt_++ |
| 15:11 |
mmorgan |
gmcharlt_++ |
| 15:11 |
JBoyer |
ok |
| 15:11 |
JBoyer |
#topic Launchpad Status |
| 15:11 |
* JBoyer |
#info Snapshot |
| 15:11 |
JBoyer |
#info Snapshot |
| 15:11 |
JBoyer |
#info Open Bugs - 2765 |
| 15:11 |
JBoyer |
#info Pullrequests - 108 |
| 15:11 |
JBoyer |
#info Signedoff - 27 |
| 15:11 |
JBoyer |
#info Updates Since Last Meeting |
| 15:11 |
JBoyer |
#info Bugs Added - 47 |
| 15:11 |
JBoyer |
#info Pullrequest tag Added - 27 |
| 15:11 |
JBoyer |
#info Signedoff tag Added - 6 |
| 15:12 |
JBoyer |
#info Fix Committed - 20 |
| 15:12 |
JBoyer |
Fresh business incoming |
| 15:12 |
JBoyer |
#topic New Business |
| 15:12 |
JBoyer |
#topic Schedule next Bug Squashing Week - late July? (terranm) |
| 15:12 |
terranm |
oops, sorry |
| 15:13 |
berick |
#info berick Bill Erickson, KCLS |
| 15:13 |
terranm |
Yes, I was thinking it is time. |
| 15:13 |
terranm |
Maybe the week of July 25? |
| 15:13 |
terranm |
In addition, I'd like to start spacing out BSWs from FFs better. Since FFs tend to be in Feb and Aug, I was thinking BSWs would be good around early November and late May. Thoughts? |
| 15:14 |
gmcharlt_ |
makes sense to me |
| 15:14 |
berick |
+1 to spacing |
| 15:14 |
JBoyer |
That week works for me. |
| 15:14 |
shulabear |
+1 to the week and to spacing |
| 15:14 |
Dyrcona |
Someone who usually hosts servers for bug squashing is going to be out the week of the 25th, but I'll let them chime in if they feel the need. |
| 15:14 |
mmorgan |
+1 to both |
| 15:15 |
Dyrcona |
I may also be out that week and/or the next. |
| 15:15 |
JBoyer |
And +1 to spacing also. Were they forced together for some reason or has experience suggested that they need more space than before? |
| 15:15 |
terranm |
I think it just happened sort of randomly |
| 15:16 |
JBoyer |
Dyrcona, perhaps worth checking, is the person you're thinking of here? |
| 15:17 |
terranm |
I think we get more testing participation if they are spaced out rather than in two months back to back |
| 15:17 |
Dyrcona |
JBoyer: They |
| 15:17 |
berick |
i should be able to host a bug squashing VM this time around |
| 15:17 |
terranm |
berick++ |
| 15:17 |
JBoyer |
terranm, makes sense. |
| 15:17 |
Dyrcona |
Yes, listed in the room, and I had a personal chat with them earlier today. |
| 15:17 |
mmorgan |
berick++ |
| 15:18 |
shulabear |
berick++ |
| 15:18 |
JBoyer |
terranm++ |
| 15:18 |
JBoyer |
berick++ |
| 15:18 |
terranm |
Tiffany and I should both be able to host, so with ours and berick's, we should be okay |
| 15:18 |
terranm |
Any more are welcome of course |
| 15:18 |
mmorgan |
terranm++ |
| 15:19 |
Dyrcona |
I think spacing the events out would be better. |
| 15:19 |
terranm |
Okay, I will schedule this one for the week of July 25, then move to November & May for the regular rotation |
| 15:20 |
JBoyer |
I'll have our two updated also. |
| 15:20 |
JBoyer |
terranm++ |
| 15:20 |
terranm |
JBoyer++ |
| 15:20 |
mmorgan |
:) |
| 15:20 |
shulabear |
terranm++ |
| 15:20 |
JBoyer |
And Nov / May also looks good. |
| 15:21 |
JBoyer |
Anything else for terranm ? |
| 15:21 |
terranm |
Thanks all! |
| 15:22 |
JBoyer |
up next is berick: |
| 15:22 |
JBoyer |
#topic Consider merging bug 1904036? (berick) |
| 15:22 |
pinesol |
Launchpad bug 1904036 in Evergreen "Port patron interfaces to Angular (search, checkout, etc.)" [Wishlist,New] https://launchpad.net/bugs/1904036 |
| 15:22 |
JBoyer |
#info If UI components are not ready for prime time, they can remain hidden (unless you know where to find them). |
| 15:22 |
JBoyer |
#info There's lots of good Angular stuff in here and we're collecting other pullrequests that rely on them. |
| 15:22 |
berick |
pretty much says it. if we don't show the UI bits, we still get a lot of new code that is usable as more stuff is ported to Angular |
| 15:23 |
berick |
new SCKO and item status UI depend on it, and several others I'm sure |
| 15:23 |
gmcharlt_ |
are the compoent changes fully separated out in the current branch? |
| 15:24 |
berick |
i'm also leaning toward removing the partial UI integration where there is an extra menu, but that's a secondary part of the discussion |
| 15:24 |
berick |
gmcharlt_: not sure I understand the question.. |
| 15:24 |
gmcharlt_ |
are changes to core Angular components in separate commits, or are they mixed in with the patron interface commits? |
| 15:25 |
berick |
gmcharlt_: a bit of everything, i imagine. i can do some cleanup, though |
| 15:25 |
gmcharlt_ |
also, I am concerned about the potential for a reprise of the Angular holdings and item editor situation, but even bigger |
| 15:26 |
berick |
gmcharlt_: you mean regressions? |
| 15:26 |
gmcharlt_ |
yes |
| 15:26 |
gmcharlt_ |
but there's going to be a balancing act |
| 15:27 |
berick |
i get that and it's why I thought merging sans UI bits for starters would buy time to find more bugs |
| 15:27 |
berick |
sans menu entry changes, I should say |
| 15:27 |
gmcharlt_ |
the branch is realistically far too large for detailed patch-level scrutiny |
| 15:27 |
berick |
yeah, it's a beast |
| 15:28 |
gmcharlt_ |
but if we merge soon (and I do see reasons for doing that), I think we're going to need to organize community testing on a large scale; possibly larger than previoulsy attempted |
| 15:28 |
berick |
my thinking is if the UI is not yet exposed, a minimal amount of the new code will actually be used. |
| 15:29 |
berick |
once we do expose the new UI's, which may come after 3.10, then loads of testing would be needed |
| 15:29 |
gmcharlt_ |
yeah, but that just kicks the can down the road, since of course the point is eventually to switch to it |
| 15:29 |
Dyrcona |
gmcharlt_++ |
| 15:29 |
Dyrcona |
+1, too.... I think if it goes in, turn it on. |
| 15:30 |
berick |
sort of. if we can expose less ambitious interfaces that use the underlying code, then we get the chance to test parts of it without flipping a giant switch |
| 15:30 |
gmcharlt_ |
so I think what I'm saying is that organizing broad testing needs to happen on the heals of a merge |
| 15:30 |
gmcharlt_ |
*heels |
| 15:31 |
berick |
gmcharlt_: so you're thinking flip the big switch on day one too? |
| 15:32 |
terranm |
I could work up a list of tasks that need to be tested for each of the new interfaces as a starting point. It might be easier to get people to test if it's broken into bite-sized pieces. |
| 15:32 |
mmorgan |
Just to clarify, right now, the new uis are under an org unit setting? |
| 15:32 |
gmcharlt_ |
more like stand up test systems that have the switch flipped |
| 15:32 |
berick |
mmorgan: sort of. it's kind of a mess what we have. |
| 15:32 |
berick |
that we were going to test with |
| 15:32 |
berick |
i'm of the opinion that when we do flip the switch, it has to be fully flipped or it's going to get really confusing real fast |
| 15:33 |
berick |
hopping between the same UI's depending on how you got there |
| 15:33 |
gmcharlt_ |
(also noting that soon there will be a dump of the Angular acquisitions sprint 4 stuff, though that's more self-contained than the patron/circ stuff) |
| 15:34 |
JBoyer |
terranm++ I do think having a reminder of what all needs to be tested helps. I wonder if some of the staff interfaces have the 1-2 things users do *most* and then say "yeah, didn't fall over" by end users. A guide would help them test things they maybe do quarterly or less. |
| 15:34 |
mmorgan |
terranm++ |
| 15:34 |
mmorgan |
+1 to broad community testing |
| 15:35 |
shulabear |
terranm++ |
| 15:35 |
gmcharlt_ |
also, I think the more that the branch can be cleaned up to have new and changed shared component live in self-contained patches, the better |
| 15:36 |
gmcharlt_ |
as individually, those should be much more amenable to piecemeal testing by devs and committers |
| 15:38 |
berick |
yeah, i can clean up the shared/core changes. that's a small portion of it. |
| 15:39 |
gmcharlt_ |
and I think the other thing that would help is ensuring that there's one big ol' switch (or maybe a small set of them) to reliably switch between old and new interfaces |
| 15:39 |
berick |
it gets a little complicated with the patron UI, since it's basically one big application. it kind has to be added as a whole. |
| 15:39 |
mmorgan |
+1 to reliable switch(es) |
| 15:40 |
berick |
a few things link out, but it's a single tabbed interface |
| 15:40 |
berick |
w/ loads of sub-interfaces |
| 15:41 |
JBoyer |
berick, I think 1 big switch for the patron app is ok, so long as there's no way to accidentally get dropped in the "other" one unexpectedly. |
| 15:41 |
gmcharlt_ |
if I'm understanding correctly, that seems like it would mean that most of the work of the switch lines in toggling (a) nav menu entries and (b) links originating outside of the patron/circ apps to point to either AngularJS or Angular |
| 15:41 |
gmcharlt_ |
*lies in |
| 15:42 |
berick |
yeah, every link that loads a patron, gets pointed to Angular. that part's easy |
| 15:42 |
jeff |
another option is to have no switch, and "don't upgrade" is your only switch. combined with potentially a longer support life for the previous release, that might make sunsetting the old interfaces more of a sure thing. |
| 15:42 |
berick |
jeff: that would be my pref. |
| 15:43 |
berick |
running them side by side will get messy no matter what, imo |
| 15:43 |
gmcharlt_ |
that still presupposes actively organized and broad testing |
| 15:43 |
berick |
absolutely |
| 15:43 |
* Bmagic |
scrolls up |
| 15:44 |
* phasefx |
still remembers having three or so pull lists |
| 15:44 |
gmcharlt_ |
but I mislike the notion of potenially have 3.10.0 end up being intentionally full of regressions |
| 15:44 |
berick |
but going back to my original proposal, if we merge the code without any menu/link updates, then we have a body of code we can start building on, which will have the affect of testing said code. Eg. it's a lot easier to test a new Item Status UI then overhauling the whole patron UI. |
| 15:44 |
mmorgan |
gmcharlt_++ |
| 15:44 |
gmcharlt_ |
I wonder if we should consider an extended timeframe for 3.10, balanced with a brief 3.11 |
| 15:45 |
berick |
i wasn't trying to flip the switch for 3.10. a full switch flip should happen basically the day after a major release is made |
| 15:45 |
berick |
not halfway into the release cycle |
| 15:46 |
berick |
if going all in is the consensus, then'd i'd say we do that the day after 3.10 is released or thereabouts |
| 15:47 |
* mmorgan |
still favors reliable switch(es) |
| 15:47 |
berick |
mmorgan: how do you mean? |
| 15:47 |
JBoyer |
If I take gmcharlt_ 's point that is the suggestion. 3.10 doesn't have the branch and is supported a longer time, with 3.11 having a shorter cycle so there's only 1 huge change, am I following correctly gmcharlt_ ? |
| 15:47 |
mmorgan |
These are probably the most used interfaces in many systems |
| 15:48 |
mmorgan |
berick: Meaning not going all in and the "switch" being don't upgrade. |
| 15:48 |
gmcharlt_ |
JBoyer: one huge change and a largish change (acq) |
| 15:48 |
Dyrcona |
Why not add it after 3.10, go all in, and 3.11 becomes 4.0 if the changes are that big? |
| 15:49 |
gmcharlt_ |
because anything that isn't turned until 3.11 will largely not get significant testing untikl 3.11 starts (is my fear) |
| 15:50 |
Dyrcona |
Anyone testing leading up to the 3.11 release would be using the new interfaces. |
| 15:50 |
gmcharlt_ |
berick: let me ask you this - assuming a longer 3.10 cycle, is your branch essentially feature complete now? (barring the inevitable obscure YAOUS implementations and so forth)? |
| 15:50 |
phasefx |
this is probably crazy, but how about we hold releases hostage until we get significant testing? super long rc-1 for whatever holds the new stuff |
| 15:51 |
gmcharlt_ |
or are there significant known bits of the overall AngularJS circ app that aren't yet implemented in Angular? |
| 15:51 |
berick |
gmcharlt_: we're using in production, w/ some patches I have not yet backported. I think the patron messages stuff might need some tweaking as well |
| 15:51 |
berick |
since it was concurrently developed |
| 15:51 |
berick |
oh and the triggered events UI needs updating to match the new stuff |
| 15:52 |
gmcharlt_ |
what about circulation settings and options that KCLS doesn't use? anything not implemented? |
| 15:52 |
berick |
gmcharlt_: it was built on the AngJS code, so in theory, it's all there. but, i'm sure there's something |
| 15:53 |
gmcharlt_ |
well, yeah, there's always going to be something, but at the moment I'm just querying what are the known gaps |
| 15:54 |
gmcharlt_ |
and it sounds like - other than catching up with trigger events interfaces and notes/messages changes - there aren't significant ones? |
| 15:54 |
berick |
no, those are the 2 menu items that are disabled in the UI right now |
| 15:54 |
berick |
should be the only big things |
| 15:55 |
gmcharlt_ |
in that case, here's a thought |
| 15:55 |
gmcharlt_ |
1. ensure that there's a Big Red Switch for insurance purposes |
| 15:55 |
gmcharlt_ |
2. merge sooner rather than later, hopefully with some cleanup of the branch |
| 15:56 |
gmcharlt_ |
3. target this for 3.10, then aim for broad testing |
| 15:56 |
berick |
what if the Big Red Switch is a patch/commit? making all the links/buttons have optional destinations is non-trivial |
| 15:56 |
gmcharlt_ |
3a including nudges, test systems, etc. |
| 15:57 |
gmcharlt_ |
4. we agree to prepare to extend 3.10 into November, possibly early December |
| 15:58 |
gmcharlt_ |
5. and by mid-November, review the state of the bugs against the Angular interfaces and make a go/no-go decision |
| 15:58 |
gmcharlt_ |
5a. (which is potentially when the decision to apply the BRS as a commit, if that's what it has to be, gets made) |
| 15:58 |
gmcharlt_ |
(end of my list) |
| 15:59 |
gmcharlt_ |
but basically, combine (a) a quick merge so that the code doesn't age or diverge too much with (b) a much more intentional testing stance for a big change like this than may have been the case in the past |
| 16:00 |
gmcharlt_ |
without kicking the can to 3.11, since the testing needs to happen eventually and it would be good not to block the potentiall for normal enhancements to patrons/circ |
| 16:00 |
berick |
gmcharlt_: ok, that makes sense. and the BRS will be a commit that just reverses all the link/button/menu changes? |
| 16:01 |
berick |
or a revert, basically |
| 16:02 |
gmcharlt_ |
if need be; a global setting / YAOUS would make it easier for ongoing testing if we're not confident enough to release 3.10 with $NewCirc, but if it's not feasible, it's not feasible |
| 16:03 |
berick |
k. do-able, was just hoping to avoid that, but I understand the desire. |
| 16:03 |
berick |
a bold plan and I like it |
| 16:03 |
berick |
gmcharlt_++ |
| 16:04 |
mmorgan |
gmcharlt_++ |
| 16:04 |
JBoyer |
berick++ gmcharlt_++ |
| 16:04 |
mmorgan |
berick++ |
| 16:04 |
terranm |
berick++ gmcharlt_++ |
| 16:04 |
shulabear |
berick++ gmcharlt_++ |
| 16:04 |
mmorgan |
BRS++ :) |
| 16:05 |
* berick |
just created a lot of work for himself |
| 16:05 |
phasefx |
the debt is never paid |
| 16:06 |
JBoyer |
My attention is lightly split, but going on, we've got just 2 more topics; I expect they'll be relatively quick. |
| 16:06 |
JBoyer |
#topic Consider merging bug 1979357? (phasefx) |
| 16:06 |
pinesol |
Launchpad bug 1979357 in Evergreen "fixes for qatester failures" [Undecided,New] https://launchpad.net/bugs/1979357 |
| 16:06 |
phasefx |
yeah, someone push this |
| 16:06 |
JBoyer |
#info Need this so we can get the QA tester going again; changes some pre-reqs for stretch and buster, and fixes a live test |
| 16:06 |
phasefx |
also fixes a bug with cover image uploader for stretch |
| 16:07 |
Dyrcona |
So, stretch is like EOL and we should drop it from our prerequisites. |
| 16:07 |
phasefx |
sure |
| 16:08 |
JBoyer |
Which is probably fine for 3.10 |
| 16:08 |
Bmagic |
berick++ gmcharlt_++ |
| 16:08 |
JBoyer |
but it is still listed for 3.9, even if not what you *should* do. |
| 16:09 |
Dyrcona |
Right. I agree. I think I made a Lp for this some months ago. |
| 16:10 |
JBoyer |
Dyrcona++ that you did. lp1947728 |
| 16:10 |
phasefx |
related to this, if anyone wants to provide qa servers with different supported distros, such that they start off pristine, can be installed on, and then made pristine again.. I'd be willing to get qatester running against all of them concurrently |
| 16:11 |
Dyrcona |
I'll take a look at Lp 1979357. It sounds like we may need some of that for Ubuntu 22.04. |
| 16:11 |
pinesol |
Launchpad bug 1979357 in Evergreen "fixes for qatester failures" [Undecided,New] https://launchpad.net/bugs/1979357 |
| 16:11 |
phasefx |
Dyrcona++ |
| 16:11 |
mmorgan |
Dyrcona++ |
| 16:11 |
JBoyer |
Dyrcona++ phasefx++ |
| 16:11 |
mmorgan |
phasefx++ |
| 16:12 |
JBoyer |
Ok, the next is something I may just drop here as a reminder that those of us with Powers(tm) on LP should check out |
| 16:12 |
JBoyer |
#topic Review list of Bug Wranglers (terranm) |
| 16:12 |
JBoyer |
terranm++ |
| 16:12 |
terranm |
https://launchpad.net/~evergreen-bugs/+members |
| 16:12 |
terranm |
Andrea and I noticed at some point during the EG Conf that the bug wrangler list hadn't been cleaned up in a long time. There are 10 or so names I don't even recognize, and several more for people that are no longer actively involved. |
| 16:12 |
terranm |
It seems like the list is overdue for an update, but I don't have the permissions to do that, nor would I feel comfortable making the decisions to downgrade people. |
| 16:14 |
terranm |
I don't have a specific agenda, just thought I'd throw it out there. |
| 16:14 |
mmorgan |
What are the powers of wranglers vs. drivers? |
| 16:15 |
mmorgan |
Also doesn't need to be answered at this meeting :) |
| 16:16 |
Dyrcona |
Drivers can modify releases, etc. Wranglers can modify bugs and target them to releases. |
| 16:16 |
JBoyer |
I'll take this one on and can coordinate with other LP types on the lists or directly and clean things up. Worst case people can be added back to a group if they're removed unexpectedly. |
| 16:17 |
JBoyer |
I do have to disappear though. |
| 16:17 |
terranm |
JBoyer++ |
| 16:17 |
JBoyer |
#topic Announcements |
| 16:17 |
mmorgan |
JBoyer++ |
| 16:17 |
JBoyer |
#info Next Meeting is August 9, 2022 |
| 16:17 |
JBoyer |
#endmeeting |
| 16:17 |
pinesol |
Meeting ended Tue Jul 12 16:17:24 2022 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:17 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-07-12-15.01.html |
| 16:17 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-07-12-15.01.txt |
| 16:17 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2022/evergreen.2022-07-12-15.01.log.html |
| 16:17 |
Dyrcona |
JBoyer++ |
| 16:17 |
JBoyer |
Thanks everybody |
| 16:17 |
Bmagic |
JBoyer++ |
| 16:17 |
phasefx |
JBoyer++ |
| 16:17 |
collum |
JBoyer++ |
| 16:18 |
berick |
JBoyer++ |
| 16:18 |
terranm |
JBoyer++ |
| 16:25 |
shulabear |
Jboyer++ |
| 16:31 |
|
jonadab joined #evergreen |
| 16:35 |
|
akilsdonk joined #evergreen |
| 17:04 |
|
mmorgan left #evergreen |
| 17:12 |
Bmagic |
berick: I loaded that patch on bugsquash (there were two minor conflicts, one for docs and the other for a sql upgrade line, merged onto tags/rel_3_0) |
| 17:12 |
Bmagic |
https://bugsquash.mobiusconsortium.org/eg2/en-US/staff/circ/patron/search |
| 17:12 |
Bmagic |
sorry tags/3_9_0 |
| 17:13 |
Bmagic |
that was a lot* of files :) |
| 20:12 |
|
dbriem joined #evergreen |
| 20:46 |
|
dbriem joined #evergreen |
| 21:32 |
|
dbriem joined #evergreen |
