| Time |
Nick |
Message |
| 04:13 |
|
dluch joined #evergreen |
| 04:13 |
|
Bmagic joined #evergreen |
| 04:13 |
|
scottangel joined #evergreen |
| 04:32 |
|
dluch joined #evergreen |
| 04:32 |
|
Bmagic joined #evergreen |
| 04:50 |
|
dluch joined #evergreen |
| 04:54 |
|
scottangel joined #evergreen |
| 04:54 |
|
Bmagic joined #evergreen |
| 07:15 |
|
kworstell-isl joined #evergreen |
| 07:34 |
|
redavis joined #evergreen |
| 07:37 |
|
collum joined #evergreen |
| 07:54 |
|
mantis joined #evergreen |
| 08:00 |
|
BDorsey joined #evergreen |
| 08:26 |
|
mmorgan joined #evergreen |
| 08:29 |
|
Dyrcona joined #evergreen |
| 08:53 |
|
dguarrac joined #evergreen |
| 09:24 |
|
kmlussier joined #evergreen |
| 09:59 |
|
Stompro joined #evergreen |
| 10:35 |
|
kworstell-isl joined #evergreen |
| 11:42 |
|
jvwoolf joined #evergreen |
| 12:20 |
mantis |
would anyone have an idea as to which files to look at with a window resizing issue? We noticed this in our version of the Record In-House Use page - the form disappears when the window is sized to small or if the monitor isn't large enough. |
| 13:18 |
|
sandbergja joined #evergreen |
| 13:24 |
sandbergja |
mantis: for the window resizing issue, I would definitely take a look at src/templates/staff/css/style.css.tt2 and src/templates/staff/circ/in_house_use/index.tt2. It would be good to determine if the form is totally removed from the DOM at small sizes, or if it's there but hidden (for example with CSS display:none), or if another DOM element is |
| 13:24 |
sandbergja |
just totally covering it up. I would investigate in the browser dev tools to see if it's there, and if so, if it's hidden or covered up. |
| 13:25 |
Dyrcona |
I was about suggest Open-ILS/src/eg2/src/app/staff/nav.component.html (depending on your release) and that it does sound like a CSS style issue. |
| 13:34 |
Stompro |
dluch, did you see bug #1533424 in regards to your question about circulation duration rules? No solution, but some discussion. |
| 13:34 |
pinesol |
Launchpad bug 1533424 in Evergreen "Wishlist: Ability to create circulation policies to make items due at closing" [Wishlist,New] https://launchpad.net/bugs/1533424 |
| 14:18 |
|
terranm joined #evergreen |
| 14:32 |
|
terranm joined #evergreen |
| 14:39 |
|
shulabear joined #evergreen |
| 14:44 |
|
terranm55 joined #evergreen |
| 14:48 |
|
terranm69 joined #evergreen |
| 14:48 |
|
mdriscoll joined #evergreen |
| 14:54 |
|
sleary joined #evergreen |
| 14:55 |
|
terranm joined #evergreen |
| 14:55 |
|
terranm48 joined #evergreen |
| 14:56 |
|
terranm57 joined #evergreen |
| 14:56 |
terranm57 |
Sorry if everyone is seeing me join and disconnect a million times, trying to get my router to work. |
| 14:57 |
mmorgan |
terranm: I was thinking you might be trying to clone yourself to get more work done ;-) |
| 14:57 |
terranm57 |
If only! |
| 14:58 |
terranm57 |
Maybe then I'd be able to catch up on help desk tickets |
| 14:58 |
mmorgan |
If you figure it out, let me know!! |
| 14:59 |
csharp_ |
the 57th clone! |
| 14:59 |
|
collum joined #evergreen |
| 15:00 |
terranm57 |
And we know the quality degrades with every copy. |
| 15:00 |
csharp_ |
or mutates! |
| 15:00 |
abneiman |
@band add The 57 Terrans |
| 15:00 |
pinesol |
abneiman: Band 'The 57 Terrans' added to list |
| 15:00 |
terranm57 |
lol |
| 15:01 |
terranm57 |
I could use an extra arm |
| 15:02 |
shulabear |
The shortlived "Terran 48" was an experimental mid-60s scifi novel. |
| 15:02 |
|
gmcharlton joined #evergreen |
| 15:03 |
csharp_ |
shulabear++ |
| 15:03 |
terranm57 |
heh |
| 15:04 |
csharp_ |
@who showed up expecting a dev meeting? |
| 15:04 |
pinesol |
dbs showed up expecting a dev meeting. |
| 15:04 |
abneiman |
yeah I was just gonna ask |
| 15:04 |
* gmcharlton |
waves |
| 15:04 |
* Stompro |
also... furiously checking lists for announcements I missed. |
| 15:04 |
berick |
let's just add more band names |
| 15:05 |
abneiman |
who's this gmcharlton guy, we only know gmcharlt |
| 15:05 |
gmcharlton |
doppelganger, of course |
| 15:05 |
terranm57 |
All my clones are helping me get to my ultimate goal: https://www.amazon.com/Rise-Terran-Empire-Technic-Civilization/dp/1439134243 |
| 15:05 |
Bmagic |
oh! dev meeting! |
| 15:05 |
Bmagic |
sorry yall, let's go ahead, just a second |
| 15:05 |
abneiman |
Terran & The Clones ... Galen & The Doppelgangers ... double billing, Mardi Gras only! |
| 15:05 |
csharp_ |
@ana bespoke dev meeting |
| 15:05 |
pinesol |
csharp_: Peeved gem bikes not |
| 15:06 |
abneiman |
that's deep, pinesol |
| 15:06 |
csharp_ |
pinesol: wat |
| 15:06 |
pinesol |
csharp_: SysTEmContROL ReeStarTT Opan |
| 15:06 |
Bmagic |
#startmeeting 2024-02-13 - Developer Meeting |
| 15:06 |
pinesol |
Meeting started Tue Feb 13 15:06:29 2024 US/Eastern. The chair is Bmagic. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:06 |
pinesol |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:06 |
pinesol |
The meeting name has been set to '2024_02_13___developer_meeting' |
| 15:06 |
Bmagic |
#info Agenda at https://wiki.evergreen-ils.org/doku.php?id=dev:meetings:2024-02-13 |
| 15:07 |
Bmagic |
#topic Introductions |
| 15:07 |
Bmagic |
#info Bmagic = Blake GH, MOBIUS |
| 15:07 |
Stompro |
#info Stompro = Josh Stompro, LARL |
| 15:07 |
gmcharlton |
#info gmcharlton = Galen Charlton, Equinox |
| 15:07 |
terranm57 |
#info terranm57 = Terran McCanna, PINES |
| 15:07 |
shulabear |
#info shulabear = Shula Link, GCHRL |
| 15:07 |
collum |
#info collum = Garry Collum, KCPL |
| 15:07 |
csharp_ |
#info csharp_ = the actual and only Chris Sharp |
| 15:07 |
dluch |
#info dluch = Debbie Luchenbill, MOBIUS |
| 15:07 |
mmorgan |
#info mmorgan = Michele Morgan, NOBLE |
| 15:07 |
abneiman |
#info abneiman = Andrea Buntz Neiman, Equinox |
| 15:07 |
berick |
#info berick Bill Erickson, KCLS |
| 15:08 |
Bmagic |
#topic Action Items from Last Meeting |
| 15:08 |
Bmagic |
#info mmorgan will explore moving LP stats to community site and automating same |
| 15:08 |
* mmorgan |
has been poking at Dyrcona's launchpad api scripts and was able to retrieve bug counts, so a bit of progress. |
| 15:08 |
Bmagic |
mmorgan++ |
| 15:08 |
mmorgan |
That's all I have for now. |
| 15:08 |
Bmagic |
carry it forward? |
| 15:08 |
mmorgan |
Yep! |
| 15:08 |
Bmagic |
#action mmorgan will explore moving LP stats to community site and automating same |
| 15:09 |
Bmagic |
#info sandbergja will see if gh actions can run the pgtap tests |
| 15:09 |
Bmagic |
skipping |
| 15:09 |
Dyrcona |
#info Dyrcona = Jason Stephenson, CW MARS |
| 15:09 |
Bmagic |
#info GalenCharlton will open LP bug with the official proposal for git commit message release-note |
| 15:09 |
Bmagic |
#action sandbergja will see if gh actions can run the pgtap tests |
| 15:10 |
gmcharlton |
So, the bug is opened: https://bugs.launchpad.net/evergreen/+bug/2051946 |
| 15:10 |
pinesol |
Launchpad bug 2051946 in Evergreen "institute a Git commit message template" [Wishlist,New] - Assigned to Galen Charlton (gmc) |
| 15:10 |
gmcharlton |
ah, sorry, wrong one |
| 15:10 |
gmcharlton |
just a moment |
| 15:10 |
gmcharlton |
this is the one: https://bugs.launchpad.net/evergreen/+bug/2051874 |
| 15:10 |
pinesol |
Launchpad bug 2051874 in Evergreen "new script to extract information for release notes from commit messages" [Wishlist,New] |
| 15:11 |
gmcharlton |
and it comes with a pull request |
| 15:11 |
gmcharlton |
so, additional feedback welcome |
| 15:12 |
Bmagic |
gmcharlton++ |
| 15:12 |
shulabear |
gmcharlton++ |
| 15:12 |
Dyrcona |
gmcharlt++ |
| 15:12 |
Dyrcona |
I should be able to take a look. |
| 15:13 |
gmcharlton |
Dyrcona++ |
| 15:13 |
Bmagic |
:) |
| 15:13 |
Bmagic |
this next one is yours also |
| 15:13 |
Bmagic |
#info GalenCharlton update the release note script to look for the release-note tags |
| 15:14 |
Bmagic |
I thought maybe that was more along the lines of: update the release script to include the release note portion |
| 15:15 |
gmcharlton |
yeah - I think the action items got a bit squished during the previous meeting |
| 15:15 |
Bmagic |
but I suppose you killed both birds with one LP? |
| 15:15 |
gmcharlton |
the first bug I mentioned, bug 2051946, is the one to instituate a commit message template |
| 15:15 |
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:15 |
gmcharlton |
that bug is open, but now I need to devise a template and create a pull request |
| 15:16 |
Bmagic |
ok, shall we make that an action for you? |
| 15:16 |
gmcharlton |
so I'll take an action item to create a Git commit message type and update bug 2051946 |
| 15:16 |
gmcharlton |
yes please |
| 15:16 |
Bmagic |
#action gmcharlton - create a Git commit message type and update bug 2051946 |
| 15:16 |
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:17 |
Bmagic |
#link https://wiki.evergreen-ils.org/doku.php?id=dev:git#commit_messages |
| 15:18 |
Bmagic |
I suppose Stompro did his thing? |
| 15:18 |
Stompro |
I added examples to the dev:git page and updated a few other pages that referenced creating the release notes with stubs just so the new ability gets noticed. |
| 15:18 |
gmcharlton |
he did |
| 15:18 |
gmcharlton |
Stompro++ |
| 15:18 |
Bmagic |
Stompro++ |
| 15:18 |
gmcharlton |
also, on the general topic, there's a comment from abneiman on the release-tag bug that I'd like to mention now, as it might affect the template |
| 15:19 |
gmcharlton |
namely, seeing if we can setting for a tense to use for the one-liner release notes |
| 15:19 |
Bmagic |
please, the rest of the agenda is almost empty, so go ahead |
| 15:20 |
gmcharlton |
abneiman: do you have any preference one way or another? |
| 15:20 |
Bmagic |
hmmm |
| 15:20 |
gmcharlton |
(comment is https://bugs.launchpad.net/evergreen/+bug/2051874/comments/9) |
| 15:20 |
pinesol |
Launchpad bug 2051874 in Evergreen "new script to extract information for release notes from commit messages" [Wishlist,New] - Assigned to Jason Stephenson (jstephenson) |
| 15:20 |
abneiman |
sorry, I was just here for the band names |
| 15:21 |
Bmagic |
I like the "s" - inferring that the following code does* the thing. Though from a documentation context, I'd say without the s, but maybe a "d" instead. Like "Removed" X, "Fixed" Y |
| 15:21 |
abneiman |
personally I tend to go with the more active (to my ears) version: "Fixes an issue..." "Restores the ability..." "Adds a something or another" |
| 15:21 |
kmlussier |
+1 |
| 15:21 |
gmcharlton |
abneiman: be it. "Megadeth fixes the accessibility issue." "Chanticleer updates the MARC tag tables" |
| 15:22 |
gmcharlton |
etc. |
| 15:22 |
abneiman |
but, I don't really have a strong preference, just a preference for consistency (hobgoblins or not) |
| 15:22 |
abneiman |
gmcharlton++ # actual lol |
| 15:22 |
Bmagic |
s! Esss it issss! |
| 15:23 |
Dyrcona |
We could go with just "Fix an issue...." |
| 15:23 |
shulabear |
all release notes should be in passive voice /jk |
| 15:24 |
Bmagic |
lol, Dyrcona |
| 15:24 |
dluch |
Yeah, I think with the s |
| 15:24 |
dluch |
shulabear lol |
| 15:24 |
Bmagic |
so, where does this lead us? Should this be formal somewhere? |
| 15:24 |
gmcharlton |
suggestion in the Git commit message template (and the wiki page) would be where to put it, I think |
| 15:25 |
Bmagic |
Stompro? want that one? |
| 15:25 |
Stompro |
Sure |
| 15:25 |
Bmagic |
#action Stompro will formalize the tense usage in the release-note message |
| 15:26 |
Bmagic |
I would like to open the floor for any topic that anyone would like to mention? I dropped the ball and forgot to email the list yesterday, attempting to get the agenda a bit more filled out |
| 15:26 |
Dyrcona |
While we're at it can we get better commit messages in general? Some folks don't follow guidelines. |
| 15:27 |
Bmagic |
it'd be neat if git would flat refuse to commit if it's not in our format :) |
| 15:27 |
terranm57 |
Bmagic I added one to New Business |
| 15:27 |
gmcharlton |
yeah, I think that's going to be a matter of nudging |
| 15:27 |
kmlussier |
Bmagic: That's what core committers are for. |
| 15:27 |
Bmagic |
terranm57++ |
| 15:27 |
gmcharlton |
(though as I'm sure many of you have observed, I'm also quite willing to edit commit messages) |
| 15:28 |
Bmagic |
kmlussier++ # I'm picking up your sublty |
| 15:28 |
Bmagic |
moving on! |
| 15:28 |
Bmagic |
#topic Launchpad Status (as of noon Eastern) |
| 15:28 |
Bmagic |
incoming!!! |
| 15:29 |
Bmagic |
lol, gmcharlt took incoming seriously |
| 15:29 |
Bmagic |
#info Open Bugs - 3091 |
| 15:29 |
Bmagic |
#info Pullrequests - 107 |
| 15:29 |
Bmagic |
#info Signedoff - 8 |
| 15:29 |
Bmagic |
#topic Launchpad Status since last meeting |
| 15:29 |
Bmagic |
#info Bugs Added - 62 |
| 15:29 |
Bmagic |
#info Pullrequest tag Added - 39 |
| 15:29 |
Bmagic |
#info Signedoff tag Added - 13 |
| 15:29 |
Bmagic |
#info Fix Committed - 23 |
| 15:29 |
Bmagic |
#topic New Business - New Launchpad tag: "caching" |
| 15:30 |
Bmagic |
who has "caching" ? |
| 15:30 |
terranm57 |
lol |
| 15:31 |
terranm57 |
Caching might have been gmcharlton's since I saw some tickets get added |
| 15:31 |
Bmagic |
oh shoot, he disconnected |
| 15:31 |
Bmagic |
gotta wait for the ol' cable modem to power cycle |
| 15:31 |
|
gmcharlton joined #evergreen |
| 15:31 |
Bmagic |
poof, he's back |
| 15:32 |
gmcharlton |
so, did y'all fix all the bugs while I was gone? |
| 15:32 |
terranm57 |
We just assigned them all to you |
| 15:32 |
Bmagic |
gmcharlton: we're here: "New Launchpad tag: "caching"" |
| 15:32 |
gmcharlton |
terranm57: fair |
| 15:32 |
gmcharlton |
so regarding the caching tag, just a heads-up that I added it today |
| 15:33 |
terranm57 |
gmcharlton, did you add it to the "official list" too? |
| 15:33 |
gmcharlton |
intended as a catch-all for issues where caching is just too. dang. much. |
| 15:33 |
Bmagic |
gmcharlton++ # moving and shaking! |
| 15:33 |
gmcharlton |
I did also making it an official tag |
| 15:33 |
terranm57 |
I'll add it here - https://wiki.evergreen-ils.org/doku.php?id=dev:lp_tags |
| 15:33 |
gmcharlton |
but of course, now's the time to revert that if somebody has a serious objection or wishes an alternative name |
| 15:34 |
Bmagic |
when do we tag bugs with it? |
| 15:35 |
gmcharlton |
Bmagic: basically, any bug where a value gets cached, then changed, but then there's no obvious way to refresh the caching without server-side action such as an Apache restart |
| 15:35 |
terranm57 |
"caching" works for me |
| 15:35 |
gmcharlton |
it would cover both settings and configuration data as well as things like cached images and files served from the webserver (including Javascript) |
| 15:35 |
Bmagic |
ok, makes sense. Documenting that on the wiki would be good. terranm is getting that covered |
| 15:35 |
Dyrcona |
Yeah, "caching" is OK. If we need another for browser cache, we can add that. |
| 15:36 |
Bmagic |
#action terranm will make LP tag "caching" official |
| 15:36 |
terranm57 |
If we want to break it up, please do so like caching-server, caching-browser, etc. |
| 15:36 |
terranm57 |
Bmagic - done! |
| 15:37 |
Bmagic |
terranm57: and confirmed! I see it. Wow, that has to be some kind of record |
| 15:37 |
gmcharlton |
my overall goal: without compromising speed, to make it possible to change something or do an upgrade and see the new stuff without anything more than a page refresh |
| 15:37 |
gmcharlton |
(or at least, a cache-clearing action that you can get at via the staff client) |
| 15:37 |
Dyrcona |
Well, why not drop the "ing?" Particularly if there are two: browser-cache, server-cache? |
| 15:37 |
|
mantis left #evergreen |
| 15:38 |
Bmagic |
CTR+f the tags wiki page for "cach" - no results but the new one |
| 15:38 |
* Bmagic |
waves at mantis, ongoing dev meeting atm |
| 15:39 |
Dyrcona |
I'm not sure we'd need a tag for browser cache, though. So, don't mind me. |
| 15:39 |
Bmagic |
we're good then, with the "caching" tag? I mean, it's already official |
| 15:40 |
gmcharlton |
I think for the moment that there's no need to split the tag |
| 15:40 |
Bmagic |
sounds good to me |
| 15:40 |
Bmagic |
#topic New Business - 3.next / 4.0 release team & schedule? |
| 15:40 |
abneiman |
that's mine |
| 15:40 |
Bmagic |
strap in, this might be a long one |
| 15:40 |
abneiman |
just a poke |
| 15:40 |
abneiman |
I mean, I don't have anything to say other than, hey we should talk or at least think about this? |
| 15:41 |
abneiman |
anyone want to take the lead? |
| 15:41 |
abneiman |
for that matter, are we settled on whether this will be 3.13 or 4.0? |
| 15:41 |
abneiman |
anyway, discuss! |
| 15:41 |
Dyrcona |
I have been meaning to start a larger conversation about releases because I don't think our current model is working. |
| 15:42 |
abneiman |
agreed that that is a larger convo that needs to be had; but for this month I just don't want another month to go by without a relteam for the spring |
| 15:43 |
Bmagic |
#link https://wiki.evergreen-ils.org/doku.php?id=dev:evergreen:release_checklist |
| 15:43 |
Dyrcona |
Well, our last release was three months late. Do we think we're really ready for another? |
| 15:44 |
Bmagic |
Dyrcona: point release? |
| 15:44 |
abneiman |
part of that was we didn't get a rel team together till three months late... and we're already running late on the spring, so, is the answer to run later? or to get people to step up now and try to get a schedule together? |
| 15:45 |
csharp_ |
is anyone experimenting with RediSRF? that seems to be one of the factors for 3.X vs 4.0 |
| 15:45 |
Bmagic |
csharp_: I am! nothing to report yet though |
| 15:45 |
gmcharlton |
csharp_: yep |
| 15:45 |
Bmagic |
I'm planning on putting it into production for a 3.12.1 upgrade |
| 15:45 |
csharp_ |
we should also consider an LTS (long term support) 3.X for people not ready to move to RediSRF/Rust |
| 15:46 |
Dyrcona |
That schedule is unrealistic given our current experience. I think we should do 1 release per year, if we wish to do the full tarball dance. |
| 15:46 |
terranm57 |
From a user perspective, I would expect a 4.0 version to be fully Angularized. |
| 15:46 |
berick |
Bmagic: nice! |
| 15:46 |
shulabear |
terranm57++ |
| 15:46 |
sleary |
another factor is that we have some Angularizations coming up (Reports, Acq A&B) that would let us remove some older interfaces, but we might want a version where they overlap... what terranm57 said |
| 15:46 |
dluch |
terranm57: same |
| 15:46 |
csharp_ |
at the Hackaway we talked about changing up the release timings iirc |
| 15:47 |
Dyrcona |
abneiman: To answer your specific question: Yes, I think we should push the spring release back depending. |
| 15:47 |
Bmagic |
sounds like we don't want 4.0 to be the next* release name |
| 15:47 |
csharp_ |
I don't think it fits |
| 15:47 |
sleary |
I agree |
| 15:47 |
abneiman |
Equinox has a couple large features -- alluded to by sleary -- that IMO should predate a 4.0/redis |
| 15:47 |
sleary |
I would love for 4.0 to have some visual polish, and the UI group is working on some things, but they will not all be ready for spring |
| 15:47 |
Dyrcona |
Someone has started targeting bugs at 4.0-beta, fwiw. |
| 15:47 |
Bmagic |
3.13 rolls off the togue anyway! |
| 15:47 |
abneiman |
I'd love to see a spring release but we need volunteers |
| 15:48 |
csharp_ |
and we have to do 3.13 so we can get to Evergreen Pi! |
| 15:48 |
Dyrcona |
I also think we should follow the trend of using YY.MM for releases. Many more projects are doing that now. |
| 15:49 |
Bmagic |
I'm not opposed to changing the numbering system, but we might want to take that to the mailing list? |
| 15:49 |
Dyrcona |
As for the next release, do we think there are enough new feature ready now to justify another "major" release? |
| 15:49 |
csharp_ |
we based the twice a year thing on Ubuntu, and we're actually a bit more like Fedora (late all the time) |
| 15:49 |
sleary |
I do not love the year/month numbering, just because last-minute release schedule changes would force us to edit a lot of docs and things |
| 15:50 |
abneiman |
there will be a whole pile of potential major features shortly, once I know what a release schedule looks like .... |
| 15:50 |
gmcharlton |
noting that the 4.0 series / 4.0-beta tags in LP are easily renamed |
| 15:50 |
Dyrcona |
Bmagic: Right, I was gong to add that changing the numbering and reducing the number of releases should be part of that larger conversation. However, I think it is worth mentioning as we discuss the next release. |
| 15:50 |
Bmagic |
actually that is a good point, don't we have a bunch of code that relies on the numbers to be in sequence like that? |
| 15:50 |
csharp_ |
gmcharlton right - and *all* of this is kinda arbitrary in the end :-) |
| 15:51 |
gmcharlton |
next release, Evergreen ξ! |
| 15:51 |
Dyrcona |
What csharp_ just said is why I prefer dated releases. The numbers are arbitrary. |
| 15:51 |
csharp_ |
PINES does annual upgrades and we'll do whatever version is newest at that time |
| 15:51 |
Dyrcona |
gmcharlton: You're proposing we got the rote of TeX and increment 1 digit of Pi for earch new release? |
| 15:51 |
Dyrcona |
:) |
| 15:51 |
abneiman |
so, no release team volunteers? We're just gonna talk about numbers? |
| 15:52 |
berick |
annual here too fwiw, but it seems we're veering into a huge tangent :) |
| 15:52 |
Bmagic |
Dyrcona: would you like to take the action of leading the numbering discussion on the mailing list? |
| 15:52 |
berick |
abneiman++ |
| 15:52 |
Bmagic |
I'll be on the team! |
| 15:52 |
shulabear |
I'll volunteer again. I'm not extremely useful, but I'm a body! |
| 15:52 |
abneiman |
Bmagic++ |
| 15:52 |
terranm57 |
Bmagic++ |
| 15:52 |
Dyrcona |
abneiman: I am not convinced that we're ready for another release. Why not open the Lp bugs with the new features, firt? |
| 15:52 |
Dyrcona |
first... |
| 15:52 |
Bmagic |
shulabear++ |
| 15:52 |
csharp_ |
Bmagic++ shulabear++ |
| 15:52 |
Dyrcona |
Bmagic: No, I'm not taking an action. |
| 15:53 |
Bmagic |
:) |
| 15:53 |
berick |
Dyrcona: seems like something the release team could discuss? |
| 15:53 |
terranm57 |
Why not choose the release team and let them take a closer look at when there is enough new good stuff? |
| 15:53 |
abneiman |
Dyrcona: standby and I will give you a list of bugs in LP |
| 15:53 |
csharp_ |
makes sense to me, berick & terranm57 |
| 15:53 |
Bmagic |
shulabear: it's you and me! We got this. |
| 15:54 |
shulabear |
bmagic: oh lord we're in trouble |
| 15:54 |
Bmagic |
(You're telling me :)) |
| 15:54 |
Dyrcona |
We can put it to a vote if you like. I'm just not prepared to volunteer at the moment |
| 15:54 |
berick |
it's been a while, but I can assist w/ the release team this time. just tell me what to do |
| 15:55 |
Bmagic |
berick++ # glad to have you along |
| 15:55 |
terranm57 |
Bmagic I can't commit to being on the release team again this time, but I can help with organizing feedback fest for it |
| 15:55 |
csharp_ |
berick++ |
| 15:55 |
csharp_ |
we all have your back |
| 15:55 |
abneiman |
https://bugs.launchpad.net/evergreen/+bug/1993823 |
| 15:55 |
abneiman |
https://bugs.launchpad.net/evergreen/+bug/2006970 |
| 15:55 |
abneiman |
https://bugs.launchpad.net/evergreen/+bug/2039609 |
| 15:55 |
abneiman |
https://bugs.launchpad.net/evergreen/+bug/2006969 |
| 15:55 |
pinesol |
Launchpad bug 1993823 in Evergreen "wishlist: Angular Reports Interface" [Wishlist,Confirmed] - Assigned to Andrea Neiman (aneiman) |
| 15:55 |
pinesol |
Launchpad bug 2006970 in Evergreen "wishlist: Acquisitions Sprint B: Angular Invoicing and Claiming" [Wishlist,New] - Assigned to Jason Etheridge (phasefx) |
| 15:55 |
Bmagic |
terranm++ # I love this stone soup we're making |
| 15:55 |
pinesol |
Launchpad bug 2039609 in Evergreen "wishlist: Acquisitions Sprint A - Z39.50 and other fixes" [Wishlist,New] - Assigned to Mike Rylander (mrylander) |
| 15:55 |
pinesol |
Launchpad bug 2006969 in Evergreen "wishlist: enhanced MARC editor rewrite" [Wishlist,Confirmed] - Assigned to Stephanie Leary (stephanieleary) |
| 15:55 |
csharp_ |
but I'm unable to take on new things right now |
| 15:55 |
csharp_ |
holy craznap |
| 15:56 |
abneiman |
noting that those 4 that I linked are in the final stages of internal cleanup and I expect PRs on all of them within the month |
| 15:56 |
sleary |
those are just the big ones :) |
| 15:56 |
abneiman |
so, yes, there are features |
| 15:56 |
terranm57 |
nice! |
| 15:56 |
Bmagic |
lol, that's all? |
| 15:56 |
gmcharlton |
berick: Bmagic: shulabear: if it helps, I am willing to do a one-shot session to go over some of the details; and I'm pretty sure that there are other recent release team members who could help me out |
| 15:56 |
shulabear |
gmcharlton++ I'd appreciate that, for one. |
| 15:56 |
Bmagic |
gmcharlton++ we can use all the help we can get |
| 15:56 |
berick |
i'm interested |
| 15:57 |
sleary |
I can help out with the release |
| 15:57 |
gmcharlton |
I'll send out a call for scheduling said session |
| 15:57 |
terranm57 |
There's also a recording in one of the New Devs meetings - https://wiki.evergreen-ils.org/doku.php?id=newdevs:meetings:agenda-2023-11 |
| 15:57 |
Bmagic |
gmcharlton: I was just about to ask that |
| 15:57 |
Bmagic |
#link https://wiki.evergreen-ils.org/doku.php?id=newdevs:meetings:agenda-2023-11 |
| 15:58 |
Bmagic |
abneiman++ I think you accomplished your goal |
| 15:58 |
Dyrcona |
Rolling the release itself isn't that hard if enough people who have the proper permissions are around. |
| 15:58 |
terranm57 |
IIRC, the recording doesn't cover the translation stuff, which is quite a few more steps |
| 15:58 |
abneiman |
also, https://bugs.launchpad.net/evergreen/+bug/2043142 (and security bug #1917821) as well as a pile of bugfixes on Item Alerts, Holdings Editor, and a bunch of fixes for Experimential Angular Circ. |
| 15:58 |
pinesol |
Launchpad bug 2043142 in Evergreen "wishlist: Reports security improvements" [Wishlist,New] - Assigned to Mike Rylander (mrylander) |
| 15:59 |
* abneiman |
drops mic |
| 15:59 |
terranm57 |
abneiman++ |
| 15:59 |
Bmagic |
real quick, with the 30 seconds |
| 15:59 |
abneiman |
thanks for letting me, uh, yell-spire you |
| 15:59 |
Bmagic |
#topic New Business - Next Bug Squashing Week? |
| 15:59 |
mmorgan |
abneiman++ |
| 15:59 |
terranm57 |
It's time to plan the next Bug Squashing Week - Maybe the week of February 26 or week of March 18? |
| 15:59 |
abneiman |
and I can help with relteam comms & release notes, etc. but can't take a big role |
| 16:00 |
shulabear |
abneiman++ |
| 16:00 |
Bmagic |
terranm57: My schedule allows for either week |
| 16:00 |
terranm57 |
Bmagic++ |
| 16:01 |
terranm57 |
I'm inclined to push it back to March unless anyone wants it sooner |
| 16:01 |
Bmagic |
nope, that's fine! |
| 16:01 |
abneiman |
+1 to March, I can even promise some shiny new features to test :-D |
| 16:01 |
terranm57 |
Cool beans, I'll put it on the calendar and do all my stuff |
| 16:01 |
abneiman |
and some buffed-up old features |
| 16:02 |
Bmagic |
terranm++ |
| 16:02 |
Bmagic |
#endmeeting |
| 16:02 |
gmcharlton |
and at least a couple buffed-OUT really old things |
| 16:02 |
pinesol |
Meeting ended Tue Feb 13 16:02:11 2024 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:02 |
pinesol |
Minutes: http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-02-13-15.06.html |
| 16:02 |
pinesol |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-02-13-15.06.txt |
| 16:02 |
pinesol |
Log: http://evergreen-ils.org/meetings/evergreen/2024/evergreen.2024-02-13-15.06.log.html |
| 16:02 |
* kmlussier |
stepped away from the meeting at the wrong time. Did any actions come out of that release discussion? |
| 16:02 |
gmcharlton |
Bmagic++ |
| 16:02 |
gmcharlton |
kmlussier: yep, we have a release team |
| 16:02 |
terranm57 |
Bmagic++ ciaaaaaooo y'all |
| 16:03 |
abneiman |
Bmagic++ terranm57++ gmcharlton++ berick++ shulabear++ sleary+++ |
| 16:03 |
abneiman |
sleary++ #rather |
| 16:03 |
kmlussier |
But we still don't have steps towards a larger discussion on release timing. Or is that discussion going to the release team too? |
| 16:03 |
Dyrcona |
kmlussier: No, just a list of bugs. |
| 16:03 |
abneiman |
anyway hope I didn't forget anyone |
| 16:03 |
Bmagic |
Thank you, thank you! I'd like to thank my parents, and my pet dragon! |
| 16:03 |
abneiman |
Dyrcona: it's a list of features, and I eagerly await the schedule the release team puts out so I can coordinate all of that on my end |
| 16:03 |
Dyrcona |
I think it would have been justified to run the meeting over. |
| 16:04 |
Bmagic |
shulabear: I PMed you |
| 16:04 |
gmcharlton |
kmlussier: yeah, at least for the short term (next release), scheduling would be up to the new team to put something specific together |
| 16:04 |
Dyrcona |
abneiman: Understood. |
| 16:04 |
shulabear |
bmagic: just noticed! |
| 16:06 |
kmlussier |
gmcharlton: Understood. I'll keep the rest of my thoughts in my head for now. |
| 16:06 |
Dyrcona |
abneiman: I'll look over the list of features and see what I think. I always reserve the right to change my mind when new evidence comes to light. |
| 16:07 |
* kmlussier |
takes back her last comment and decides to share a thought. |
| 16:07 |
kmlussier |
Regardless of the features in any release, I think it's helpful for Evergreen sites to have a consistent release schedule they can rely on. If there aren't many new features, then it's a smaller release. |
| 16:08 |
sleary |
kmlussier: I think you should revive that discussion on the mailing list. It seems to not fit well into the format of these meetings. |
| 16:08 |
sleary |
I know you didn't get any traction on it last time, though. |
| 16:09 |
kmlussier |
Yeah, maybe. It's just frustrating because I know this community is capable of consistent releases that are not always late. |
| 16:09 |
|
smayo joined #evergreen |
| 16:09 |
abneiman |
Dyrcona: definitely appreciate the feature review. Branches will be coming soon. |
| 16:10 |
|
shulabear left #evergreen |
| 16:14 |
berick |
Dyrcona: i too prefer the YY.MM release nomenclature. the ubuntu release code names are practically useless to me. |
| 16:14 |
berick |
and just becuase a relase is delayed doesn't mean you have to change its yy.mm name. |
| 16:14 |
sleary |
kmlussier: are we comparing to pre-pandemic schedules? My observation is that virtually everyone I know is short-handed, stretched thin, and dealing with some kind of personal or family health crisis. I think we need to adjust our expectations of ourselves. |
| 16:15 |
abneiman |
^^ this |
| 16:16 |
Dyrcona |
berick: It's also what all the "cool" projects are doing, |
| 16:16 |
abneiman |
and for the record, I am neither opposed to a single-release-per-year schedule nor a yy.mm naming scheme, I just would love to see us get out of staring around blankly when it's time to do a release, and continue to run later and later |
| 16:17 |
abneiman |
*and not continue to run later & later. Words. Hard. |
| 16:17 |
Dyrcona |
I said this in private to someone, but I'll repeat it here: "It's not exactly the same community as when we had consistent releases." Some people are no longer part of the community. |
| 16:18 |
abneiman |
and some people are newly part of the community, and as the 3.12 team showed, they are eager / willing / able to learn the process |
| 16:18 |
Dyrcona |
abneiman++ On that, we definitely agree! |
| 16:18 |
kmlussier |
Yeah, adjusting the release schedule is fine to adapt to this new reality. You get no arguments from me on that. |
| 16:19 |
Dyrcona |
I think it might be useful to find out if tarballs are being used. One project I know of stopped releasing them, and said check out the code from git using tags. |
| 16:19 |
Bmagic |
I don't use the tarballs, and i've had that same question "who uses the tarball" |
| 16:20 |
sleary |
Do we have stats on the download page? |
| 16:20 |
Dyrcona |
sleary; I don't know if we run webalyzer, but I might be able to look at the logs. |
| 16:21 |
* Dyrcona |
should know... being on the admin team and all. |
| 16:21 |
Bmagic |
If someone downloads the tar, I think the only track for that is the apache log. Compared to Google analytics which can capture page loads via embedded JS. But a straight download is likely not* captured by GA |
| 16:22 |
sleary |
Webalyzer... now there's a name I haven't heard in a long time |
| 16:22 |
kmlussier |
A discussion about tarballs is fine too. It's great that we're moving forward with this specific release, but, at some point, we need to deal with the questions of what release schedule (both feature and point) works for us now. Do we need a tarball? But I don't think I'm the best person to be bringing these questions to the mailing list since I am not in a position where I can help make these things happen. |
| 16:22 |
* Dyrcona |
should start working on a draft email, but I'm afraid it will turn into War and Peace, if not LotR.... |
| 16:22 |
kmlussier |
And now I'm really done. |
| 16:22 |
kmlussier |
Dyrcona: Sometimes you need that War and Peace discussion to make progress on something. |
| 16:22 |
* abneiman |
whispers great topic(s) for dev hackfest!!! and then vanishes |
| 16:22 |
Dyrcona |
:) |
| 16:30 |
Dyrcona |
Well, the tarballs are definitely being downloaded, but most of the hits look like bots and scripts. |
| 16:34 |
Dyrcona |
Six downloads in the last tow days. This counts both OpenSRF and Evergreen tarballs. |
| 16:34 |
Dyrcona |
s/tow/two/ |
| 16:35 |
Dyrcona |
I tried excluding bots and scripts. |
| 16:35 |
* Dyrcona |
calls it a day. |
| 16:42 |
|
gmcharlton left #evergreen |
| 16:46 |
berick |
Bmagic: hey keep me posted on your redis deployments. i'm hoping to migrate after our 3.11 upgrade this spring. |
| 16:54 |
Bmagic |
berick: will do! |
| 17:11 |
|
kmlussier left #evergreen |
| 17:27 |
|
mmorgan left #evergreen |
| 17:42 |
|
collum joined #evergreen |
| 18:14 |
|
bshum joined #evergreen |
| 18:28 |
pinesol |
News from commits: LP#2043508 fix misconfigured delete dialogs and add dialogs where they were missing. <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f358293943a3a6d031c03f8e5d06327adb3ac450> |
| 18:58 |
pinesol |
News from commits: LP#2043508 follow-up: ng lint --fix <https://git.evergreen-ils.org/?p=Evergreen.git;a=commitdiff;h=f1fa8cfa6e2a700c17e10886bd7d8044c1b45a31> |
| 19:52 |
|
collum joined #evergreen |
| 20:32 |
|
collum joined #evergreen |
| 21:10 |
|
collum joined #evergreen |
| 21:33 |
|
collum joined #evergreen |
| 22:10 |
|
collum joined #evergreen |
| 22:32 |
|
collum joined #evergreen |
| 23:12 |
|
collum joined #evergreen |
| 23:35 |
|
collum joined #evergreen |
