| Time |
Nick |
Message |
| 07:09 |
|
collum joined #evergreen |
| 08:31 |
|
mmorgan joined #evergreen |
| 08:31 |
|
Lorne joined #evergreen |
| 09:20 |
csharp_ |
Lorne: make sure apt works on the AWS machine? (e.g., apt update) |
| 09:21 |
csharp_ |
could be networking, bad repo mirror, etc. |
| 09:23 |
Lorne |
Aha, thanks csharp_. That may explain Andydude's problem from earlier as well. |
| 10:05 |
|
redavis joined #evergreen |
| 10:18 |
|
dguarrac joined #evergreen |
| 10:33 |
|
Lorne joined #evergreen |
| 10:34 |
Lorne |
Apt-get confirmed working on AWS Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-1029-aws x86_64). It probably is a bad repo problem then. I can look at documenting that piece. |
| 11:09 |
csharp_ |
Lorne: if apt-get update works fine, the repos probably aren |
| 11:09 |
csharp_ |
t the problem |
| 11:10 |
|
Christineb joined #evergreen |
| 11:11 |
Lorne |
Oh, I thought you meant Evergreen's repo? When running Ansible script it just times out here: |
| 11:11 |
Lorne |
TASK [Build Evergreen] *********************************************************************************************************************************************************************** |
| 11:11 |
Lorne |
included: /home/ubuntu/evergreen-ansible-installer/evergreen/eg-build.yml for 127.0.0.1 |
| 11:11 |
Lorne |
TASK [Checkout Evergreen Repository] ********************************************************************************************************************************************************* |
| 11:11 |
Lorne |
changed: [127.0.0.1] |
| 11:11 |
Lorne |
TASK [Install Evergreen Prereqs] ************************************************************************************************************************************************************* |
| 11:13 |
Lorne |
Anyway, I will probably continue with Azure as I've had best results there. |
| 11:15 |
berick |
Lorne: ansible-playbook -v (or -vv, etc.) will provide more details |
| 11:17 |
csharp_ |
Lorne: I've seen Ubuntu (not on AWS or Azure) hang when installing ejabberd - could be something like that |
| 11:18 |
csharp_ |
Lorne: that step just automates this: https://evergreen-ils.org/documentation/install/README_3_15.html#_installing_prerequisites |
| 11:18 |
csharp_ |
s/step/task |
| 11:19 |
csharp_ |
@blame ejabberd |
| 11:19 |
pinesol |
csharp_: ejabberd broke Evergreen. |
| 11:19 |
csharp_ |
pinesol: no doubt |
| 11:19 |
pinesol |
csharp_: IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! |
| 11:19 |
csharp_ |
pinesol: that's always possible though |
| 11:19 |
pinesol |
csharp_: OK BOOMER |
| 11:19 |
Lorne |
I did have issues with ejabberd when trying a local install "by hand" (i.e. the documentation). |
| 11:20 |
csharp_ |
yeah |
| 11:20 |
csharp_ |
Lorne: if you're comfortable using the redis version, you can skip the ejabberd nightmare |
| 11:20 |
csharp_ |
looking forward to that being default, for my part |
| 11:22 |
Lorne |
I am working towards delivery of pre-packaged ILS to library partners. Is there a "packaged" version with Redis, if a library had a requirement to use redis only? |
| 11:23 |
csharp_ |
Lorne: as in APT (deb) package? or a container? or what? |
| 11:24 |
Lorne |
Yes, a deb package or Ansible installer |
| 11:25 |
Lorne |
Something where I write a script with 5 lines and it does the heavy lifting. |
| 11:25 |
Lorne |
or I press a button |
| 11:26 |
csharp_ |
Lorne: given that it's gotten a lot of activity/attention, I would tend towards Ansible at this point |
| 11:27 |
csharp_ |
if you're curious, though, check out our (PINES's) deb building efforts here: https://git.evergreen-ils.org/ (contrib/pines/eg-debian.git and contrib/pines/osrf-debian.git) |
| 11:27 |
|
jihpringle joined #evergreen |
| 11:27 |
berick |
Lorne: the Ansible installer you are using is Redis-based and should not be install Ejabberd |
| 11:27 |
csharp_ |
I intend to revamp those to be more faithful to current deb packaging guidelines, but you know, time |
| 11:28 |
Lorne |
Thank you berick, that's good to know |
| 11:28 |
Lorne |
Thank you csharp_ for background |
| 11:28 |
csharp_ |
Lorne: sure thing |
| 11:29 |
berick |
my new tattoo: should not be install Ejabberd |
| 11:29 |
Lorne |
So Ubuntu hates ejabberd, and something in AWS hates Ansible. Fun times :D |
| 11:30 |
csharp_ |
Lorne: also see bug 1880703 for attempts to expand out from Debian/Ubuntu |
| 11:30 |
pinesol |
Launchpad bug 1880703 in OpenSRF "Wishlist: RHEL/Rocky Support" [Wishlist,New] https://launchpad.net/bugs/1880703 - Assigned to Chris Sharp (chrissharp123) |
| 11:34 |
csharp_ |
berick++ |
| 12:15 |
|
jihpringle joined #evergreen |
| 13:46 |
|
redavis joined #evergreen |
| 14:09 |
|
terranm joined #evergreen |
| 14:10 |
|
jihpringle joined #evergreen |
| 14:13 |
|
shulabramble joined #evergreen |
| 14:13 |
shulabramble |
47 minutes until we ball (Developers' Meeting) |
| 14:19 |
|
jihpringle97 joined #evergreen |
| 14:31 |
shulabramble |
29 minute warning because I got distracted for a minute |
| 14:39 |
pinesol |
News from commits: LP2115535 Basket nav markup, ARIA label <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=1153f4784c1cd4bb4b3ca9dd6c5a9c46d23f10a2> |
| 14:45 |
shulabramble |
15 minute warning! |
| 14:46 |
|
mdriscoll joined #evergreen |
| 14:47 |
|
jihpringle joined #evergreen |
| 14:50 |
shulabramble |
10 minutes. time enough for many things. |
| 14:51 |
shulabramble |
...got that one in right under the buzzer |
| 14:54 |
abneiman |
csharp_: actual LOL at pinesol's sassing of me yesterday |
| 14:55 |
|
mantis joined #evergreen |
| 14:55 |
abneiman |
and of course, your kind defense |
| 14:55 |
csharp_ |
abneiman: I live to defend you milady |
| 14:55 |
abneiman |
:-D |
| 14:55 |
* gmcharlt |
blows dust off |
| 14:55 |
* csharp_ |
coughs dramatically |
| 14:56 |
abneiman |
I feel as though the whole middle aged experience can be summed up as "has bugs" |
| 14:56 |
csharp_ |
no joke |
| 14:56 |
|
collum joined #evergreen |
| 14:56 |
gmcharlt |
but also: "less ability to fling servers around" |
| 14:56 |
abneiman |
"not to specification, not cleared for general release" |
| 14:56 |
csharp_ |
gmcharlt: feeling that too |
| 14:58 |
shulabramble |
i have developed many hardware bugs in addition to someone trying to mount an m4 processor on an intel motherboard. |
| 14:58 |
Rogan |
I don't know what anyone means. Excuse me while I take medicine for pains from sitting motionless. |
| 14:59 |
csharp_ |
yeah, GenXers' parents warned us against strangers, drugs, guns, etc., but never about *sitting* |
| 15:00 |
|
jihpringle53 joined #evergreen |
| 15:00 |
shulabramble |
I was way more worried about catching on fire and quicksand than it turns out i needed to be |
| 15:00 |
shulabramble |
#startmeeting 2025-07-08 - Developer Meeting |
| 15:00 |
pinesol |
Meeting started Tue Jul 8 15:00:16 2025 US/Eastern. The chair is shulabramble. 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 '2025_07_08___developer_meeting' |
| 15:00 |
csharp_ |
shulabramble++ |
| 15:00 |
shulabramble |
Okay, y'all! |
| 15:00 |
|
sandbergja joined #evergreen |
| 15:00 |
shulabramble |
#topic Intros |
| 15:00 |
shulabramble |
#info shulabramble = Shula Link, GCHRL |
| 15:00 |
redavis |
#info redavis = Ruth Frasur Davis, ECDI and my own open-source ILS lovin' self. |
| 15:00 |
sandbergja |
#info sandbergja = Jane Sandberg, PUL |
| 15:01 |
Rogan |
#info Rogan = Rogan Hamby, EOLI |
| 15:01 |
abneiman |
#info abneiman = Andrea Buntz Neiman, EOLI |
| 15:01 |
collum |
#info collum = Garry Collum, KCPL |
| 15:01 |
sleary |
#info sleary = Stephanie Leary, EOLI |
| 15:01 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:01 |
gmcharlt |
#info gmcharlt = Galen Charlton, Equinox |
| 15:01 |
mdriscoll |
#info mdriscoll = Martha Driscoll, NOBLE |
| 15:01 |
phasefx |
#info phasefx = Jason Etheridge, EOLI |
| 15:01 |
jeff |
#info jeff = Jeff Godin, Traverse Area District Library (TADL) |
| 15:01 |
terranm |
#info terranm = Terran McCanna, PINES |
| 15:02 |
shulabramble |
We've got potentially lengthy discussions at the end of this so lets forge on, people can continue introductions as they filter in |
| 15:02 |
csharp_ |
#info csharp = Chris Sharp, GPLS |
| 15:02 |
shulabramble |
#topic Action Items from Last Meeting |
| 15:02 |
shulabramble |
#topic sleary and sandbergja will report progress on test writing wiki pages next month |
| 15:03 |
sleary |
updates! I added a couple links to the agenda |
| 15:03 |
shulabramble |
#info https://wiki.evergreen-ils.org/doku.php?id=dev:contributing:qa#common_things_that_break_angular_unit_tests |
| 15:03 |
shulabramble |
#info custom ESLint rules, e.g. #lp2019139 |
| 15:04 |
shulabramble |
#info custom ESLint rules, e.g. lp2019139 |
| 15:04 |
abneiman |
sleary++ sandbergja++ |
| 15:04 |
sleary |
sandbergja and I are working on adding some common "if you changed X in your code, you'll need to do Y in the unit tests" examples; if you've run across test-breaking things, we'd love your input |
| 15:04 |
shulabramble |
sleary++ sandbergja++ |
| 15:04 |
sleary |
we are also working on custom lint rules as described in that LP bug |
| 15:04 |
redavis |
sleary++ sandbergja++ |
| 15:04 |
terranm |
sleary++ sandbergja++ |
| 15:05 |
shulabramble |
y'all want to keep this as an action item still? provide updates every month on progress? |
| 15:05 |
sleary |
sure |
| 15:06 |
shulabramble |
#action sleary and sandbergja will report further progress on test writing wiki pages next month |
| 15:06 |
shulabramble |
#topic Bmagic will look into transferring POeditor account ownership to a generic EG account/moving this task to the nascent Infrastructure Committee |
| 15:06 |
sandbergja |
sounds good! |
| 15:06 |
jeff |
sleary++ sandbergja++ |
| 15:07 |
gmcharlt |
one note that the POEditor account is already under a generic evergreen-ils.org account |
| 15:07 |
shulabramble |
gmcharlt++ |
| 15:08 |
jeff |
anything more to share/point to on "nascent Infrastructure Committee"? |
| 15:08 |
gmcharlt |
I'll be calling a organizing meeting shortly |
| 15:09 |
jeff |
shulabramble++ gmcharlt++ |
| 15:09 |
sandbergja |
gmcharlt++ |
| 15:09 |
shulabramble |
gmcharlt++ again |
| 15:10 |
shulabramble |
#action gmcharlt will be calling an organizing meeting for the nascent Infrastructure Committee |
| 15:10 |
redavis |
gmcharlt++ |
| 15:10 |
shulabramble |
Now we get into Big Topic 1! |
| 15:10 |
shulabramble |
#topic Fall 2025 / 4.0 Release Team selection |
| 15:11 |
* redavis |
glances at eeevil |
| 15:11 |
shulabramble |
anyone jumping on board? |
| 15:11 |
redavis |
https://docs.google.com/spreadsheets/d/1aKffVGU_vIWbtFR_vpoHsqodSw-Kdd5yn65RpfkMKKA/edit?gid=0#gid=0 |
| 15:11 |
* gmcharlt |
also is putting my name forward |
| 15:11 |
redavis |
Here's the buildmaster spreadsheet. There are several already signed up. We need a manager, release notes person and translations people. |
| 15:12 |
* mmorgan |
can help with translations |
| 15:12 |
redavis |
Please add your name to the appropriate cell(s) on the spreadsheet. |
| 15:12 |
shulabramble |
redavis++ for the spreadsheet |
| 15:12 |
shulabramble |
mmorgan++ |
| 15:13 |
redavis |
np. I just linked it though :D. |
| 15:13 |
redavis |
gmcharlt, are you putting your name forth to manage the release? |
| 15:13 |
gmcharlt |
I am |
| 15:13 |
redavis |
Yes!! I see it. |
| 15:13 |
redavis |
Sorry, needed to horizontal scroll. |
| 15:13 |
jeff |
I'll release the notes. |
| 15:13 |
shulabramble |
gmcharlt++ |
| 15:13 |
shulabramble |
jeff++ |
| 15:14 |
jeff |
I suspect there will be a few. |
| 15:14 |
mmorgan |
gmcharlt++ |
| 15:14 |
redavis |
And thank you to those who just added yourselves for the July point releases as well. |
| 15:14 |
sandbergja |
gmcharlt++ |
| 15:14 |
sandbergja |
jeff++ |
| 15:14 |
shulabramble |
progress++ |
| 15:15 |
sandbergja |
mmorgan++ |
| 15:15 |
sandbergja |
berick++ |
| 15:15 |
redavis |
And that fill out the release teams for both 4.0 and July 3.15.3 and 3.14.8 |
| 15:15 |
sandbergja |
sleary++ |
| 15:15 |
sandbergja |
mdriscoll++ |
| 15:15 |
shulabramble |
berick++ sleary++ mdriscoll++ |
| 15:15 |
sandbergja |
redavis++ |
| 15:15 |
sandbergja |
abneiman++ |
| 15:15 |
sandbergja |
mantis++ |
| 15:15 |
redavis |
whew, go team! |
| 15:15 |
shulabramble |
what a productive action item! |
| 15:16 |
shulabramble |
team++ |
| 15:16 |
shulabramble |
mantis++ |
| 15:16 |
shulabramble |
abneiman++ |
| 15:16 |
shulabramble |
Moving right along... |
| 15:16 |
shulabramble |
#topic Updates |
| 15:16 |
shulabramble |
what news do we have? |
| 15:17 |
redavis |
3.14.7 and 3.15.2 were released on June 18 |
| 15:17 |
shulabramble |
#topic Evergreen |
| 15:17 |
shulabramble |
#info 3.14.7 and 3.15.2 were released on June 18 |
| 15:19 |
redavis |
Bugsquashing is also ongoing. |
| 15:19 |
redavis |
terranm++ |
| 15:19 |
terranm |
bugsquashers++ |
| 15:19 |
mmorgan |
terranm++ |
| 15:19 |
shulabramble |
#info Bugsquashing week in progress 7-7-2025 to 13-7-2025 |
| 15:19 |
shulabramble |
terranm++ |
| 15:19 |
abneiman |
terranm++ |
| 15:20 |
gmcharlt |
terranm++ |
| 15:20 |
sandbergja |
terranm++ |
| 15:20 |
collum |
terranm++ |
| 15:21 |
shulabramble |
any documentation updates to mention? |
| 15:22 |
abneiman |
based on github traffic, DIG was busy last week! DIG++ |
| 15:22 |
shulabramble |
dig++ |
| 15:22 |
terranm |
dig++ |
| 15:22 |
sandbergja |
dig++ |
| 15:23 |
shulabramble |
if there's nothing more from updates, then we'll move on. |
| 15:23 |
shulabramble |
to everyone's favorite moment -- the wall of text |
| 15:23 |
shulabramble |
#topic Launchpad Status (as of noon Eastern) |
| 15:23 |
shulabramble |
#topic Snapshot |
| 15:23 |
shulabramble |
#info Open Bugs - 3324 |
| 15:23 |
shulabramble |
#info Pullrequests - 115 |
| 15:23 |
shulabramble |
#info Signedoff - 31 |
| 15:23 |
shulabramble |
#info Needswork - 95 |
| 15:23 |
shulabramble |
#info Needstestplan - 3 |
| 15:23 |
shulabramble |
#info Needsrebase - 24 |
| 15:23 |
shulabramble |
#topic Updates Since Last Meeting |
| 15:23 |
shulabramble |
#info Bugs Added - 92 |
| 15:23 |
shulabramble |
#info Pullrequest tag Added - 60 |
| 15:23 |
shulabramble |
#info Signedoff tag Added - 26 |
| 15:24 |
shulabramble |
#info Needswork tag Added - 1 |
| 15:24 |
shulabramble |
#info Needstestplan tag Added - 0 |
| 15:24 |
shulabramble |
#info Needsrebase tag Added - 1 |
| 15:24 |
shulabramble |
#info Fix Committed - 17 |
| 15:24 |
shulabramble |
#topic New Business |
| 15:24 |
shulabramble |
#topic Can we start accepting code pull requests via github as an option? |
| 15:25 |
shulabramble |
#info DIG's github procedure - https://wiki.evergreen-ils.org/doku.php?id=evergreen-docs:github-workflow |
| 15:25 |
shulabramble |
#info Pros: reviewers and contributors can see some test and lint results before committing, a nice UI for reviewers to see what has changed |
| 15:25 |
shulabramble |
#info Cons: yet another workflow to learn and deal with, github is not a FOSS platform |
| 15:26 |
sandbergja |
This was from me! As a reviewer, I find it much easier to review contributions to projects in Github or Gitlab. There has been various talk in the community about whether moving EVERYTHING to github or gitlab might be desirable. I wanted to propose this as an incremental step to test the waters a bit more |
| 15:26 |
shulabramble |
Anyone have input on this? opinions? |
| 15:26 |
shulabramble |
sandbergja++ |
| 15:27 |
sandbergja |
I am sure the pros and cons lists are woefully short, apologies |
| 15:27 |
mmorgan |
ls |
| 15:28 |
mmorgan |
Oops. |
| 15:28 |
gmcharlt |
speaking as somebody assuming some additional specific responsiblity for patch review this cycle: |
| 15:28 |
gmcharlt |
1. I think most of the benefit would be in a whole-sale move to a new platform, but to me the ergonomics of the bug reporting likely matter more |
| 15:28 |
jeff |
sandbergja: how do you see the process working? would the idea being that the person reviewing would take responsibility for ensuring that launchpad was updated? would launchpad be involved at all? given a contribution with no associated launchpad bug (say, if someone submits a PR gia github without reference to / mention of a launchpad bug at all), would the commits be amended/rewritten to reference LP? |
| 15:29 |
gmcharlt |
2. I wouldn't ignore GitHub PRs per se, but I don't think we're ready to actively encourage it |
| 15:29 |
jeff |
(sorry, that's a bunch of questions, several of which probably don't require answers, depending on what the overall proposal is) |
| 15:30 |
abneiman |
I'm not against it per se, however, thinking about release notes and recordkeeping: LP is an imperfect (we all know git is canonical) but still reasonably complete accounting of what goes into each release. So I'd want to see a way to make sure we're not "losing" that info to github. |
| 15:30 |
gmcharlt |
3. I do think that most of the conventions in place should stay in place for now |
| 15:30 |
gmcharlt |
i.e., commit message stays the same, including the LP bug reference |
| 15:30 |
gmcharlt |
and patches are expected to apply cleanly with a focus on retaining a linear history |
| 15:30 |
shulabramble |
abneiman++ gmchart++ jeff++ |
| 15:31 |
shulabramble |
gmcharlt++, even |
| 15:31 |
gmcharlt |
i.e., I would not be inclined to do merge commits |
| 15:31 |
gmcharlt |
shulabramble: yeah, be careful with that gmchart dude - he's Edward Tufte's public enemy number one, even over barchart! ;) |
| 15:31 |
shulabramble |
will do XD |
| 15:32 |
abneiman |
that was a terrible joke gmcharlt. I cackled. |
| 15:32 |
sandbergja |
jeff: good questions. I definitely think we would need to make sure to keep the lp bug links, and would need to amend commits that did not refer to an lp. The DIG procedure does not currently involve pressing the Big Green Button in the github ui, but cherry-picking the relevant commits, so there is ample opportunity to check them while committing |
| 15:32 |
redavis |
gmcharlt, that was delightful. |
| 15:34 |
gmcharlt |
I think there may be an initial compromise formulation |
| 15:34 |
gmcharlt |
namely, for now, leaning into the review functionality in particular |
| 15:35 |
gmcharlt |
i.e., turning a normal pull request into a GH one specifically for the purpose of doing a Fisk-style review or running the tests |
| 15:35 |
gmcharlt |
as long as there are cross-references between GH and LP |
| 15:35 |
shulabramble |
question: is this something that might be best discussed in an email thread and revisited next month? |
| 15:35 |
gmcharlt |
and that sort of pull request could be done by anybody, not just the original submitter |
| 15:36 |
abneiman |
^^ ensuring cross refs to LP is my biggest concern |
| 15:36 |
gmcharlt |
@shulabramble most likely, I'd say |
| 15:36 |
pinesol |
gmcharlt: Have you tried throwing it across the room? |
| 15:36 |
jeff |
I'd participate in such an email thread. |
| 15:36 |
jeff |
pinesol: pay attention. server hurling was earlier. |
| 15:36 |
pinesol |
jeff: The horror... The horror... |
| 15:37 |
jeff |
(server flinging, rather) |
| 15:37 |
shulabramble |
might get some more community input as well. any volunteers to kick off the discussion on the developer list? |
| 15:37 |
jeff |
sandbergja: you game? |
| 15:37 |
jeff |
(or is there already a thread there and that's what led to this agenda item?) |
| 15:37 |
sandbergja |
sure! thanks for the discussion here, looking forward to more |
| 15:38 |
jeff |
sandbergja++ |
| 15:38 |
shulabramble |
#action sandbergja will start a discussion on the developer's listserv concerning moving to github/gitlab |
| 15:39 |
shulabramble |
sandbergja++ |
| 15:39 |
sleary |
sandbergja++ |
| 15:39 |
mmorgan |
sandbergja++ |
| 15:39 |
shulabramble |
#topic Updates on possible changes to where we have dev meetings |
| 15:40 |
shulabramble |
okay. so. until January 2026 we'll be meeting on IRC for sure. without going into too many details, I have no idea if I'm going to have a steady work location come January 2026. |
| 15:42 |
shulabramble |
so that's where we stand right now; IRC through 2025, 2026 might require a new person running these meetings depending on how the situation here shakes out. |
| 15:42 |
terranm |
Good luck, Shula! |
| 15:43 |
shulabramble |
terranm i have so many things i wish to say, but will not right now. |
| 15:43 |
terranm |
shulabramble++ |
| 15:43 |
abneiman |
shulabramble++ |
| 15:43 |
mmorgan |
shulabramble++ |
| 15:43 |
terranm |
FOIA-- |
| 15:43 |
shulabramble |
FOIA-- |
| 15:43 |
sleary |
shulabramble++ |
| 15:44 |
shulabramble |
to my credit, I haven't been reading any of the details of the news here and my therapist is very proud of me. |
| 15:44 |
shulabramble |
I just get the scuttlebutt through the grapevine. |
| 15:44 |
terranm |
Good! |
| 15:44 |
redavis |
shulabramble++ |
| 15:45 |
shulabramble |
anyway, that's all the news we have right now. i'll hold off on further stuff until the meeting is closed. |
| 15:45 |
shulabramble |
#topic Launchpad hygiene: targets for 4.0-beta even though it's not branched? add a new series for "4.next" to replace 3.next? |
| 15:45 |
abneiman |
this was me |
| 15:45 |
redavis |
seems like a great idea |
| 15:46 |
shulabramble |
abneiman++ yeah, that seems like a good idea. |
| 15:46 |
abneiman |
just a thought as I was spending a lot of time on targets recently (sleary++ for the 80 million pullrequests) |
| 15:46 |
redavis |
lol |
| 15:46 |
gmcharlt |
one thought: the 4.0-beta LP target can certain exist well before a branch does |
| 15:46 |
jeff |
any benefit to renaming the 3.next target to 4.next, or should those bugs not be automatically moved without individual attention/etc? |
| 15:46 |
abneiman |
I, and others, have been inconsitent about 4.0-beta targets. Realistically, it's just a tracking mechanism - as Galen notes, it's independent from the branch |
| 15:46 |
redavis |
gmcharlt++ |
| 15:47 |
gmcharlt |
and plain old "next" or "future" rather than "3.next" would work - but I think we should also consider simply not assigning a target for such bugs |
| 15:47 |
abneiman |
I'm more asking about what SHOULD be targeted to 4.0-beta, if there's a preference or a best practice |
| 15:47 |
gmcharlt |
ah - current practice is new features and enhancements would get beta targets |
| 15:47 |
* mmorgan |
would also like to hear best practices. |
| 15:47 |
gmcharlt |
normal bugs fixes that get merged would just get the relevant 3.x.y targets |
| 15:48 |
* redavis |
needs to move on to next things right now, but will catch up on the minutes/log. |
| 15:48 |
shulabramble |
redavis++ |
| 15:48 |
|
Lorne joined #evergreen |
| 15:48 |
shulabramble |
gmcharlt++ |
| 15:48 |
abneiman |
yeah that's what I thought, but it seems that a few of us (self included) were not following that. I will correct mine own behaviour and shake a stick at the rest of you, lol |
| 15:48 |
abneiman |
gmcharlt++ |
| 15:48 |
gmcharlt |
generally, pure bugfixes that end up in 4.0-beta would be _just_ things that affect the main branch only |
| 15:49 |
gmcharlt |
e.g., cleanup of a new feature that was previously committed for inclusion in 4.0-beta |
| 15:49 |
abneiman |
ah |
| 15:49 |
abneiman |
what about something like this? https://bugs.launchpad.net/evergreen/+bug/2115535 |
| 15:49 |
pinesol |
Launchpad bug 2115535 in Evergreen 3.15 "OPAC basket dropdown should be a nav landmark" [Low,Fix committed] |
| 15:50 |
abneiman |
should that have a 4.0 target or not, since it's just going into main as a "general bugfix" at this point? |
| 15:50 |
gmcharlt |
and to articulate an organizing principle that I think has been only tacit until now: the idea (or at least, my idea) is that a bug target represents the _first_ time that it shows up in any release |
| 15:50 |
gmcharlt |
abneiman: for that example, it should not have a 4.0-beta target |
| 15:50 |
abneiman |
ok, thanks |
| 15:50 |
abneiman |
that clarifies it for me |
| 15:50 |
abneiman |
and I'll go cleanup my LP detritus :) |
| 15:51 |
gmcharlt |
abneiman: what's that band's genre? ;) |
| 15:51 |
terranm |
Punk for sure |
| 15:51 |
sleary |
that does clarify it, but leaves us without an efficient way to indicate the destination of the fix rather than just the origin of the bug |
| 15:51 |
sleary |
if that makes sense |
| 15:51 |
csharp_ |
@band add abneiman's LP detritus |
| 15:51 |
pinesol |
csharp_: Band 'abneiman's LP detritus' added to list |
| 15:51 |
abneiman |
lol |
| 15:51 |
abneiman |
and, sleary's point is well taken |
| 15:52 |
shulabramble |
abneiman++ sleary++ csharp++ |
| 15:52 |
jeffdavis |
Is there a list of requirements for 4.0? Like "a 4.0 release should contain the following features"? Or has it just already been decided that 4.0 is the next one? |
| 15:52 |
shulabramble |
csharp_++ |
| 15:53 |
shulabramble |
jeffdavis++ |
| 15:53 |
abneiman |
jeffdavis: I think the original intent was to have full angular circ for 4.0, however I do not think that is realistic at this point |
| 15:53 |
abneiman |
so the answer to your question would be "the latter" |
| 15:53 |
gmcharlt |
sleary: I think the current practice basically assumes that the LP milestone target is purely about the destination of the fix. There isn't an equivalent to (e.g.) Koha's Bugzilla that has fields to indicate all release streams where the bug is/was present |
| 15:53 |
gmcharlt |
(if I'm understanding your point correctly) |
| 15:54 |
sleary |
gmcharlt you are. thanks. |
| 15:54 |
shulabramble |
we're running up on the hour, so do we wanna action item this for further discussion? |
| 15:54 |
shulabramble |
and we still have one more piece of business |
| 15:55 |
terranm |
I remember angular circ being the original target for 4.0 as well. |
| 15:55 |
jeffdavis |
I can email the dev list about "what even is a 4.0" if we want to continue that discussion elsewhere |
| 15:55 |
gmcharlt |
likewise, but regardless, we'll nonetheless make 4.0 a release to remember :) |
| 15:55 |
shulabramble |
jeffdavis++ |
| 15:56 |
gmcharlt |
(nothing that I say this as somebody who has a very strong preference for keeping debates about version numbering as short as possible) |
| 15:56 |
shulabramble |
#action jeffdavis will email the dev list about launchpad hygiene for 4.0-beta etc |
| 15:56 |
shulabramble |
#topic Feedback requested: QA checklist for grids (with potential automated tests highlighted) - https://docs.google.com/document/d/1RDNU4d78wX9wfQjdFsY2PHjLQwjTXbSXLqZdHXrjBNk/edit?usp=sharing |
| 15:57 |
sleary |
ah, this is me. Based on gmcharlt's excellent checklist for database tables and columns, here is one for grids! |
| 15:57 |
sandbergja |
sleary++ |
| 15:57 |
sleary |
sandbergja and I have noted which ones seem like candidates for automated testing |
| 15:58 |
jeff |
"This checklist. I like it. ANOTHER!" |
| 15:58 |
jeff |
sleary++ |
| 15:58 |
sleary |
feel free to comment on the checklist and/or assign yourself to experiment with writing a test |
| 15:58 |
sleary |
I will migrate this to the wiki eventually |
| 15:58 |
shulabramble |
sleary++ |
| 15:59 |
terranm |
sleary++ |
| 15:59 |
shulabramble |
#info feel free to comment on the checklist and/or assign yourself to experiment with writing a test - https://docs.google.com/document/d/1RDNU4d78wX9wfQjdFsY2PHjLQwjTXbSXLqZdHXrjBNk/edit?usp=sharing |
| 15:59 |
shulabramble |
#topic Announcements |
| 15:59 |
shulabramble |
#topic Next Meeting is 12 August 2025 |
| 16:00 |
shulabramble |
We got anything more? |
| 16:00 |
shulabramble |
in that case, solidly on the hour - |
| 16:00 |
shulabramble |
#endmeeting |
| 16:00 |
pinesol |
Meeting ended Tue Jul 8 16:00:51 2025 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:00 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2025/evergreen.2025-07-08-15.00.html |
| 16:00 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2025/evergreen.2025-07-08-15.00.txt |
| 16:00 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2025/evergreen.2025-07-08-15.00.log.html |
| 16:00 |
gmcharlt |
shulabramble++ |
| 16:01 |
collum |
shulabramble++ |
| 16:01 |
sleary |
shulabramble++ |
| 16:01 |
jeff |
ding! |
| 16:01 |
jeff |
shulabramble++ |
| 16:01 |
csharp_ |
shulabramble++ |
| 16:01 |
shulabramble |
Okay so now that we're out of the meeting -- if anyone has a lead on any remote work please let me know because my workplace is extremely normal and okay. |
| 16:01 |
abneiman |
shulabramble++ |
| 16:02 |
shulabramble |
i'll probably still have a job in January, but I'm not putting all my eggs in that basket necessarily |
| 16:02 |
terranm |
:( |
| 16:02 |
sleary |
shulabramble >.< Sorry to hear |
| 16:03 |
mmorgan |
:-( |
| 16:05 |
Lorne |
shulabramble I thought I'd seen an ad or two on LinkedIn. let me dig them up |
| 16:05 |
shulabramble |
lorne++ |
| 16:10 |
shulabramble |
thanks for the support, y'all. (sorry about the delay, I was posting up the agenda for next month) |
| 16:13 |
Lorne |
shulabramble Hybrid role at CUNY: https://cuny.jobs/new-york-ny/university-director-of-collections-and-metadata-strategy/228006FE9D6D494489EA03F6DA402F7F/job/ |
| 16:14 |
shulabramble |
lorne++ |
| 16:16 |
Lorne |
here's the other hybrid one: https://www.linkedin.com/jobs/view/4263605879/?refId=acLduYkDSd27HF7UGGa2uQ%3D%3D&trackingId=acLduYkDSd27HF7UGGa2uQ%3D%3D |
| 16:16 |
Lorne |
I know remote roles have popped up, can't find them just now |
| 16:17 |
shulabramble |
Thank you so much! |
| 16:17 |
Lorne |
NP, just a laid-off guy who started his own business after seeing how normal and okay the job market is lol |
| 16:19 |
Lorne |
I was not in the library space until very recently |
| 16:47 |
|
dguarrac_ joined #evergreen |
| 16:55 |
|
mantis left #evergreen |
| 17:03 |
|
Lorne joined #evergreen |
| 17:18 |
|
mmorgan left #evergreen |
