Evergreen ILS Website

IRC log for #evergreen, 2014-07-28

| 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
00:39 mtcarlson joined #evergreen
00:50 mcarlson joined #evergreen
02:37 tsbere__ joined #evergreen
02:59 tsbere_ joined #evergreen
04:28 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
05:05 mnsri joined #evergreen
05:12 book` joined #evergreen
07:27 collum joined #evergreen
07:44 eeevil joined #evergreen
07:54 Shae joined #evergreen
08:03 rjackson-isl joined #evergreen
08:20 ericar joined #evergreen
08:20 ericar left #evergreen
08:26 akilsdonk joined #evergreen
08:28 mrpeters joined #evergreen
08:32 tspindler joined #evergreen
08:35 Dyrcona joined #evergreen
08:46 mmorgan joined #evergreen
09:00 jboyer-isl joined #evergreen
09:17 kmlussier joined #evergreen
09:19 kmlussier joined #evergreen
09:19 kmlussier @coffee
09:19 * pinesol_green brews and pours a cup of Costa Rica Finca Cerro Palado, and sends it sliding down the bar to kmlussier
09:28 yboston joined #evergreen
09:37 mllewellyn joined #evergreen
09:50 kmlussier1 joined #evergreen
09:56 berick joined #evergreen
09:56 mtcarlson joined #evergreen
10:01 * dbs coffees up
10:09 * Dyrcona cokes up..... Wait! That doesn't sound right! ;)
10:11 * bshum picked the wrong week to quit sniffing glue.
10:11 Dyrcona :)
10:14 bshum I might have been thinking about that movie's quotes alot this weekend.  "I just want to tell you both, good luck, we're all counting on you."
10:15 dbs Ah, canada lost a good one when Leslie Nielsen passed.
10:15 dbs Little known fact: "Men With Brooms" was shot in Sudbury.
10:15 dbs Little known, probably because it has been little seen  :)
10:17 dbs Co-starring the fabulous Molly Parker, now a supah-star (House of Cards most recently), but first brought to my attention in "Five Senses" (movie) and then the amazing "Twitch City" (CBC series filmed in my old student neighbourhood in Toronto)
10:18 dbs And thus ends your Canuck media history / triva lesson for the #evergreen channel for the day
10:23 rjackson_isl joined #evergreen
10:38 csharp @dessert [someone]
10:38 * pinesol_green grabs some Lemon Chess Pie for mceraso
10:39 * csharp thinks "Police Squad" was one of the best shows ever
10:56 mceraso I've had Lemon Chess Pie before...it's delicious :)
11:04 awitter1 joined #evergreen
11:13 vlewis joined #evergreen
11:29 Wyuli joined #evergreen
11:57 RoganH joined #evergreen
12:12 kmlussier Reminder: We have a dev meeting scheduled for 3 p.m. EDT today. You an add any agenda items to http://wiki.evergreen-ils.org/dok​u.php?id=dev:meetings:2014-07-28.
12:31 mtcarlson joined #evergreen
12:32 Wyuli joined #evergreen
12:38 awitter1 left #evergreen
12:46 DPearl1 joined #evergreen
12:46 DPearl1 left #evergreen
12:47 DPearl1 joined #evergreen
13:12 artunit joined #evergreen
13:50 mllewellyn joined #evergreen
14:12 zerick joined #evergreen
14:19 bshum DPearl++ RoganH++ # I'll merge the merge parts code to master
14:19 RoganH bshum++
14:22 pinesol_green [evergreen|Dan Pearl] LP#1099979 Provide facility to merge parts in the Monograph Parts display - <http://git.evergreen-ils.org/?p=​Evergreen.git;a=commit;h=8f4d3ef>
14:29 vlewis In general, what does 'command_tab' do?  obj.command_tab(event,obj.url_prefix......
14:34 tsbere vlewis: It either replaces the current tab's contents or makes a new tab based on preferences and held down modifiers
14:38 tsbere vlewis: Oh, and if it isn't a toolbar button click that triggers the function then it is pretty much an alternately named set_tab
14:50 kmlussier joined #evergreen
14:54 kmlussier Notable quote from our meeting today with new acq libraries: "This is a great system."
14:55 kmlussier acq has come a long way in the past 2 years.
14:58 DPearl1 bshum: Thanks!
15:02 berick kmlussier: nice.  that's the second positive input i've heard about acq today.
15:03 kmlussier berick: Really? That's great!
15:03 kmlussier Meeting time?
15:06 dbs Time. Time.
15:06 * kmlussier is good at scheduling meetings, but always forgets to get volunteers to facilitate.
15:07 kmlussier #startmeeting Evergreen Developer Meeting - 2014-07-28
15:07 pinesol_green Meeting started Mon Jul 28 15:07:55 2014 US/Eastern.  The chair is kmlussier. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:07 pinesol_green Useful Commands: #action #agreed #help #info #idea #link #topic.
15:07 pinesol_green The meeting name has been set to 'evergreen_developer_meeting___2014_07_28'
15:08 jeff kmlussier++
15:08 bshum kmlussier++ # just getting back to my desk
15:08 kmlussier #info Agenda is available at http://evergreen-ils.org/dokuwiki/d​oku.php?id=dev:meetings:2014-07-28
15:08 kmlussier #topic Introductions
15:08 kmlussier #info kmlussier is Kathy Lussier, MassLNC
15:08 jeff #info jeff is Jeff Godin, Traverse Area District Library (TADL)
15:08 eeevil #info eeevil == Mike Rylander, Equinox Software
15:08 bshum #info bshum is Ben Shum, Bibliomation
15:08 DPearl1 Dpearl1 is Dan Pearl, C/W MARS Inc.
15:08 Dyrcona #info Dyrcona is Jason Stephenson, MVLC
15:08 phasefx #info phasefx = Jason Etheridge @ ESI
15:08 gmcharlt #info gmcharlt = Galen Charlton, ESI
15:09 dbs #info dbs is Dan Scott, Laurentian University
15:09 dbwells #info dbwells is Dan Wells, Hekman Library (Calvin College)
15:09 RoganH #info RoganH = Rogan Hamby, SCLENDS
15:09 DPearl1 #info Dpearl1 is Dan Pearl, C/W MARS Inc.
15:09 berick #info berick Bill Erickson, ESI
15:09 ldw #info ldw = Liam Whalen, Sitka
15:09 phasefx want to see how many different formats get used for folks introducing themselves :)
15:09 eeevil phasefx: I'm personally tickled by the assignment version :)
15:10 gmcharlt OpenSRF/BASIC: LET gmcharlt = Galen Charlton
15:10 RoganH eeevil: we could see how many types of assigning variables that could be done.  Set Rogan = .....
15:10 kmlussier OK, people can continue introducing themselves as we move forward.
15:11 kmlussier #topic Action Items from Last Meeting
15:11 eeevil REM I like it
15:11 kmlussier #info dbwells to review and comment on conditional negative balance bug:https://bugs.launchpad.net/evergreen/+bug/1198465
15:11 pinesol_green Launchpad bug 1198465 in Evergreen "Support for Conditional Negative Balances" (affected: 14, heat: 62) [Wishlist,Confirmed]
15:11 kmlussier So dbwells has added code to this bug and also added some comments today.
15:11 * kmlussier hasn't had a chance to review the most recent comments.
15:12 dbwells Yeah, remingtron and I worked on it for a few days right after the last meeting, but haven't heard back, nor gotten back to it ourselves since.
15:13 dbwells I posted something today just to give it at least *some* small momentum forward :)
15:13 csharp #info csharp is Chris Sharp, GPLS
15:14 jeff dbwells++ remingtron++
15:14 kmlussier As part of this action item and the next one, I haven't had a chance to review the most recent code or pull together my summary. The negative balance was 1 of 4 billing projects MassLNC was working on. We decided a few weeks ago to really focus on the other three so that we can get them out of the way before we get back to negative balances, which is a harder nut to crack.
15:14 jeff (for rounding up scarce tuits)
15:15 kmlussier But just glancing at dbwells' most recent comment, it looks like there is still a bit of work to be done before this branch is ready to be merged?
15:15 dbwells Testing at the very least, but like I mentioned, I think a few hours spent on display side would be time well spent for me.
15:16 kmlussier dbwells: I'm having a hard time picturing what you suggested in your comment, but I also had some concerns on the display side.
15:18 kmlussier I also don't think I'll have a chance to test the most recent code until we finish working on our two remaining billing projects. Having two dev branches loaded on the test server at the same time causes confusion over which one might be causing a problem.
15:19 Dyrcona Well, when they're related to the same part of the system, anyway.
15:21 dbwells kmlussier: If you have a testing timeline in mind, I can try to work on my display ideas so you can test it at the same time.  Feel free to get in touch after this meeting if needed.
15:21 kmlussier So I guess we need some kind of action item for me to test the current branch and provide feedback? I don't know if anyone else wants to take a look at it.
15:21 jeff I've interest but cannot guarantee that I can make time for it in the next month.
15:22 kmlussier dbwells: Will do. I'll have to consult with Dyrcona regarding a testing timeline, but we can figure it in short order.
15:22 jeff I'll see what I *can* do, though.
15:22 kmlussier jeff++ Thanks!
15:22 kmlussier #action kmlussier and others to make time to test the latest branch.
15:23 kmlussier #action dbwells to work on display ideas for negative balance branch
15:23 kmlussier dbwells and remingtron: Thanks for taking a look at it!
15:23 kmlussier Anything else before we move on?
15:23 jeff reducing the number of cases where we deviate from stock is a goal, and our own branch to avoid negative balances is ripe for elimination if we can assist in testing this one.
15:23 Dyrcona dbwells++ remingtron++
15:24 kmlussier #topic OpenSRF release
15:24 kmlussier Anything to report one OpenSRF?
15:24 gmcharlt I'm looking for volunteers to test the websockets work submitted by berick
15:24 gmcharlt any takers?
15:24 bshum Further down in the agenda, there's some notes about websockets
15:25 bshum Sorry, juggling between meetings
15:25 jeff I can test, assuming berick or others are available for questions when I reach that point.
15:25 berick anything I can do to make testing easier?
15:25 berick jeff: yes
15:25 jeff berick++ thanks!
15:25 eeevil gmcharlt: re your 3 options, I'm strongly in favor of merging what's there and getting the release out
15:25 gmcharlt likewise
15:26 gmcharlt jeff: can you put some testing time into this week?
15:26 * csharp can test, but has not had the time lately to keep up with development, so may need assistance ;-)
15:26 jeff gmcharlt: yes. i was just about to ask what timeline you had in mind.
15:26 kmlussier berick: How many testers do you need?
15:26 kmlussier Sorry, that was for gmcharlt.
15:26 gmcharlt jeff: let's shoot for by the end of this week, if you can
15:27 eeevil berick: is it true that anyone whose tested your dev on your demo server has tested the websockets code?
15:27 berick eeevil: they have, indeed
15:27 jeff gmcharlt: i will shoot for that. thanks!
15:27 gmcharlt ok
15:28 csharp then Terran has definitely been testing
15:28 eeevil csharp: :)
15:28 dbs They all haven't installed it locally though :)
15:28 kmlussier So for an action item, that's jeff and csharp? Do we need more testers or is that good?
15:28 gmcharlt given that, I'm planning on cutting an alpha of OpenSRF the middle of next week
15:28 berick dbs: exactly.
15:28 bshum Does the websockets work interact with the current staff client?
15:28 csharp yeah, I'll install locally
15:29 berick bshum: it does not interract, but code the staff client uses is touched, like the JS opensrf libs
15:29 bshum Just making sure that present stuff continues to function I guess over what's coming next too.
15:29 eeevil bshum: only insofar as its part of opensrf ... the current SC does not attempt to make use of it
15:29 bshum Okay.
15:29 bshum So that's something we ought to test as well.
15:29 berick bshum: definitely
15:29 bshum To make sure that it doesn't break any existing functionality
15:29 kmlussier #action jeff and csharp to test websockets work by the end of this week.
15:30 kmlussier #action gmcharlt to cut alpha of OpenSRF the middle of next week (week of Aug. 4th)
15:30 kmlussier Anything else on OpenSRF?
15:31 kmlussier #topic Evergreen maintenance releases
15:31 kmlussier dbwells?
15:31 dbwells #info 2.6.2 and 2.5.6 were released on 7/7
15:32 dbwells I would also like to ask about the next round, which was due last Friday.
15:32 dbwells There is only one actual code change: https://bugs.launchpad.net/​evergreen/+milestone/2.6.3
15:32 pinesol_green dbwells: Error: malone bug 2 not found
15:33 dbwells Given the very small number of commits since 2.6.2, do we need a maintenance release now, of just wait until the next cycle?
15:34 eeevil +1
15:34 bshum dbwells: +1 to waiting
15:34 dbwells I am happy to do it if anyone needs it done.
15:34 csharp +1
15:35 eeevil only matters if you're on master opensrf, IIRC
15:35 dbwells That was also my understanding, but wanted to verify that as well.
15:35 eeevil that's how it bit me, anyway :)
15:36 Dyrcona And the two of us that use OpenSRF master should have that fix where necessary. :)
15:36 eeevil but, opensrf 2.4 coming out as a package soon... I guess we'll need a release before that's GA
15:36 kmlussier dbwells: If we wait until the next cycle then, it's an August 20 release date?
15:36 dbwells kmlussier: yes
15:37 kmlussier ok, thanks!
15:37 bshum dbwells++
15:37 eeevil gmcharlt: you expect to bundle opensrf 2.4 before then?
15:37 eeevil August 20, that is
15:37 gmcharlt eeevil: yes
15:38 Dyrcona gmcharlt: Would it be a problem to wait?
15:38 eeevil ah ... well... we'll need to warn folks against using it ("max supported version for evergreen is 2.3"), or cut back branch releases of EG.
15:39 bshum Traditionally, I don't think we've recommended to people to change OpenSRF versions mid-major release for Evergreen.
15:39 bshum Meaning Evergreen 2.6 stays with OpenSRF 2.3
15:39 bshum etc.
15:39 csharp correct
15:39 gmcharlt bshum: I'm not sure we've made definite statements, however
15:39 bshum And when OpenSRF 2.4 is around, we focus that towards Evergreen 2.7
15:39 eeevil bshum: I don't recall a specific recommendation on upper release boundary
15:39 csharp I think we should stick with one opensrf version per release, myself
15:39 bshum It's not explicitedly defined as such and in fact the README would say use the latest all the time I guess...
15:40 eeevil we've certainly had a "requires at least" statement
15:40 bshum But the downloads page doesn't get changed as new OpenSRF comes into being
15:40 eeevil and the install docs usually say "install the latest"
15:40 bshum So Evergreen 2.5 still points at OpenSRF 2.2
15:40 bshum While 2.6 points at 2.3
15:40 gmcharlt as minimum required version
15:40 bshum So it's sort of implied, but we all know what happens when we assume
15:40 dMiller_ joined #evergreen
15:40 csharp barring a security concern, I wouldn't upgrade OpenSRF without also upgrading EG
15:41 eeevil gmcharlt: right ... that doesn't imply a max to me, but a min
15:41 eeevil csharp: sure, but we're talking about new downloads
15:41 bshum Well I always read it as "use this exact version of OpenSRF with Evergreen, because beyond here lies dragons" but I guess we all read them differently.
15:41 gmcharlt circling back to "no definite statement has been made"
15:42 kmlussier So it sounds like our options are to either to do an earlier point release for 2.6 or explicitly stating that people shouldn't use OpenSRF 2.4 until they are on 2.7.
15:42 csharp eeevil: I think for troubleshooting purposes, we should have a consistent stack... do you disagree with that?
15:42 eeevil kmlussier: well, an on-time release ;)
15:42 gmcharlt bshum: remind me - when would you like to cut the 2.7 beta?
15:42 eeevil csharp: sure. but new users will grab the latest of each to try it out
15:42 kmlussier eeevil: Yes, an on-time release. :)
15:42 bshum gmcharlt: That's something I wanted to have some debate on actually.
15:43 bshum The scheduled date for 2.7.0 beta freeze and presumably soon thereafter cutting is next Thursday, August 7
15:43 csharp so we're talking about for testing purposes? or for general usage?
15:43 dbwells I can be flexible if we want to coordinate OpenSRF 2.4, 2.7-beta, 2.6.3, and 2.5.7 to all roughly coincide for dependency reasons.
15:43 eeevil dbwells: looks like we there's no rest for the wicked this month ;)
15:43 gmcharlt well, we can sequence things like this: opensrf 2.4 alpha => EG 2.6 beta => EG 2.5/2.6 pint releases => opensrf 2.4.0
15:43 eeevil dbwells++
15:44 bshum If we push it back too far, then I'd be concerned about slippage of dates and getting 2.7.0 released for September.
15:44 eeevil (s/2.6 beta/2.7 beta)
15:44 bshum And I was hoping for an on-time delivery.  :)
15:44 gmcharlt unless I'm missing something with the sequencing... sounds doable
15:45 eeevil gmcharlt: yeah, that seems fine. specific dates don't matter then
15:45 hopkinsju_ Based on the documentation I would think that setting 'Show evening_phone field on patron registration' true would show the field on the patron self registration form. This doesn't seem to be the case. Am I missing something?
15:46 gmcharlt hopkinsju: would you mind holding that question till after the meeting finishe?
15:46 * hopkinsju apologizes for the interruption
15:46 gmcharlt no worries
15:46 kmlussier So if we go with that sequencing, do we need to specify a date range as to when all this happens?
15:46 bshum Hang on, dates are important (just trying to keep things straight).  gmcharlt, are you saying that you think we can get OpenSRF 2.4 alpha out before the August 7 date for Evergreen 2.7 beta?
15:46 gmcharlt eeevil: dbwells: bshum: then it sounds like an OpenSRF 2.4.0 by the end of August would be fine for EG 2.7.0
15:46 bshum And then after that, we line things up for the next round of maintenance releases
15:46 bshum etc.
15:47 gmcharlt bshum: yes - "#action gmcharlt to cut alpha of OpenSRF the middle of next week (week of Aug. 4th)"
15:48 bshum Okay, cool.
15:48 kmlussier And then we have beta on the 7th and then 2.5 and 2.6 point releases, we're still looking at Aug. 20?
15:48 bshum That sounds reasonable.
15:48 bshum The next date for 2.7 after beta is the RC date, which is Sept 4
15:49 dbwells I'd like to plan the point releases for Aug. 7 as well, if nobody minds.
15:49 bshum So that gives us time to do tests, etc. with the new OpenSRF
15:50 kmlussier #agree next round of point releases will be scheduled for August 7
15:50 kmlussier Anything else before we move on?
15:50 bshum Just an info
15:50 gmcharlt er, that would be point releases for August 20, no?
15:50 bshum Nope, nothing, sorry.  I got all my questions answered now.
15:51 bshum Just had to read back upward
15:51 kmlussier gmcharlt: dbwells just said he would like to plan for August 7
15:51 gmcharlt ah, sorry
15:51 kmlussier #topic Evergreen 2.7 release
15:51 kmlussier bshum, you've got the floor
15:52 bshum Well, I learned how to use the make_release script tools
15:52 bshum And the first alpha tarball is up on the downloads page now.
15:52 kmlussier bshum++
15:52 bshum mceraso is actually testing the alpha tarball for me right now, but if anyone else has good or bad things to say about it, please let me know.
15:53 bshum #info 2.7.0 alpha1 was cut and available from downloads page on Evergreen website
15:53 bshum #info 2.7.0 beta1 cutoff date is August 7, 2014 (next Thursday)
15:53 kmlussier Any questions for bshum before we move on?
15:54 bshum Speaking on the beta deadline, if there's any specific things that people are working on that they really want in 2.7, this is the time to get action on LP for them.
15:54 kmlussier bshum: What kind of action?
15:54 bshum kmlussier: At a minimum, either targeting towards 2.next with pullrequest, etc.
15:55 ldw bshum: I have updated LP1084269
15:55 kmlussier Is there a deadline on when the pullrequest tag needs to be added to make the beta cutoff?
15:55 ldw I need to target it for 2.next, but I can do that before the 7th
15:55 bshum That's a good question.
15:55 bshum The beta cutoff is actually supposed to be review too
15:55 bshum Meaning we have to actually push those things to master for them to be included.
15:55 bshum So it's not just mark them for review (which should be done as soon as possible)
15:56 bshum But also a general call for getting review and edits done to work so that new features are included.
15:57 bshum I've been saying it in IRC and I think I mentioned it in the last email, but perhaps I should write a more dedicated, "HEY PUSH THINGS" email to developers so that we can get as much work done as possible.
15:57 vlewis tsbere Thanks
15:57 Dyrcona Well, that brings up something that I thought of earlier today: lp1347774.
15:58 kmlussier I have some code I plan to test over the next week, but I don't have the power to push, just sign off. I don't know if that helps expedite the process.
15:58 bshum Given our general reliance on a week's time to review new features before push, perhaps the cutoff for new LP pullrequest targets ought to be this Thursday, July 31
15:58 kmlussier https://bugs.launchpad.net/evergreen/+bug/1347774
15:58 pinesol_green Launchpad bug 1347774 in Evergreen "Backend logic has leaked into the TPAC (and friends)" (affected: 2, heat: 12) [Wishlist,New]
15:58 bshum That way we get one week to review and then push in by August 7 beta date.
15:59 Dyrcona kmlussier: Thanks, my pinesol-foo is weak. :)
15:59 kmlussier Does the July 31 date sound agreeable to everyone?
15:59 bshum I imagine we'll do more triage and fixing for anything that gets rattled in the time between beta and RC.
15:59 berick kmlussier: sign off's do help speed things up
15:59 Dyrcona Is the goal to get those changes into 2.7.0, and do we think that is possible?
16:00 kmlussier eeevil ^ ^
16:00 * eeevil reads up
16:00 eeevil sorry, got distracted
16:01 Dyrcona Basically, should using backend logic used in TPAC stop something new from going into 2.7?
16:02 eeevil yeah, if we can get that in, it would be really great. I have a first-cut of the anon-pcrud service I'll post
16:02 eeevil Dyrcona: do you have a new feature in mind that wants to do that?
16:03 eeevil (many probably do want to. this has been one of the blockers in the past -- "there's precedent!" -- but it's bad precedent :( )
16:03 Dyrcona eeevil: It's more of a radical bug fix that had a pull request since early June until this morning: lp 1208875
16:03 eeevil blockers to attacking this problem, I mean
16:03 pinesol_green Launchpad bug 1208875 in Evergreen "OPAC: My Account: Download Checkout History CSV breaks when there are a large number of items in the history" (affected: 5, heat: 26) [Medium,Confirmed] https://launchpad.net/bugs/1208875
16:04 Dyrcona Well, I like using CStoreEditor, for one thing. :)
16:04 bshum It was on my list of things to test and include for alpha but I missed my own deadline that week, fwiw.
16:04 eeevil Dyrcona: that's totally fair. if I can adjust that to fit, would that be a fair compromise?
16:04 eeevil Dyrcona: you'll get to keep using cstore editor
16:05 eeevil that's a big part of the plan
16:05 Dyrcona eeevil: Sure, but I'm willing to rework it if necessary.
16:05 eeevil (minus json_query)
16:05 Dyrcona OK. I'll keep an eye out for branches.
16:06 kmlussier #info any new features for 2.7 should have a pullrequest tag by July 31.
16:06 kmlussier #help We need volunteers to test and push code for 2.7
16:06 jeff eeevil: are you saying you'll adjust the code for bug 1208875 to work under the new reality of bug 1347774?
16:06 pinesol_green Launchpad bug 1208875 in Evergreen "OPAC: My Account: Download Checkout History CSV breaks when there are a large number of items in the history" (affected: 5, heat: 26) [Medium,Confirmed] https://launchpad.net/bugs/1208875
16:06 pinesol_green Launchpad bug 1347774 in Evergreen "Backend logic has leaked into the TPAC (and friends)" (affected: 2, heat: 12) [Wishlist,New] https://launchpad.net/bugs/1347774
16:07 jeff eeevil: or something else -- just trying to see if i understood
16:07 * Dyrcona is fine with doing the adjusting. He just needs something to work with. :)
16:07 berick Dyrcona: basically json_query, update, delete, create, and any retrieve/search calls on non-public data have to move into an API call somewhere
16:08 eeevil jeff: I think it's fair of Dyrcona to say that his code's been their waiting, and if I want to disrupt it, I should help fix it (I'm putting words in his mouth...)
16:08 kmlussier Do we have anything else for the 2.7 release?
16:08 eeevil Dyrcona: what berick said ... you shouldn't need new code, just move existing private-assuming code.
16:08 jeff eeevil: got it. thanks!
16:09 kmlussier It's already past the hour mark and we have 2 agenda items. Do we want to push on or move the discussion of the last two items to the list?
16:09 kmlussier One has already been started on the list.
16:09 eeevil kmlussier: I'll hush. sorrry
16:10 kmlussier Hearing no opinions, I'm just going to press on. :)
16:10 kmlussier topic: Bug Squashing Days
16:10 kmlussier #link http://markmail.org/message/i52gh26swaewnqzo
16:10 jeff +1 to bug squashing days
16:10 kmlussier Bah!
16:10 kmlussier #topic Bug Squashing Days
16:11 kmlussier I have nothing to add to the e-mail. I just want to know if the dev community is okay with me moving forward to schedule a Bug Squashing Day.
16:11 csharp +1
16:11 eeevil it's worth a try, and the earlier we know about it the more likely we can clear our plates for the day
16:11 kmlussier Also, would anyone be interested in volunteering to do one of the extras I listed in the e-mail (setting up a scoreboard and maybe even a Sandbox)?
16:12 kmlussier eeevil: I was thinking of shooting for the end of August to give us some time to plan.
16:12 jeff I'd be interested in hearing from those with more Koha community experience to know if there are challenges we should look out for, or areas where Evergreen lacks some infrastructure (like sandboxes?) that would present a unique challenge.
16:13 kmlussier gmcharlt: Do you have any insights to offer?
16:13 gmcharlt the lack of sandboxes is a problem
16:13 yboston kmlussier: I would like to help one way or another. One way I would like to help is put together a tutorial to gelp first time voluneteers, like creating tips for installing EG through Git
16:13 gmcharlt at least with respect to including as many people as possible who can test but who aren't necessarily in a position to apply particular fixes
16:14 hopkinsju MOBIUS could provide one or more sandboxes, gmcharlt
16:14 gmcharlt a possible mitigation would be to arrange for folks to claim bugs before the big day
16:14 gmcharlt and set up environments before hand
16:14 jeff Koha's sandboxes are quite automated from what I understand -- we might be able to replicate with a "please create a sandbox with the branch for this bug" and some manual work before the day-of?
16:15 jeff gmcharlt++ (jinx?)
16:15 gmcharlt hopkinsju: one thing to note: the sandboxes that Koha has, which are operated (mostly) by BibLibre, provide an interface for a user to specify a bug number, then a few minutes later get a running Koha instance with the patches for that bug applied
16:15 kmlussier It seems like the Koha sandboxes are fairly automated. I was trying to think through how patches could be added on an Evergreen sandbox, and it seemed like it would need to be a little more manual. (jeff beat me to it.)
16:15 gmcharlt jeff: yep, sounds like the two of use are on the same page
16:15 gmcharlt MIND MELD!
16:16 * Dyrcona has automated most of that for his nearly daily VM builds.
16:16 hopkinsju Thats awfully fancy.
16:16 kmlussier Also, would we need more than one sandbox.
16:16 kmlussier It seems like branches might conflict if everything happened on one?
16:16 gmcharlt yep, multiples would help
16:16 jeff kmlussier: one per bug/branch would be what i was thinking
16:16 gmcharlt so to expand my suggestion... I think lining up volunteers in advance would really help
16:16 gmcharlt both for hosting test envs, and for doing testing
16:17 kmlussier To speed things along, maybe we can move the Sandbox discussion to the dev list to see if we can make this happen.
16:18 kmlussier #action kmlussier to move Sandbox discussion to dev list
16:18 jeff +1
16:19 kmlussier hopkinsju++ #Volunteering a MOBIUS test server
16:19 * kmlussier will move forward with bug squashing plans.
16:19 kmlussier #topic Web client's circulation module preview for Evergreen and websockets for OpenSRF
16:19 kmlussier bshum: Was this your topic?
16:20 bshum kmlussier: Yes, but we covered a lot of it earlier with the websockets talk just now.
16:20 jeff of the three options presented in the agenda, i like the first option best, and i'm almost certain that it is actually what was agreed upon earlier with regard to opensrf alpha scheduling. :-)
16:20 bshum I think the only outstanding part of it is whether berick thinks we'll want to include the web client circ module preview for 2.7 beta
16:21 berick well, we certainly can.. technically.
16:21 berick whether we want to is a broader question
16:21 berick sprint 1 is on schedule to be done toward the end of this week.
16:21 berick It’s tracking Evergreen master, so I’m not expecting any merge conflicts
16:21 berick or other oddities
16:21 jeff if it were included without changes to the 2.7 beta timeline, do you think that it would be a useful representation of the web-based features?
16:22 kmlussier By adding it as a preview, will it make it easier for more people to test?
16:22 berick jeff: yes; kmlussier: i would think yes
16:22 berick Assuming web sockets is merged, there’s one other bit of testing we would need to merge the browser client.
16:23 berick There are a couple of places where existing (non-browser client) code had to be modified for integration (e.g. opac).  Affected areas will need to be tested in the XUL client to make sure nothing was broken.
16:23 berick I could create a list.  There aren’t very many of these.
16:24 berick otherwise, it should go unnoticed for anyone not looking for it
16:24 jeff process-wise, would a lp bug for the circ-bits with notes on pre-reqs (websockets in opensrf) and a list of things to pay attention to when testing (berick's "list" just now) be the way to get it targeted for 2.7 beta in time for thursday?
16:25 kmlussier The possibility of breakage in the existing client makes me a little nervous. On the other hand, I would love to make it available for wider testing.
16:26 berick it occurs to me the build/install process might need some more work, too
16:26 berick it's been a while since I've looked at that
16:27 berick if the requiremetn for 2.7 is basically "don't break anything", then I think this is very doable
16:27 bshum berick: I can work with that.
16:27 kmlussier "don't break anything" is a good goal to have. :)
16:27 bshum I'd like to get it included as a preview as long as it doesn't interfere too much.  Though I am curious to see the list of affected areas now :)
16:28 kmlussier berick: Can I add an action item for you to add a LP bug as jeff described above?
16:28 berick bshum: it's pretty small. shall I start w/ that in a LP like jeff ...
16:28 berick heh
16:28 berick kmlussier: yes you may ;)
16:28 bshum berick: Sure
16:28 tspindler left #evergreen
16:28 bshum Hey, look at it this way, we can always roll back :P
16:28 kmlussier #action berick to add an LP bug for web based circ client with notes on pre-reqs and a list of existing client interfaces that need special attention.
16:29 kmlussier Anything else before we wrap up?
16:30 kmlussier Going once, going twice...
16:30 kmlussier #endmeeting
16:30 pinesol_green Meeting ended Mon Jul 28 16:30:11 2014 US/Eastern.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)
16:30 pinesol_green Minutes:        http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-07-28-15.07.html
16:30 pinesol_green Minutes (text): http://evergreen-ils.org/meetings/evergr​een/2014/evergreen.2014-07-28-15.07.txt
16:30 pinesol_green Log:            http://evergreen-ils.org/meetings/evergree​n/2014/evergreen.2014-07-28-15.07.log.html
16:30 bshum kmlussier++ # wrangling
16:30 jeff kmlussier++
16:30 kmlussier Sorry for going long today. You all were so chatty! :)
16:30 DPearl kmlussier++
16:31 dbwells kmlussier++
16:31 yboston kmlussier++
16:31 gmcharlt kmlussier++
16:31 Dyrcona kmlussier++
16:32 dbs kmlussier++
16:32 eeevil kmlussier++
16:33 eeevil Dyrcona: looking at the CSV code, I'd probably just move the _get* helper methods to O::A::Circ and call the front-line one
16:43 eeevil and, having fixed some typos, working/collab/miker/lp-1347774-anon_pcrud_mode compiles! :)
16:54 mtcarlson joined #evergreen
16:54 Dyrcona eeevil: Cool.
16:55 * Dyrcona was AFK.
17:00 pinesol_green Incoming from qatests: Test Success - http://testing.evergreen-ils.org/~live/test.html <http://testing.evergreen-ils.org/~live/test.html>
17:02 mcarlson joined #evergreen
17:10 mmorgan left #evergreen
17:32 jeff Firefox can't find the server at git.evergreen-.
17:32 jeff right.
17:33 * jeff shakes his fist at bug 28649
17:33 pinesol_green Launchpad bug 28649 in Launchpad itself "mail word wrapping breaks urls and other words" (affected: 12, heat: 102) [Low,Triaged] https://launchpad.net/bugs/28649
18:38 jeffdavis Have the dates for the hackaway been finalized?
18:57 bshum jeffdavis: Might be good to email the list for verification, but I haven't seen any mentions of other dates.
19:00 mtcarlson joined #evergreen
22:35 tsbere_ joined #evergreen

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