Evergreen ILS Website

IRC log for #evergreen, 2024-08-13

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat

All times shown according to the server's local time.

Time Nick Message
03:03 dmoore joined #evergreen
07:16 kworstell-isl joined #evergreen
07:31 collum joined #evergreen
07:57 BDorsey joined #evergreen
08:01 cbrown joined #evergreen
08:39 mmorgan joined #evergreen
08:39 redavis joined #evergreen
08:40 redavis_reloaded joined #evergreen
08:40 redavis_reloaded joined #evergreen
08:44 redavis joined #evergreen
08:47 dguarrac joined #evergreen
08:57 Stompro redavis, I won't miss the release team meeting today.
09:01 redavis Stompro, I'll see you then :D.  It was a short meeting last time.  Today might be a little longer.  Are you going to be at the dev meeting this afternoon?
09:04 Stompro Yes, I'll be there also.
09:05 redavis Stompro++, I think there will be convo about both 3.14 as well as maintenance releases upcoming.
09:23 redavis https://supabase.com/blog/post​gres-new?utm_source=tldrwebdev
10:26 ian1 joined #evergreen
10:29 redavis Stompro, the most recent discontinuation from Google looks to be the final shutdown of their URL shortener.
10:35 Stompro redavis, I think this explains what is going on with the Hatch warnings.  https://blog.chromium.org/2024/05/​manifest-v2-phase-out-begins.html
10:36 redavis Stompro++, reading
10:40 Christineb joined #evergreen
10:43 redavis Stompro, I don't see a ticket for that.  I'm not sure if there needs to be one though.  I need to run to an appointment, but might also be a thing for the dev meeting.
10:43 * redavis will return
10:44 Stompro It sort of sounds like Hatch could be disabled at any time now after June 3rd... love that feeling.
10:47 csharp_ oof
10:47 csharp_ is there a bug report yet?
10:49 * mmorgan could not find a bug report.
10:51 mmorgan http://irc.evergreen-ils.org/​evergreen/2024-08-08#i_557981
10:52 csharp_ mmorgan++ # thanks
10:58 csharp_ https://bugs.launchpad.net/evergreen/+bug/2076921
10:58 pinesol Launchpad bug 2076921 in Evergreen "Hatch: Chrome Extension Requires Redevelopment" [High,New]
10:58 mmorgan csharp_++
11:20 jvwoolf joined #evergreen
11:34 collum csharp_ - jinx
11:38 csharp_ collum++
11:46 csharp_ @eightball is today the day?
11:46 pinesol csharp_: Maybe...
11:46 csharp_ @eightball is today *a* day?
11:46 pinesol csharp_: The answer is def-- oooh! shiny thing!
11:47 csharp_ @eightball is today D day?
11:47 pinesol csharp_: Naturally.
11:54 jvwoolf joined #evergreen
12:29 jvwoolf joined #evergreen
13:04 collum joined #evergreen
13:21 collum joined #evergreen
13:22 _collum joined #evergreen
13:58 * eeevil installs new zoom for cat IG meeting ... pardon lateness :(
13:58 eeevil zoom--
13:59 jvwoolf joined #evergreen
14:12 * berick had to do the same
14:21 dbriem joined #evergreen
14:22 csharp_ zoom--
14:26 dbriem joined #evergreen
14:46 jvwoolf joined #evergreen
14:51 Bmagic 9 minutes till dev meeting
14:52 shulabear joined #evergreen
14:53 sandbergja joined #evergreen
14:54 smayo joined #evergreen
14:56 collum joined #evergreen
14:59 redavis joined #evergreen
14:59 Bmagic 30 seconds
14:59 Bmagic 10
14:59 Bmagic 5
14:59 redavis The pressure!!
15:00 Bmagic #startmeeting 2024-08-13 - Developer Meeting
15:00 pinesol Meeting started Tue Aug 13 15:00:04 2024 US/Eastern.  The chair is Bmagic. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00 pinesol Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00 pinesol The meeting name has been set to '2024_08_13___developer_meeting'
15:00 Bmagic #info Agenda at https://wiki.evergreen-ils.org/do​ku.php?id=dev:meetings:2024-08-13
15:00 Bmagic #topic Introductions
15:00 Bmagic #info Bmagic = Blake GH, MOBIUS
15:00 scottangel #info scottangel = Scott Angel, MOBIUS
15:00 redavis #info redavis - Ruth Frasur Davis, ECDI
15:00 Stompro #info Stompro = Josh Stompro, LARL
15:00 sandbergja #info sandbergja = Jane Sandberg, PUL
15:00 sleary #info sleary = Stephanie Leary, Equinox
15:00 shulabramble #info shulabramble = Shula Link, GCHRL
15:00 mmorgan #info mmorgan = Michele Morgan, NOBLE
15:00 collum #info collum = Garry Collum, KCPL
15:00 smayo #info smayo = Steven Mayo, PINES
15:01 berick #info berick Bill Erickson, KCLS
15:01 eeevil #info eeevil = Mike Rylander, EOLI
15:01 Bmagic feel free to introduce yourself as you arrive
15:01 terranm joined #evergreen
15:01 abneiman #info abneiman = Andrea Buntz Neiman, Equinox
15:01 terranm #info terranm = Terran McCanna, PINES
15:01 Bmagic #topic Action Items from Last Meeting
15:02 Bmagic mmorgan - should I skip?
15:02 jeff #info jeff = Jeff Godin, Traverse Area District Library (TADL)
15:02 mmorgan Bmagic: I opened the bug - bug 2076932
15:02 pinesol Launchpad bug 2076932 in Evergreen "Launchpad Statistics Tracking" [Undecided,New] https://launchpad.net/bugs/2076932
15:02 Bmagic oh!
15:02 Bmagic #info mmorgan will open a ticket for moving LP stats to community site & automating same
15:02 Bmagic #info https://launchpad.net/bugs/2076932
15:02 sandbergja mmorgan++
15:02 redavis mmorgan++
15:02 Bmagic mmorgan++
15:02 shulabramble mmorgan++
15:03 mmorgan Feel free to add code, ideas, etc.
15:03 Bmagic #link https://launchpad.net/bugs/2076932
15:03 pinesol Launchpad bug 2076932 in Evergreen "Launchpad Statistics Tracking" [Undecided,New]
15:03 Bmagic I meant link
15:03 dluch #info dluch = Debbie Luchenbill, MOBIUS
15:04 Bmagic Any discussion on that?
15:04 mmorgan Hopefully the bug will gather some! I will add some of the scripts I tried with lp api.
15:04 dluch mmorgan++
15:04 jvwoolf #info jvwoolf = Jessica Woolford, Bibliomatin
15:05 Bmagic mmorgan: great work
15:05 Bmagic I do like knowning the big picture
15:05 Bmagic ok, next up
15:05 Bmagic #info eeevil will open a bug for cross-column stats targets
15:06 eeevil ha! nope... not this month :(
15:06 Bmagic #action eeevil will open a bug for cross-column stats targets
15:06 Bmagic no worries
15:06 Bmagic #info gmcharlt - create a Git commit message type and update bug 2051946
15:06 pinesol Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] https://launchpad.net/bugs/2051946 - Assigned to Galen Charlton (gmc)
15:06 abneiman Galen is away
15:06 eeevil I'll make a stub soon, but $someone will need to spend time digging through "slow" query logs...
15:06 Bmagic eeevil++
15:07 Bmagic #action gmcharlt - create a Git commit message type and update bug 2051946
15:07 Bmagic #info redavis will look at making a regular calendar event for translation work in lock step with point releases
15:07 redavis gonna give that a pass this month.  I've not forgotten though.
15:07 redavis please carry over to next month
15:08 Bmagic ok, perfect. Thanks for keeping it in mind
15:08 Bmagic #action redavis will look at making a regular calendar event for translation work in lock step with point releases
15:08 Bmagic #info Dyrcona will look into git integration with POEditor
15:09 redavis Dyrcona is out of office currently
15:09 Bmagic oh, lol, I was about to say something like "must be a lot of typing"
15:10 Bmagic but I see he's MIA
15:10 Bmagic #action Dyrcona will look into git integration with POEditor
15:10 Bmagic #info sandbergja, abneiman, redavis, and mmorgan will put out said point release
15:10 abneiman hey we deffo did that
15:10 sandbergja yeah, with Dyrcona's help!
15:10 redavis Said point releases went out on July 19. 3.11.7, 3.12.5 and 3.12.2
15:10 Bmagic deffo cool!
15:10 sleary sandbergja++ abneiman++ redavis++ mmorgan++
15:10 mmorgan :)
15:11 redavis with Dyrcona's immense help
15:11 jvwoolf sandbergja++ abneiman++ redavis++ mmorgan++
15:11 jvwoolf Dyrcona++
15:11 Bmagic sandbergja++ abneiman++ redavis++ mmorgan++ Dyrcona++
15:11 mmorgan sandbergja++ abneiman++ redavis++ Dyrcona++
15:11 sleary Dyrcona++
15:11 redavis Dyrcona++ sandbergja++ abneiman++ mmorgan++
15:11 Bmagic #info abneiman will review existing EOLI PRs for test plans
15:11 shulabramble Dyrcona++ sandbergja++ abneiman++ mmorgan++
15:12 abneiman I reviewd them but did not add test plans to any. Will do so in advance of BSW.
15:13 Bmagic abneiman++
15:13 sandbergja abneiman++ # that's awesome
15:13 shulabramble abneiman++
15:13 redavis abneiman++
15:13 dluch abneiman++
15:13 Bmagic want that carried?
15:14 jvwoolf abneiman++
15:14 abneiman nah
15:14 Bmagic #info abneiman will add a discussion item for next meeting: test plans for big features
15:14 abneiman I ninja-edited that into the agenda 10 minutes ago :)
15:14 Bmagic I see that, lol
15:14 * redavis was also ninja editing
15:14 dluch sandbergja++ abneiman++ redavis++ mmorgan++ (belatedly, lol)
15:14 Bmagic alright, that does it for last meeting stuffs
15:15 Bmagic #topic Evergreen
15:15 dluch ninja-editing++
15:15 Bmagic #info Roadmap: Evergreen Development Roadmap
15:15 Bmagic #link https://wiki.evergreen-ils.org/do​ku.php?id=faqs:evergreen_roadmap
15:16 redavis Um...the 3.14 release team has been meeting...
15:16 shulabramble ninjas++ editing++
15:16 Bmagic i guess it's 3 o' clock .14 somewhere
15:16 jvwoolf redavis: Should we share the Launchpad tracking sheet? Or is it not ready for prime time yet?
15:16 Bmagic who's working on the pi graphic for the release?
15:16 redavis It's Dyrcona, Stompro, jvwoolf, and myself
15:17 redavis jvwoolf, I think it's fine to share, but definitely a working document
15:17 Bmagic feel free to hash link it
15:18 redavis Stompro and Dyrcona worked through some postgresql 16 and ubuntu 24 things and that all is "ready to go."  Next up is Bug Squash Week...
15:18 Bmagic whoohoo!
15:18 Bmagic new_postgres++
15:18 redavis The 3.14 roadmap wiki page is a living document as always but here is what's shaping up so far - https://wiki.evergreen-ils.org/doku​.php?id=faqs:evergreen_roadmap:3.14
15:19 redavis Here's our launchpad tracking sheet right now...https://docs.google.com/spreadsheets/d/1xodq5mLdU7​Cjlw-gi8KYAyI6wmfGKRYUE7LYDdpscJY/edit?usp=sharing
15:20 Bmagic I love the organization of it
15:20 Bmagic friggin_spreadsheets++
15:20 redavis So, there are a lot of things that had a 3.next target that were just kind of hanging on each release.  We're working on going through those, but others might want to take a look.  We also have page as yet unpopulated for things we might pass on to Terran for BSW
15:20 abneiman whoa, total spreadsheet props
15:20 jvwoolf redavis++ #for keeping us on task
15:20 abneiman redavis++
15:20 * redavis also loves a spreadsheet
15:20 sleary thank you all for cleaning out the 3.next target
15:21 terranm Nice!
15:21 terranm redavis++
15:21 redavis All the LP foo from jvwoolf on that.
15:21 redavis jvwoolf++
15:21 terranm jvwoolf++
15:21 Bmagic jvwoolf++
15:21 abneiman jvwoolf++
15:22 Bmagic release_team++
15:22 shulabramble jvwoolf++ redavis++
15:22 sandbergja jvwoolf++ redavis++ Stompro++ Dyrcona++
15:22 mmorgan Dyrcona++ jvwoolf++ redavis++ Stompro++
15:22 sandbergja 3.14 is going to be so cool!
15:22 shulabramble stompro++ dyrcona++
15:22 * sleary wishes a happy tenth birthday to several of those 3.next bugs
15:22 Bmagic Dyrcona++ jvwoolf++ redavis++ Stompro++
15:22 dluch redavis++ jvwoolf++ Stompro++ Dyrcona++
15:22 redavis Oh...I guess we're talking about releases.  There are going to be some point releases next week (please volunteer ye ol' buildmasters)
15:23 Bmagic lol, ten years! Like a fine wine. But don't drink 'em
15:23 Bmagic #info Maintenance releases 3.11.7, 3.12.5, 3.13.2 on July 19.
15:23 abneiman lolsob
15:23 Bmagic #info Merge Pause on Friday, August 16. Should be able to lift pause on Tuesday, August 20.
15:23 Bmagic #info 3.13.3 and 3.12.6 monthly maintenance releases on Wednesday, August 21.
15:24 Bmagic redavis prompted me to info those
15:24 sandbergja are they on the 19th or 21st?
15:24 redavis Volunteers for building the releases will be heartily compensated (with many accolades of praise...until the next release(s))
15:24 Bmagic I'm availablel for building next week
15:25 sandbergja oh whoops, I was reading the July thing, ignore me
15:25 redavis Bmagic++
15:25 sandbergja I could help on the 21st too
15:25 * mmorgan can help
15:25 redavis sandbergja, I wrote the stuff and still asked the exact same question to myself more than once.
15:25 abneiman I signed myself up for release notes, which I can do early next week
15:26 Bmagic abneiman++
15:26 redavis Great.  I'll send out an email to bmagic, sandbergja, abneiman (cuz I see your release notes name on the spreadsheet) to see if we can schedule a quick talk time.
15:26 Bmagic redavis++
15:26 Bmagic good idea
15:26 sleary I might be around, but at the very least I can help with web uploading/updating
15:26 sandbergja redavis++
15:26 Bmagic sleary++
15:26 redavis sleary++
15:26 mmorgan redavis: I can help too.
15:26 Bmagic mmorgan++
15:26 redavis lol, alright, including all y'all!
15:27 Bmagic blamo
15:27 Bmagic #info Bug squash week for 3.14 release, August 26-30.
15:27 Bmagic terranm++
15:27 redavis terranm++
15:28 mmorgan terranm++
15:28 sleary terranm++
15:28 shulabramble terranm++
15:28 terranm Yep 10 year anniversary, let's make it good!
15:28 sandbergja terranm++
15:28 jvwoolf terranm++
15:28 redavis 10 year anniversary and PIE!!!!!
15:28 Bmagic I can't believe it, we've been doing BSW for 10 years, OMG
15:28 dluch terranm++
15:29 Bmagic moving onto docs
15:29 Bmagic #topic Documentation
15:29 Bmagic #info DIG met on August 1
15:29 Bmagic #info We are running our style guide through Vale to find errors in the docs. Images without alt tags was first–all fixed now! Next up is consistent word use for certain terms
15:29 Bmagic #info Plans to work on docs bugs and especially reviewing older bugs during Bug Squashing Week
15:29 Bmagic #info Next meeting, September 5
15:29 Bmagic dluch you have the floor
15:31 dluch Sorry, I was distracted, lol
15:31 dluch I don't have anything else to add. Any questions? Any other DIGgers want to add/comment?
15:32 Bmagic cool about Vale
15:32 Bmagic dluch++
15:32 shulabramble dluch++ bmagic++
15:32 dluch shoutout to sandbergja for Vale!
15:33 Bmagic sandbergja++
15:33 redavis dluch++ DIG++
15:33 dluch sandbergja++
15:33 shulabramble sandbergja++
15:33 redavis sandbergja++
15:33 dluch DIG++
15:33 Bmagic DIG++
15:33 mmorgan sandbergja++
15:33 Bmagic #topic Launchpad Status (as of noon Eastern)
15:33 Bmagic hit the deck, we got incoming!
15:33 Bmagic #info Open Bugs - 3119
15:33 Bmagic #info Pullrequests - 96
15:33 Bmagic #info Signedoff - 15
15:34 Bmagic #topic Launchpad Status since last meeting
15:34 Bmagic #info Bugs Added - 69
15:34 Bmagic #info Pullrequest tag Added - 29
15:34 Bmagic #info Signedoff tag Added - 18
15:34 Bmagic #info Needswork tag Added - 2
15:34 Bmagic #info Needstestplan tag Added - 0
15:34 Bmagic #info Needsrebase tag Added - 5
15:34 Bmagic #info Fix Committed - 22
15:34 Bmagic #topic New Business - (Jane) How can we encourage more automated testing?, What are current barriers to writing and running the automated tests?
15:34 sandbergja ok, my turn to paste some stuff:
15:34 Bmagic #link https://wiki.evergreen-ils.org/​doku.php?id=dev:contributing:qa
15:34 sandbergja During the 3.12 and 3.13 release process, we found a number of big issues that we were able to resolve before cutting the release, for example:
15:34 sandbergja an unpredictable intermittent failure in search, a bug that prevented users from adding new action trigger event defs, a case where I had committed the wrong patch from a launchpad ticket, one where the holdings view wouldn't load, and a major accessibility regression that detached form inputs from their labels across the client.
15:35 sandbergja And the way we found those was by one of our automated tests failing, alerting us to the issue, which is great!  Very nice that we discovered those before they were in production.
15:35 sandbergja However, it makes me think how many more regressions we could be catching if we'd been writing and running tests more often over the past 9 years.
15:35 sandbergja So... I'd like to know: how can we get there?  What barriers can we iron out around automated testing?
15:36 redavis sandbergja++
15:36 shulabramble sandbergja++
15:37 Bmagic those node nightwatch tests are clever. Automating the process of clicking on the interface like a human would. Not sure what the barriers are? Hard to write?
15:38 sleary IIRC there are two (maybe three?) different QA/guideline documents for contributions that have different instructions, and we need to consolidate them into one coherent process.
15:38 Bmagic consolidate! +1. Got links?
15:38 Stompro For me personally it is just the time it takes to create the tests, but I know if I do it more often it wouldn't take me as long.
15:39 sleary working on links
15:40 sandbergja Stompro++ sleary++ Bmagic++
15:41 Bmagic giving sleary a minute
15:41 sleary https://wiki.evergreen-ils.org/doku.p​hp?id=dev:angular_dev_best_practices
15:42 Bmagic I know there is one out ther esomewhere for PG and one for perl
15:42 sleary https://wiki.evergreen-ils.org/​doku.php?id=dev:contributing:qa
15:43 Bmagic there it is
15:43 Bmagic that's the one I was thinking of
15:43 Bmagic sleary++
15:43 sandbergja consolidating and refining those seems like a great place to start
15:43 sleary https://wiki.evergreen-ils.org/doku.p​hp?id=dev:meetings:common_qa_problems might also be relevant
15:44 terranm +1 to a single page just about writing tests
15:44 Bmagic do we need to make assignments around this?
15:44 sleary sandbergja I will be happy to help with that... about a month from now, lolsob
15:44 Bmagic sleary++
15:44 terranm sleary++ sandbergja++
15:44 shulabramble +1 to a page about writing tests
15:44 sandbergja a month sounds great!  And I'm also happy to help as needed!
15:45 mmorgan +1 to a page about writing, and also running them
15:45 jeff do we need to do anything to remove barriers to running the tests? i.e., is setting up an environment where you can run the tests challenging or not-well-documented?
15:45 redavis sandbergja++ sleary++
15:45 sleary I know that sandbergja has given a couple of talks in New Devs about test-driven development, and we can pull things from those meeting archives
15:45 redavis jeff, good question
15:45 Bmagic #action sleary and sandbergja will create/consolidate the test writing wiki page(s)
15:45 terranm It always makes sense when I watch Jane do it, but then confusion returns
15:46 Bmagic jeff: the docker container image now days is including the pre-reqs which is nice
15:46 sleary jeff I think there is one quirk around Firefox, but it's mentioned in the eg2 CHEAT SHEET doc
15:46 Bmagic Imma preserve those wiki urls
15:46 sandbergja for me, reloading a test database from scratch can take a while, and a clean db is necessary for some of the tests
15:46 Bmagic #link https://wiki.evergreen-ils.org/doku.p​hp?id=dev:meetings:common_qa_problems
15:47 Bmagic #link https://wiki.evergreen-ils.org/​doku.php?id=dev:contributing:qa
15:47 Bmagic I added a feature to the the dev container, which I find myself using a bunch, that automates the creation of new databases by editing a text file
15:47 sleary the e2e tests take a while to run, and the syntax for running them on a single file or directory is not easy to remember
15:48 sandbergja true sleary
15:48 sleary we can probably script our way out of that problem :)
15:48 sandbergja Bmagic I know you've told me this before, but I gotta start using the dev containers!
15:49 Bmagic sandbergja: the water is fine, lol
15:49 Bmagic the takeaway was consolidating the wiki pages
15:50 Bmagic shall we add something else?
15:50 sleary maybe step 2 can be writing some simple example tests or pinpointing old ones as good examples for basic tasks
15:50 sandbergja maybe as part of that process we can look into the syntax for nightwatch on a single file or directory -- whether it is a docs fix or a script fix?
15:51 sleary sandbergja++
15:52 Bmagic making sure I'm understanding: making the test run differently depending on what was committed?
15:52 sleary running the tests on only the files you changed rather than the whole Angular project
15:52 Bmagic gotcha, and what's missing for that to work?
15:52 sleary memorable syntax
15:53 Bmagic documentation is missing basically?
15:53 sleary it's documented in the Nightwatch docs, but it's hard to remember
15:53 sleary not sure it's in our cheat shee
15:53 sleary sheet
15:53 eeevil I would appreciate a how-to, for sure. fwiw
15:53 sandbergja so better syntax and better docs perhaps
15:54 Bmagic maybe a wrapper that takes some evergreen-community arguments. like ./wrapper --one-test path/to/file
15:54 sleary that's what I was thinking, but docs would be simpler :)
15:54 Bmagic docs would be simplier :)
15:55 dluch docs++ ;-)
15:55 Bmagic I suppose that can be part of the same action? Or woudl you like a new action? Anyone want to put their name on it?
15:56 sleary that should probably be a separate action from the wiki page consolidation
15:56 Bmagic would you like to have it?
15:56 sandbergja you could put my name on it
15:56 Bmagic #action sandbergja will make it easier for folks to know how to run the tests in single file mode and all-mode
15:57 Bmagic sandbergja++
15:57 sleary sandbergja++
15:57 sandbergja thanks everyone!
15:57 sleary thanks for bringing up this topic!
15:57 mmorgan sandbergja++
15:57 Bmagic we're coming up on the hour
15:57 Bmagic #topic New Business - Hatch extension 'may soon no longer be supported' Hatch Chrome Extension
15:57 Bmagic #link https://chromewebstore.google.com/detail/hatch-n​ative-messenger/ppooibdipmklfichpmkcgplfgdplgahl
15:57 shulabramble sandbergja++
15:57 dluch sandbergja++
15:58 berick count me in for helping with Hatch work.  hopefully i can pitch in starting next week
15:58 * berick runs off to another meeting
15:58 jeff happy to help / help test.
15:58 Bmagic berick++
15:58 Bmagic jeff++
15:58 sandbergja berick++ jeff++
15:58 mmorgan csharp opened bug 2004058
15:58 jeff also, noting for the benefit of any who have the ability to make use of policies across their chrome fleet:
15:58 jeff > Enterprises using the ExtensionManifestV2Availability policy to ensure the continued functioning of Manifest V2 extensions in their organization will have one additional year - until June 2025 - to migrate the Manifest V2 extensions in their organization. Browsers with the policy enabled won't be impacted by the rollout of the deprecation until that time.
15:59 jeff ( from https://developer.chrome.com/docs/extension​s/develop/migrate/mv2-deprecation-timeline )
15:59 jeff I'll also add that to the bug as a comment.
15:59 mmorgan berick++ jeff++
15:59 Bmagic #action berick and jeff will look at making Hatch look better in the chrome store, so that it's not removed
15:59 Bmagic #topic New Business - DokuWiki needs updating
16:00 sleary that was me! Just a note for those of us who have website/db access; we should update
16:00 dluch berick++ jeff++
16:00 Bmagic I see, you mean upgrade dokuwiki version
16:00 sleary yes
16:01 Bmagic cool, who usually does that?
16:01 Bmagic do we have a dev environment to make sure the upgrade works before doing it for real?
16:01 abneiman I think has fallen on Rogan and/or Galen the last few times
16:01 sleary csharp_ most likely. I think I can, but I'm reluctant to touch things without taking time to make my own backups
16:02 Bmagic I can help too :)
16:02 Bmagic #action Bmagic will work on upgrading the version of DokuWiki
16:03 Bmagic #topic (ABN) Test plans for big features?
16:03 Bmagic We're almost done... sorry we're going over
16:03 abneiman yes, so, briefly
16:03 abneiman what does the community want to / need to see out of test plans for new features?
16:04 abneiman things that are beyond the scope of "X is broken, install patch Y, follow steps 1 2 3, profit"
16:04 Bmagic are you finding that certain things need more than our bsw and bff ?
16:04 abneiman asking because several EOLI feature PRs are either forthcoming soon, or carryovers from 3.13, and I want to make sure I'm doing what is needed to facilitate review & commit of those things
16:05 Stompro I always appreciate notes on how to configure the system if certain lib settings need to be enabled, etc.
16:05 jeff varies, but maybe starting with: "here is a summary of / pointer to description of what this code should add/change/fix; here is a recommended way to test / how we tested; here are special considerations / gotchas"?
16:05 abneiman Stompro++ jeff++
16:05 mmorgan What Stompro said. Also if certain data is needed.
16:05 abneiman both helpful thanks
16:05 abneiman mmorgan++
16:06 redavis Stompro++ jeff++ mmorgan++
16:06 abneiman and Bmagic, regarding BSW, I acknowlege that it's hard to test big features when there's a lot of other fixes flying around ... which is fine, IMO, that's what BSW is about.
16:06 Bmagic Stompro++ jeff++ mmorgan++
16:07 Bmagic abneiman++ # I think I took your query the wrong direction after reading Stompro, jeff and mmorgan's ideas
16:07 abneiman like I said, I want to make sure we're doing what we can to faciliate merges of features. And to maybe offer similar guidelines to other feature developers
16:07 sandbergja abneiman++
16:07 shulabramble abneiman++
16:07 mmorgan abneiman++
16:08 Bmagic thanks all, just a couple things and we're outta here
16:08 Bmagic #topic Announcements
16:08 abneiman anyway, I appreciate the thoughts shared ... any others can come to me here, or directly at abneiman@equinoxoli.org and I'll put them.... somewhere public
16:08 terranm abneiman++
16:08 dluch abneiman++
16:08 Bmagic #info Next Meeting is Tuesday, September 10th 2024
16:08 Bmagic #info Hack-A-Way, November 12-14 in Boston, MA
16:08 Bmagic #endmeeting
16:08 pinesol Meeting ended Tue Aug 13 16:08:34 2024 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:08 pinesol Minutes:        http://evergreen-ils.org/meetings/evergr​een/2024/evergreen.2024-08-13-15.00.html
16:08 pinesol Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2024/evergreen.2024-08-13-15.00.txt
16:08 pinesol Log:            http://evergreen-ils.org/meetings/evergree​n/2024/evergreen.2024-08-13-15.00.log.html
16:08 mmorgan Bmagic++
16:08 redavis And the Hack-A-Way page is linked in the agenda. It seems far away but isn't.
16:08 redavis Bmagic++
16:09 dluch Bmagic++
16:09 terranm Bmagic++
16:09 shulabramble bmagic++
16:09 jvwoolf Bmagic++
16:09 jvwoolf Anybody know if there will be a virtual component to the Hack-A-Way this year?
16:10 redavis jvwoolf, not sure yet.  But Rogan might know
16:12 jvwoolf If there is any way I can assist with making that happen, let me know! I would like to attend, but in person will be hard for me until the baby gets a bit bigger.
16:12 redavis jvwoolf++
16:13 Bmagic jvwoolf: I don't think you're alone. I think it's a great idea to offer remote attendance. Easier said than done, I'm sure.
16:15 redavis It gets a little easier each time from a technology standpoint. From a venue standpoint, there are some unknowns right now.  I'll ask at the next outreach meeting.
16:20 jvwoolf redavis++
16:20 jvwoolf left #evergreen
16:40 csharp_ sleary: Bmagic: re: dokuwiki - users with admin rights can update via the GUI fwiw
16:41 Bmagic csharp_: that sounds super easy
16:41 csharp_ yep, and quick
16:41 csharp_ just back up the folder for safety
16:41 Bmagic do you have an reservations about clicking on it without testing it on a cloned env?
16:41 csharp_ nah, I've done it several times
16:42 Bmagic ok then, sounds like it's in good hands!
16:42 csharp_ we do keep backups for 30 days on that server at ITS also
16:42 Bmagic perfect
16:42 csharp_ file-level browseable backups via Dell Avamar
16:42 Bmagic aint dell grand
16:43 csharp_ so dell
16:43 Bmagic lol
16:52 jeff so dell. much dude. very michael.
17:04 mmorgan left #evergreen
17:10 sleary csharp_: cool! Thanks!
17:57 sleary Wiki updated. Refresh if you see the logo as a repeating background.
18:11 Bmagic sleary++
18:54 eby joined #evergreen
18:55 degraafk joined #evergreen
19:09 eglogbot joined #evergreen
19:09 Topic for #evergreen is now Welcome to #evergreen (https://evergreen-ils.org). This channel is publicly logged. Logs for today: http://irc.evergreen-ils.org/evergreen/today

| Channels | #evergreen index | Today | | Search | Google Search | Plain-Text | summary | Join Webchat