| Time |
Nick |
Message |
| 05:52 |
|
gsams joined #evergreen |
| 06:40 |
|
rlefaive joined #evergreen |
| 07:30 |
|
JBoyer joined #evergreen |
| 07:53 |
|
ericar joined #evergreen |
| 07:59 |
|
rlefaive joined #evergreen |
| 08:31 |
|
mrpeters joined #evergreen |
| 08:43 |
|
mmorgan joined #evergreen |
| 08:43 |
|
book` joined #evergreen |
| 09:00 |
|
rlefaive joined #evergreen |
| 09:18 |
|
bos20k joined #evergreen |
| 09:22 |
|
yboston joined #evergreen |
| 10:02 |
|
mmorgan1 joined #evergreen |
| 10:12 |
|
kmlussier joined #evergreen |
| 10:28 |
|
terran joined #evergreen |
| 10:57 |
|
mmorgan joined #evergreen |
| 10:59 |
|
yboston joined #evergreen |
| 11:03 |
|
brahmina joined #evergreen |
| 11:05 |
|
rlefaive joined #evergreen |
| 11:07 |
|
sam_l joined #evergreen |
| 11:08 |
|
Christineb joined #evergreen |
| 11:13 |
|
bos20k_ joined #evergreen |
| 11:25 |
yboston |
gmcharlt: FYI, did you see this wishlist bug? In case you wanted to add your comemnts fromt eh last conference to it regarding new approaches lp 1575908 |
| 11:25 |
pinesol_green |
Launchpad bug 1575908 in Evergreen "It should be possible to put dereferencable URIs in $0 of authorized fields" [Undecided,New] https://launchpad.net/bugs/1575908 |
| 11:29 |
|
rlefaive joined #evergreen |
| 11:30 |
gmcharlt |
yboston: folks |
| 11:30 |
gmcharlt |
er, thanks |
| 11:30 |
gmcharlt |
and howdy folks - re bug 1579225, I think it warrants an early 2.10.3; I would appreciate eyes on it |
| 11:30 |
pinesol_green |
Launchpad bug 1579225 in Evergreen "Patron registration- unable to log in with password entered during registration" [High,Confirmed] https://launchpad.net/bugs/1579225 |
| 11:36 |
dbwells |
gmcharlt: I've given it a once (or twice) over and it seems sensible. Rolling it out now to try to test more angles in our live environment. Do you know the simplest means to reproduce the double-hashing problem? I think we experienced that last week, but I haven't tracked it down yet. |
| 11:38 |
gmcharlt |
dbwells: from the user side, it's just a matter of registering a completely new patron in either the XUL or web staff interfaces |
| 11:39 |
dbwells |
gmcharlt: sorry, I was unclear. I mean the later updates which corrupt the password (e.g. address updates). Does that happen for every address update? |
| 11:40 |
gmcharlt |
dbwells: ah, gotcha. no, I don't believe it would occur with every address updates, just ones that add or subtract an address and thereby causes an update of the base patron record |
| 11:41 |
dbwells |
gmcharlt: okay, that helps a lot, thank you |
| 11:48 |
|
rlefaive joined #evergreen |
| 11:55 |
|
sandbergja joined #evergreen |
| 11:58 |
kmlussier |
+1 to early 2.10.3 release. |
| 12:06 |
|
jihpringle joined #evergreen |
| 12:16 |
|
bos20k joined #evergreen |
| 12:23 |
|
brahmina joined #evergreen |
| 12:24 |
|
jvwoolf joined #evergreen |
| 12:27 |
dbwells |
gmcharlt: I am off to lunch, but everything looks good in my testing. I posted a sign-off branch to the bug. Hopefully others will still weigh in. |
| 12:47 |
jeffdavis |
I'll be testing that branch today fwiw. |
| 12:48 |
|
bmills joined #evergreen |
| 12:52 |
dbs |
gmcharlt: +1 to your response on bib record / auth record $0 stuff |
| 12:53 |
dbs |
I guess I should just gmcharlt++ so it counts :) |
| 12:53 |
gmcharlt |
well, there's always the possibility of +1, but gmcharlt-- # I agree with you... dagnabbit! |
| 12:53 |
gmcharlt |
;) |
| 13:29 |
bshum |
Doh, and I forgot the best reason to be in IRC... pinesol! |
| 13:50 |
|
mmorgan1 joined #evergreen |
| 13:51 |
mceraso |
bshum: Or the @dessert!!! |
| 14:03 |
csharp |
@dessert pinesol_green |
| 14:03 |
* pinesol_green |
grabs some Key Lime Pie for pinesol_green |
| 14:10 |
kmlussier |
As much as I love pinesol_green, I suspect heavy bot activity could cause more confusions for users who are already feeling uncomfortable with IRC. |
| 14:11 |
kmlussier |
And I do love the bots, so please don't use the above comment as a reason to stop giving me desserts pinesol_green! |
| 14:12 |
kmlussier |
@dessert [someone] |
| 14:12 |
* pinesol_green |
grabs some Key Lime Cheesecake for jeff |
| 14:12 |
|
Dan-BAPL joined #evergreen |
| 14:26 |
kmlussier |
gmcharlt++ #Quick response to bug 1579225 |
| 14:26 |
pinesol_green |
Launchpad bug 1579225 in Evergreen "Patron registration- unable to log in with password entered during registration" [High,Confirmed] https://launchpad.net/bugs/1579225 |
| 14:33 |
|
cag00 joined #evergreen |
| 14:37 |
|
yboston_ joined #evergreen |
| 14:44 |
jeff |
jvwoolf: I'm interested in the Reports Interest Group meeting today at 3 PM, but won't be able to make it until after 3:15 PM. Not that I expect anything to change as a result of this, but just wanted to mention that I'll be "late". |
| 14:45 |
|
Callender_ joined #evergreen |
| 14:45 |
jvwoolf |
jeff: That's cool. We'll see you after 3:15 :) |
| 14:56 |
jvwoolf |
Just a reminder that the Reports Interest Group meeting is starting in a few minutes. |
| 14:57 |
|
massalex joined #evergreen |
| 14:57 |
* cag00 |
Ok Jessica |
| 15:03 |
jvwoolf |
#startmeeting Reports Interest Group |
| 15:03 |
pinesol_green |
Meeting started Mon May 9 15:03:18 2016 US/Eastern. The chair is jvwoolf. Information about MeetBot at http://wiki.debian.org/MeetBot. |
| 15:03 |
pinesol_green |
Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. |
| 15:03 |
pinesol_green |
The meeting name has been set to 'reports_interest_group' |
| 15:03 |
jvwoolf |
Hello everyone! The meeting agenda can be found here: http://wiki.evergreen-ils.org/doku.php?id=evergreen-reports:meetings:2016-05-09 |
| 15:04 |
jvwoolf |
Let's get started with introductions. |
| 15:04 |
* jvwoolf |
is Jessica Woolford, Bibliomation, CT |
| 15:04 |
* cag00 |
is Carol Yarrison from Bibliomation |
| 15:06 |
* rhamby_ |
is Rogan Hamby, Equinox Software |
| 15:06 |
|
mllewellyn joined #evergreen |
| 15:08 |
jvwoolf |
Hey cag00 and rhamby_. Anybody else? |
| 15:10 |
terran |
#info terran is Terran McCanna, PINES, GA |
| 15:10 |
|
dcz joined #evergreen |
| 15:10 |
jvwoolf |
Welcome, terran! |
| 15:12 |
jvwoolf |
I'll give folks another couple of minutes to roll in, but if it stays this small, maybe we'll just have a casual discussion. |
| 15:13 |
terran |
csharp is planning to attend, but will be a few minutes late |
| 15:13 |
jeff |
#info jeff is Jeff Godin - Traverse Area District Library (TADL) |
| 15:13 |
jvwoolf |
Hi jeff |
| 15:14 |
jvwoolf |
terran: Thanks for the info |
| 15:15 |
jvwoolf |
Well, might as well get started |
| 15:15 |
jvwoolf |
#topic 2016 Conference Discussion |
| 15:16 |
jvwoolf |
I thought there were a lot of great reports programs at the conference this year |
| 15:16 |
jvwoolf |
Did anyone learn anything new? |
| 15:17 |
jvwoolf |
(Most folks here were presenting on the topic, I think) |
| 15:17 |
* cag00 |
yes, I think so |
| 15:17 |
cag00 |
I enjoyed the preconference reports session |
| 15:18 |
cag00 |
Now I understand what a link is... |
| 15:18 |
jeff |
Are any materials from any of the pre-conference sessions available? I'm interested to see what sorts of things were covered. |
| 15:18 |
jvwoolf |
csharp++ He does a good job. |
| 15:18 |
terran |
I got a lot out of Chris Sharp's and Rogan Hamby's pre-conference sessions, and feel like I understand aggregate fields and the field mapper a little better. |
| 15:19 |
rhamby_ |
My discussion was pretty free form based on what attendees had questions about so I don't have much in the way of materials per se to share. |
| 15:19 |
* cag00 |
You always do a good job |
| 15:19 |
jvwoolf |
rhamby_++ |
| 15:19 |
jeff |
Were there any wishlists that came out of either session's discussions? |
| 15:20 |
jeff |
wishlists, buglists, etc? |
| 15:20 |
rhamby_ |
Not so much out of mine but there's always a huge laundry list of things that people want from reports. |
| 15:20 |
* csharp |
appears |
| 15:20 |
jvwoolf |
jeff: They were more informational than aspirational, I think |
| 15:20 |
jvwoolf |
csharp: Welcome! |
| 15:21 |
jeff |
rhamby_: Sorry, I don't think I parsed that one successfully: "there's always a huge list but not this time?" |
| 15:21 |
rhamby_ |
jeff: there are always a lot of things people want but they didn't come during my session |
| 15:22 |
jeff |
rhamby_: got it. |
| 15:22 |
rhamby_ |
that should be "come up during my session" |
| 15:22 |
rhamby_ |
I'm suffering from "brain ahead of fingers-itis" today |
| 15:24 |
jeff |
rhamby_: that's okay. i originally joined this meeting via my phone as I walked in the building. I'm lucky I didn't state my affiliation as "Ytsbrtdr Strs Fodytovy :ontstu (YSF:)" |
| 15:25 |
|
chtrotter joined #evergreen |
| 15:25 |
jvwoolf |
rhamby_: You cleared something up for me during your session that I had wondered about |
| 15:25 |
jvwoolf |
Namely that is doesn't matter which table is referenced first in an ON statement |
| 15:26 |
rhamby_ |
jvwoolf: I'm glad that helped :) |
| 15:26 |
jvwoolf |
I had been writing statements the way you described, (with the joined table to the right of the =), but didn't know the other way was correct as well. |
| 15:27 |
* jvwoolf |
is learning to love SQL |
| 15:27 |
jeff |
So, with more people more-well-versed in writing SQL queries, is there any more interest in having a nice frontend way to run those queries, as in Jasper Reports Server or similar? |
| 15:28 |
|
mmorgan joined #evergreen |
| 15:28 |
csharp |
jeff: re: materials from my preconf - I just had an outline that I sent to the conference planning committee last week - it isn't up on the conf site yet, but I'm happy to share with anyone |
| 15:29 |
jeff |
csharp: cool! i'd be interested. i think you have my contact info. :-) |
| 15:30 |
jvwoolf |
jeff: I'm always interested in better ways to deliver reports to libraries. |
| 15:30 |
rhamby_ |
I'm a proponent of an interface for running sql queries in the staff client with variables that could be filled in by authorized users. I don't know how popular that idea would be. |
| 15:30 |
jeff |
rhamby_: that sounds like something else entirely. what would your use case be? |
| 15:30 |
jeff |
rhamby_: not reporting, but something else? |
| 15:31 |
chtrotter |
Hey, all. Cristina Trotter from Oconee Regional Library System (PINES) here. Apologies for arriving late. |
| 15:31 |
rhamby_ |
jeff: my vision for it would be reporting. it could conceivably be extended to other sql functions but that's not what I had in mind. |
| 15:31 |
jvwoolf |
Welcome, chtrotter! |
| 15:31 |
cag00 |
rhamby_: I think that is basically what we had in WebReporter used in Horizon days |
| 15:32 |
rhamby_ |
cag00: My horizon memory is a little vague these days (I used to be a Horizon user) but I think there would be superficial similarities, more from parallel evolution than one following the other though. |
| 15:33 |
csharp |
people *say* they want a direct SQL interface, but I'm pretty sure they don't actually want to be writing raw queries against the DB as-is - I think we'd need far more end-user-friendly views in place |
| 15:33 |
jeff |
rhamby_: then perhaps you're exactly describing something like jasper. further discussion may be warranted. :-) |
| 15:34 |
rhamby_ |
jeff: I think Jasper has a good place too. I don't think there is such a thing as a single viable reports solution for all users. I'm sure there's at least two, and I could easily be convinced there are three separate types of users and needs. |
| 15:34 |
|
bos20k_ joined #evergreen |
| 15:34 |
terran |
It would be handy if the Reporter interface would show you the SQL that it's generating on the fly, so that you could see what it's doing prior to actually running the report. |
| 15:35 |
cag00 |
terran: I agree, I could learn better that way too |
| 15:36 |
jvwoolf |
jeff: Did you do a program on Jasper in years past? |
| 15:36 |
jeff |
I did. It has changed a bit since then, as has our usage here. |
| 15:37 |
chtrotter |
As a library staff member who is on the advanced end of reporting using the staff client, I would definitely *love* some sort of access to running SQL queries. I certainly would not complain if it were a more user-friendly front-end user interface. |
| 15:39 |
jvwoolf |
jeff: I would love to hear about how it has changed. Not that I remember much about it, other than it was cool. |
| 15:39 |
rhamby_ |
I think one thing we gave up in exchange for more power in the reporter over the years was less overhead for casual users. |
| 15:39 |
rhamby_ |
I don't think this is a bad thing but it's a trade off that's hard to avoid. |
| 15:40 |
|
bos20k joined #evergreen |
| 15:41 |
chtrotter |
jvwoolf: Is there a way we can have an interest group meeting via some webinar software... and maybe where we can sweet talk jeff into showing us how they are using Jasper? |
| 15:41 |
cag00 |
jvwoolf: I second that motion. |
| 15:41 |
jvwoolf |
jeff: Can we bribe you with kharma? |
| 15:42 |
jeff |
heh |
| 15:42 |
jvwoolf |
jeff++ |
| 15:42 |
cag00 |
I do not remember much about the product other than it was cool as jvwoolf said |
| 15:43 |
jeff |
Sounds worth some prep time. I'll see what I can do. Mostly I'm glad to hear that there's some interest. It's lonely out here all by ourselves. :-) |
| 15:43 |
chtrotter |
jeff++ |
| 15:43 |
cag00 |
jeff++ |
| 15:45 |
rhamby_ |
I'm not familiar with Jasper but it sounds like a great solution for a lot of users. |
| 15:45 |
rhamby_ |
jeff: is it fairly straight forward to export and import some kind of template with it? |
| 15:45 |
rhamby_ |
What I'm thinking of is so that there would be an easy mechanism for community members to share reports. |
| 15:46 |
jeff |
That's my hope. |
| 15:46 |
cag00 |
That would be very nice. |
| 15:47 |
jeff |
Sorry to keep beating the "we use Jasper" drum. I'll lay off now. :-) |
| 15:47 |
jvwoolf |
jeff: No worries. :) |
| 15:47 |
jvwoolf |
Looks like your drum beats attracted some interest |
| 15:47 |
jeff |
There's some interest -- that's good enough for me to put some more time into writing some things up. |
| 15:48 |
cag00 |
I would like to hear more about Jasper, it has been awhile since you presented |
| 15:49 |
csharp |
jeff: well, you know I'm interested too :-) |
| 15:50 |
jvwoolf |
Not too change gears too quickly, but csharp and terran: I'm very excited about the Quick Reporter |
| 15:50 |
csharp |
we're pretty happy with it too |
| 15:51 |
terran |
Our users are too! bmills installed it on his test server during our session at the conference and had it up and running by the time we left :) |
| 15:51 |
jvwoolf |
Wow! I should have paid attention to what he was doing. I was sitting right next to him! |
| 15:52 |
jvwoolf |
terran: Your materials are posted, right? |
| 15:52 |
terran |
He found a handful of small issues that we need to tweak, but nothing huge. |
| 15:52 |
chtrotter |
Yes, the Quick Reporter has been super helpful for branch managers and department heads around here. |
| 15:52 |
terran |
Yes, everything should be posted - and feel free to ask us questions |
| 15:53 |
jeff |
csharp, terran: Are any of the earlier commits of the report creator / quick reporter interface available? |
| 15:55 |
csharp |
jeff: well, it wasn't developed in git - just committed there at the end - is there something we can find out for you? |
| 15:55 |
jeff |
And is there a preferred place to track issues, like those that bmills identified already? |
| 15:55 |
terran |
jeff: the earlier versions were PINES-specific and I believe they're in the PINES repo - csharp, do you know for sure |
| 15:56 |
csharp |
they aren't publicly available - the current repo clobbered what was put there last year |
| 15:56 |
jeff |
csharp: mostly I was curious, nothing specific. The files contain copyright dates going back to 2005, so I thought that there might be more history somewhere. |
| 15:56 |
|
jlitrell joined #evergreen |
| 15:56 |
jeff |
csharp: The revision logs are often very useful in determining intent when the docs / comments don't state things explicitly. |
| 15:56 |
csharp |
oh - hmm - that would either be using older files from something else or a typo ;-) |
| 15:56 |
csharp |
right |
| 15:56 |
terran |
I'm guessing typo :D |
| 15:57 |
jeff |
Ah. Perhaps a copy-paste from Evergreen without changing the date. |
| 15:57 |
csharp |
well, our contractors don't "live" in git like the EG project does, so there's been a learning curve |
| 15:58 |
jeff |
Since the first date I noticed was in the file COPYING, I'm betting that one of your requirements was "same license as Evergreen, please" -- and thus, an exact copy of COPYING. :-) |
| 15:59 |
jeff |
Thanks for satisfying my curiosity on that one. |
| 15:59 |
csharp |
jeff: probably it |
| 15:59 |
jeff |
As for issue tracking -- any thoughts? Do you have a list anywhere of the things bmills found? |
| 16:00 |
terran |
So far it's just a list sitting in my in-box that I haven't had a chance to go over yet. |
| 16:00 |
jeff |
Got it. :-) |
| 16:01 |
jeff |
What do your users like best about it, and what do you like best about it? |
| 16:02 |
terran |
Since it's an add-on, and not part of Evergreen, we'll need to set up something outside of Evergreen's Bug Tracker - maybe a different launchpad account |
| 16:04 |
jvwoolf |
terran: Keep us posted! |
| 16:04 |
jvwoolf |
I have to run soon but there were a couple other things I wanted to mention. |
| 16:04 |
terran |
Our libraries have reported that the interface is more user-friendly / less intimidating, and it's easier for them to find the reports they need. We like that it's reduced the number of help desk questions we get dramatically. |
| 16:05 |
terran |
I also like that I can run reports from my phone :D |
| 16:05 |
jvwoolf |
First, I don't think akilsdonk is around but I hope she posts her slides! I found her session on acqusitions reports very helpful. |
| 16:05 |
* jvwoolf |
doesn't speak acq. |
| 16:05 |
jvwoolf |
terran: That is awesome! |
| 16:06 |
csharp |
oh, we can also share our documentation for the reports we have added to quick reports - they depend on reporter.classic_item_list pretty heavily (which is a PINES view that doesn't match others' setups, but could probably be enabled without any real harm) |
| 16:07 |
csharp |
I heard from our acq person that akilsdonk's session was excellent |
| 16:07 |
jeff |
csharp: the same reporter.classic_item_list that's in Open-ILS/src/sql/Pg/example.reporter-extension.sql in the Evergreen source, or modified from that? |
| 16:07 |
csharp |
jeff: yeah, that one, unmodified |
| 16:07 |
csharp |
in fact, when I modify it in PINES, I modify it there first :-) |
| 16:08 |
csharp |
since it's kind of "ours" |
| 16:08 |
jeff |
csharp++ |
| 16:08 |
jeff |
you're a good man, charlie bro^W^Wcsharp |
| 16:08 |
jvwoolf |
csharp: Looks like the templates are posted along with the presentation notes |
| 16:09 |
csharp |
oh good |
| 16:09 |
csharp |
jeff: :-D |
| 16:10 |
jvwoolf |
One last thing before I have to depart |
| 16:10 |
jvwoolf |
#topic Meeting schedule |
| 16:10 |
csharp |
(then we'll start the REAL meeting :-)) |
| 16:10 |
jvwoolf |
csharp: I see liberal use of @bartender in the future |
| 16:11 |
csharp |
ha! |
| 16:11 |
jvwoolf |
Anyhow, does anyone object to chaging the meeting schedule to quarterly? |
| 16:11 |
jvwoolf |
I can put something out on the list too, just figured I'd float it here first |
| 16:11 |
csharp |
no objections here, since attempts at monthly meetings have quickly petered out the past |
| 16:13 |
jeff |
works for me. i suspect if we do it properly more things will be done between meetings and in list conversations than during meetings. |
| 16:14 |
jvwoolf |
I agree. |
| 16:14 |
jvwoolf |
I'm thinking September or October for the next meeting |
| 16:14 |
jvwoolf |
jeff: Would that be enough time for you to put something together on Jasper Reports? |
| 16:14 |
cag00 |
Sounds good to me |
| 16:15 |
jvwoolf |
Or do you want to save that for the conference? |
| 16:15 |
jeff |
I would hope to have shared many interesting things before then, and would be happy to discuss if folk were still interested. |
| 16:16 |
jvwoolf |
Cool, thanks. I'll be in touch. :) |
| 16:16 |
csharp |
hopefully I will get around to setting up a jasper test instance before then too :-) |
| 16:16 |
jvwoolf |
And eagerly awaiting the things you'll share :) |
| 16:16 |
csharp |
jvwoolf++ # thanks for setting up this meeting |
| 16:17 |
terran |
and I'll figure out a Quick Reports bug tracker site before then... |
| 16:17 |
terran |
jvwoolf++ |
| 16:17 |
chtrotter |
jvwoolk++ |
| 16:17 |
jvwoolf |
Thanks for coming everyone! |
| 16:17 |
jvwoolf |
#endmeeting |
| 16:17 |
pinesol_green |
Meeting ended Mon May 9 16:17:50 2016 US/Eastern. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) |
| 16:17 |
pinesol_green |
Minutes: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-05-09-15.03.html |
| 16:17 |
pinesol_green |
Minutes (text): http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-05-09-15.03.txt |
| 16:17 |
pinesol_green |
Log: http://evergreen-ils.org/meetings/evergreen/2016/evergreen.2016-05-09-15.03.log.html |
| 16:19 |
csharp |
#endworkday |
| 16:24 |
jeff |
csharp: how's that working for you? :-) |
| 16:27 |
csharp |
jeff: IT DIDN'T WORK! |
| 16:28 |
terran |
csharp: one of us, one of us |
| 16:39 |
kmlussier |
jvwoolf++ |
| 16:45 |
pinesol_green |
[evergreen|Galen Charlton] LP#1579225: add live_t regression test - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=82c0202> |
| 16:45 |
pinesol_green |
[evergreen|Galen Charlton] LP#1579225: fix handling of passwords in patron registration - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=9289743> |
| 16:48 |
* gmcharlt |
starts the release-cutting dance |
| 16:48 |
|
jvwoolf left #evergreen |
| 17:03 |
jeff |
Wow. Conference Attendees list this year includes cell phone and work phone numbers, as well as whatever people supplied for their mailing address. That's... surprising. |
| 17:04 |
gmcharlt |
release notes for 2.10.3 are available at collab/gmcharlt/release_notes_2_10_3 - feedback invited |
| 17:04 |
gmcharlt |
http://git.evergreen-ils.org/?p=working/Evergreen.git;a=commitdiff;h=c8e422690b5ec6ff3a8dab2f5dae87448803850e |
| 17:04 |
jeff |
(previous year included name, organization, state/province, email, twitter handle, irc nick) |
| 17:09 |
|
mmorgan left #evergreen |
| 17:11 |
pinesol_green |
[evergreen|Galen Charlton] 2.10.2 to 2.10.3 schema upgrade script - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=65ca2a0> |
| 17:28 |
jeff |
With all of that added info, it's an interesting study in "how many different ways can a group of people list their work address" |
| 17:33 |
pinesol_green |
[evergreen|Galen Charlton] release notes for 2.10.3 - <http://git.evergreen-ils.org/?p=Evergreen.git;a=commit;h=0f0f6c1> |
| 17:40 |
dbs |
need to update history.git |
| 18:04 |
gmcharlt |
the 2.10.3 release is just about ready to go; I'll put it up after dinnner |
| 18:39 |
jeffdavis |
password fix is tested and confirmed here, but I can see it doesn't need any more signoffs :) |
| 18:39 |
jeffdavis |
gmcharlt++ |
| 18:41 |
jihpringle |
gmcharlt++ |
| 19:52 |
gmcharlt |
https://evergreen-ils.org/evergreen-2-10-3-released/ |
| 20:13 |
jlitrell |
gmcharlt++ |
| 20:13 |
jlitrell |
'tis lovely. |
| 22:50 |
|
geoffsams joined #evergreen |
