15:00:19 #startmeeting 2022-05-10 - Developer Meeting 15:00:19 Meeting started Tue May 10 15:00:19 2022 US/Eastern. The chair is JBoyer. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:19 The meeting name has been set to '2022_05_10___developer_meeting' 15:00:27 #info Agenda at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2022-05-10 15:00:33 #topic Introductions 15:00:41 Give deets. 15:00:43 #info terranm = Terran McCanna, PINES 15:00:51 #info JBoyer = Jason Boyer, EOLI 15:00:56 #info shulabear = Shula Link, GCHRL in PINES 15:00:59 #info abneiman = Andrea Buntz Neiman, Equinox 15:01:12 #info mmorgan = Michele Morgan, NOBLE 15:01:22 #info collum = Garry Collum, KCPL 15:01:48 #info Bmagic = Blake GH, MOBIUS 15:01:49 #info Dyrcona = Jason Stephenson, CWMARS 15:03:04 Ok, anyone joining later feel free to #info-out on your way in 15:03:12 #topic Action Items from Last Meeting 15:03:28 The only previous action item involved miker who isn't available, so we'll carry that over 15:03:33 #action miker will may have looked into bug 1955079 15:03:33 Launchpad bug 1955079 in Evergreen "Emailing Bib Records from the catalog (staff and OPAC) reports success, but fails to send email" [High,Confirmed] https://launchpad.net/bugs/1955079 15:03:50 And he left a release update above that should be in the minutes 15:03:54 #topic Evergreen Release Updates 15:04:01 #info From miker earlier today: "we cut 3.9.0 on April 27 and then I was promptly out of the office for travel and not-work until basically today. I did get the tarball and friends up on the downloads site last week, but we had a suspected broken-build issue, which thankfully turned out to be a false alarm, but delayed the release announcement. so, I still owe the world an email to say "come and get it," but you can, indeed, come and 15:04:01 get it. quietest release yet? MAYBE SO" 15:04:09 So, 15:04:10 #action miker will ring the dinnerbell re: Evergreen 3.9.0 on the lists 15:04:25 Actually, re bug 1955079, sandbergja has provide a patch 15:04:34 sandbergja++ 15:04:42 sandbergja++ 15:04:45 ooh, sandbergja++ 15:05:19 sandbergja++ 15:05:23 heya! hope it works :-) 15:06:02 He or others can test it now and see how things shake out instead of worrying about how to solve it. :D 15:06:08 and that branch also includes miker's patch for the staff side 15:07:53 Do we have any volunteers to handle the point releases? I believe there should be a 3.7.3 as a final sendoff to the 3.7 series to go along with 3.8.1 15:09:13 I think our biggest sticking point is release notes for the bug fixes and contributors. The longer we go between releases, the wore work it ends up involving. 15:10:12 if that's a sticking point, I can put some time into release notes later this week 15:10:27 I don't remember if someone is working on release note simplification or if there's something to look over to make it more automatic sitting somewhere. 15:10:43 * mmorgan can also help with release notes. 15:10:58 I have a script that prints out some draft release notes to stdout 15:11:06 I have some ideas to try to automate release note generation or at least commit message summarization, but no time to really work on it. 15:11:07 somewhere... 15:11:18 That may be what I'm thinking of, sandbergja. 15:11:38 bug 1948674 15:11:38 Launchpad bug 1948674 in Evergreen "Improve release building automation" [Undecided,New] https://launchpad.net/bugs/1948674 15:11:55 also: abneiman++ 15:11:58 mmorgan++ 15:12:57 sandbergja: That looks interesting. 15:13:04 if it would help, I'd be happy to run that script and send you the output as a starting place 15:13:30 sandbergja++ 15:13:34 that would be a great start, thanks 15:13:51 sandbergja++ 15:13:58 I have a script that I used at MVLC to come up with summaries of changes for the directors. It can does a git cherry to get the commits since the previous release and then dumps those commit messages into a LibreOffice document. 15:14:10 sandbergja++ 15:14:28 #info phasefx = Jason Etheridge, EOLI 15:14:36 Dyrcona: cool! 15:14:38 abneiman++ mmorgan++ dyrcona++ 15:14:41 I'd like to find time to check that out and see how many of the params can be guessed automagically by the script but I can't promise much at the moment. 15:14:52 But it sounds like an action item 15:15:28 #action sandbergja will prep auto-drafted release notes for abneiman and mmorgan to review for 3.7.3 and 3.8.1 15:15:36 I've been looking at how some other projects do releases, and many have abandoned tarballs. 15:15:39 sandbergja++ abneiman++ mmorgan++ 15:15:59 sandbergja++ abneiman++ mmorgan++ 15:16:19 Dyrcona, and moved to .db / .rpm or what do you mean? 15:16:41 .deb, that is. 15:16:42 They just tag releases in their git repos, and they let others worry about packaging. 15:17:07 Some (mplayer2?) have even abandoned version numbers. 15:18:28 Not sure how well that would play out. I don't think an ILS would fit well on the "The only version you need is the latest one" like a media player or browser. 15:19:05 Missed some words in there. Treadmill was one I believe. 15:19:37 Sure, but we can tag releases. I came across some of this while looking into XMPP issues with OpenSRF on Ubuntu 22.04. 15:19:47 JBoyer: addendum for the meeting, live tester 15:20:01 phasefx++ will add it to new business 15:21:28 Dyrcona, do you think you have time to gather what some other projects do re: releases and put together some possibilities for consideration? 15:21:47 But, it would be nice if we cleaned up our build process so that we could just type 'make release' and have the tarball built for us by autotools. 15:22:23 JBoyer: I might have some time for that. I'll see what I can do. 15:22:26 That would simplify a lot of things, yes. 15:22:29 Dyrcona++ 15:23:22 #action Dyrcona will try to collect data on release processes across some open source projects for consideration 15:23:48 Before moving on to new business I'll drop in the LP update real quick 15:24:02 #topic Launchpad Status 15:24:03 #info Snapshot 15:24:10 #info Open Bugs - 2711 15:24:11 #info Pullrequests - 84 15:24:14 Dyrcona++ 15:24:17 #info Signedoff - 32 15:24:17 #info Updates Since Last Meeting 15:24:20 Dyrcona++ 15:24:21 #info Bugs Added - 31 15:24:27 #info Pullrequest tag Added - 15 15:24:27 * JBoyer #info Signedoff tag Added - 3 15:24:37 #info Signedoff tag Added - 3 15:24:39 #info Fix Committed - 8 15:24:47 mmorgan++ 15:24:59 Ok, new stuff 15:25:01 #topic New Business 15:25:07 #info timeline for deprecating TPAC and the traditional staff catalogue 15:25:11 Take it away, jeffdavis 15:25:27 So, uh, we should decide on a timeline for deprecating those tings. 15:25:34 Is 3.10 reasonable? 15:25:52 +1 15:26:00 They're deprecated already, aren't they? 15:26:15 Well, I mean TPAC is no longer the default. 15:26:36 Since that doesn't mean "remove" I don't see why not. And I'm kind of like Dyrcona, I thought the staff catalog basically was though I don't know that it has actually been spelled out. 15:28:06 * mmorgan would want to see more angular catalog bugs fixed before it's the only option. 15:28:10 I wouldn't necessarily say that tpac has already been deprecated just because it's not the default; to me that would mean it gets nothing but security changes from now on. (Officially, as opposed to just not seeing any improvements) 15:28:20 I think it's valuable to be clear that no bug fixes will be done on the old versions. 15:28:25 It would be nice to have a timeline for removal in addition to just deprecation. I can think of an example of something that was deprecated in 2004 and wasn't removed from Ejabberd until 2021. :) 15:28:42 *cough*xul*cough* 15:29:00 Yup, and that. 15:29:16 We've been solely on the Angular staff catalog and BooPAC since January 2021. 15:29:23 I think XUL was supposed to have been removed by now. 15:30:20 mmorgan: for me, part of the point of deprecation would be setting a clear target for resolving any major bugs still blocking use of the angular catalogue. 15:30:28 Because of the way the "traditional" staff catalog works it will be easiest to remove both together. (not *required*, but significantly simpler.) 15:31:33 And it sends a message to users still using the old interfaces that if they have an issue that's not present in the bootstrap opac or Angular catalog that those are their options for remedy, not an LP bug. 15:32:47 jeffdavis: Makes sense. Essentially applies a deadline to getting those resolved. 15:32:52 +1 15:33:01 And with the improvements to both coming in 3.9+ I think 3.10 is a manageable target for deprecation. Might be trickier to try to determine a drop-dead date today, though. Feeling up for a vote? 15:34:00 I vote in favor of voting on deprecation 15:34:05 If the deprecation target is set, and the major bugs don't get resolved, does deprecation still happen? 15:34:30 mmorgan, major bugs in AngCat and BPAC or the older two? 15:34:45 AngCat and BPAC 15:35:07 When we moved to the web-based client we had a "webstaffblocker" tag in Launchpad and did not release 3.0 until all bugs with that tag were resolved, IIRC. That's what I would want us to do for this too. 15:35:51 Putting a flag in the ground may help get some traction for those bugs now while there's time. And jeffdavis's tag plan would likely also help with that. 15:36:38 And that's still not removal, just "stick these in amber, they're done." 15:36:57 I could've sworn there was an "angcatblocker" tag in LP but I'm not finding it - there is 'boostrap-blocker' https://bugs.launchpad.net/evergreen/+bugs?field.tag=bootstrap-blocker 15:36:58 IIRC there was a similar tag for moving to BooPAC, but the blockers were all resolved ages ago 15:37:22 I have no idea why I cannot be consistent with my usage of quotes, lol 15:37:38 Oh, my apologies, there are a couple still flagged as blockers 15:37:49 abneiman: It's IRC don't sweat it. :) 15:38:02 :') 15:38:29 abneiman: just looks like my early JS cod :) 15:38:40 One of those is only a blocker if using the old staff catalog 15:39:29 And I don't think the third is a blocker either 15:40:17 shulabear: :-D 15:40:26 Not if you have a local workaround (which you do), though it would be convenient to do something genericizable. 15:40:55 OK! Keeping in mind that deprecation is not removal: 15:41:39 #startvote Shall the TPAC and Traditional Staff Catalog(ue) be officially deprecated when 3.10 is released? yes, no, abstain 15:41:39 Begin voting on: Shall the TPAC and Traditional Staff Catalog(ue) be officially deprecated when 3.10 is released? Valid vote options are yes, no, abstain. 15:41:39 Vote using '#vote OPTION'. Only your last vote counts. 15:42:01 #vote yes 15:42:02 #vote yes 15:42:02 #vote yes 15:42:06 #vote yes 15:42:09 #vote yes 15:42:11 #vote yes 15:42:12 #vote yes 15:42:13 #vote yes 15:42:31 #vote yes 15:43:08 +1 to an 'angcatblocker' tag 15:43:21 #endvote 15:43:21 Voted on "Shall the TPAC and Traditional Staff Catalog(ue) be officially deprecated when 3.10 is released?" Results are 15:43:21 yes (9): mmorgan, JBoyer, sandbergja, phasefx, collum, Dyrcona, jeffdavis, terranm, abneiman 15:43:23 There are 82 staff catalog bugs, so I propose - staffcatalogblocker 15:44:00 +1 to staffcatalogblocker 15:44:05 +1 15:44:13 I'll add it 15:44:20 terranm++ 15:44:23 terranm++ 15:44:24 terranm++ 15:44:41 terranm++ 15:44:58 Thanks for bringing that up jeffdavis 15:45:01 jeffdavis++ 15:45:09 jeffdavis++ 15:45:12 jeffdavis++ terranm++ 15:45:27 jeffdavis++ 15:45:40 Ok, and an update from phasefx 15:45:42 #info Live tester update 15:45:48 ha, so speaking of blockers 15:45:57 we should probably start treating the live tester as a blocker 15:46:14 but I disabled it in April for fear that people would become inured to the daily error messages 15:46:27 I confess I haven't had any tuits since then to actually look at what the problem is 15:46:36 http://testing.evergreen-ils.org/~live/archive/2022-04/2022-04-25_16:00:04/test.49.html 15:46:50 phasefx++ # thanks for bringing that up 15:47:08 phasefx++ 15:47:19 phasefx: I think the failing test has to do with missing directories and autogen.sh. It should be resolved now. 15:47:22 And I've seen that same test work on a local testing rig, though not one that's rebuilt from scratch like the live tester is, which is annoying. 15:47:24 so any love that can be put toward it would be much appreciated; I'm about to go on vacation, but will re-enable it; it picks up from a public repo that any commiter should have access to 15:48:11 which repo is it, phasefx? 15:48:29 https://git.evergreen-ils.org/?p=working/random.git;a=shortlog;h=refs/heads/collab/phasefx/eg_live_tests 15:48:46 phasefx++ 15:49:48 EOLI hosts the machine (the test instigator) and the test vm, but in the past we've let community folks into it. I'm sure such can be done again if needed 15:50:02 And to Dyrcona's point above, I believe the autogen patch (and a followup) were already in master and it was still failing. 15:50:46 I think I used to have access to the old tester. I wouldn't mind looking into it. 15:51:54 I'd also like to find time to redo the entire testing setup, but time to do so has not made itself available to me. 15:53:26 It looks like Dyrcona and jeff have both had access in the past and still should (though that machine is not where the testing is actually done, just where the data is gathered) but let me know if you have time to look around and need any help 15:55:06 Ok, any other new business before we wrap up? 15:55:21 JBoyer: I'll wager it 15:55:28 s my old key. 15:55:41 Is there really going to be a June meeting at the same time since that is the EG Conf week? 15:56:51 Ah, I hadn't looked into that. There's no point conflicting with anything in the same timeslot. 15:57:12 Maybe just make the meeting part of the Friday Hackfest? 15:57:20 There is usually a dev meetup at the conference. 15:57:32 Yeahp. 15:57:33 * JBoyer furiously scrolls the conf schedule 15:57:48 During the hackfest? 15:59:05 Yeah, the hackfest seems the best place for it; I don't want to try to take away from csharp_'s sys admin discussion or anything like that. 16:00:21 Is everyone good with 3:00p on June 17th then? 16:00:26 We've usually had them during time when nothing else is going on, so I concur with during the hackfest. 16:01:18 Not hearing any issues, 16:01:22 #topic Announcements 16:01:26 #info Next Meeting is June 17th at 3pm Eastern / 12 Pacific during the Conference Hackfest 16:01:31 #endmeeting