15:00:43 #startmeeting 2015-09-02 - Developer Meeting 15:00:43 Meeting started Wed Sep 2 15:00:43 2015 US/Eastern. The chair is Dyrcona. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:00:43 The meeting name has been set to '2015_09_02___developer_meeting' 15:01:10 #info agenda at http://evergreen-ils.org/dokuwiki/doku.php?id=dev:meetings:2015-09-02 15:01:28 #topic Introductions 15:01:44 #info Dyrcona = Jason Stephenson, MVLC 15:01:51 #info gmcharlt = Galen Charlton, ESI 15:02:30 #info Stompro = Josh Stompro, LARL MN 15:02:30 #info berick = Bill Erickson, KCLS 15:02:52 #info dbwells = Dan Wells, Hekman Library (Calvin College) 15:03:23 #info isl-jasonb = Jason Boyer, IN State Lib (Eg IN) 15:03:34 (oops.) 15:03:42 heh 15:04:03 #info dbs = Dan Scott, Laurentian University 15:04:16 @info jeff = Jeff Godin, Traverse Area District Library (TADL) 15:04:17 jeff: (info ) -- Returns information from the given RSS feed, namely the title, URL, description, and last update date, if available. 15:04:21 bah. 15:04:25 #info remingtron = Remington Steed, Hekman Library (Calvin College) 15:04:29 #info jeff = Jeff Godin, Traverse Area District Library (TADL) 15:05:02 Stragglers can announce themselves as they show up. 15:05:17 #top Action Items from Last Meeting 15:05:22 oops. 15:05:37 #topic Action Items from Last Meeting 15:06:04 #info gmcharlt to organize webstaff client hacking day in September 15:06:07 #info yboston is Yamil Suarez - Berklee.edu 15:06:22 #info We've now picked a date: Wednesday, 16 September 2015. Will discuss at dev meeting. 15:06:34 gmcharlt, you have the floor. :) 15:07:08 so, main thing to discuss before we officially announce it is mostly scheduling: does that day happen to be no good very bad not free at all for everybody who isn't me and miker? 15:07:12 if not, we'll run with it 15:07:57 works for me 15:07:58 looks good here. 15:08:07 * dbs isn't free at all but realistically that doesn't matter 15:08:26 looks like 2.9.0 and monthly maintenance releases are scheduled for that day. 15:08:27 It is release day for 2.9.0, 2.8.4, and 2.7.[i forget] 15:08:53 i would not object to pushing releases ahead or back a day 15:08:54 #info miker = Mike Rylander, ESI 15:09:13 I cannot release on the 15th. 15:09:35 how about the 17th for AngularJS day? 15:10:08 also works for me 15:10:18 Day after a release might be better than a day before. 15:10:48 17th also good for me. EOB meeting for one hour that day, if that affects anyone else with interest. 15:11:49 17th works for me. 15:12:01 * gmcharlt imagines that the EOB meeting si less of a blocker for anybody who falls in the intersection 15:12:25 17th works better for me also. 15:13:30 ok, I think that settles it 15:13:33 thanks for the feedback! 15:13:43 #info AngularJS Day will be scheduled for 17 September 2015 15:13:49 beat me to it. 15:14:11 #info ldw will follow up with jeff about removing old self check interface status -- Done! 15:14:24 I put that as done, since the code branch went in. 15:14:33 Any discussion before moving on? 15:14:41 nope! 15:14:56 ok, then. 15:15:04 #info ldw will follow up with jeff about removing old JSPAC code status - Done! 15:15:13 Same with this one. 15:15:19 yay! 15:15:43 #info ldw will follow up with jeff on merge vs cherry-pick discussion 15:15:59 I don't think this one happened, jeff? 15:17:45 #info Bmagic = Blake GH, MOBIUS 15:17:49 #info ldw = Liam Whalen, Sitka 15:17:49 Does anyone want to have any discussion on the matter before I defer it to next meeting? 15:17:52 nope, though ldw did say he wanted to ask me about something. 15:18:17 jeff: I wanted to make sure all was well. Just a follow up to the TODO. 15:18:36 my report would be that i've given it some but not a lot of thought, enough to be reconsidering and i have no specific proposal to make at this time. i'd be interested in further (not in this meeting) discussion with anyone else who was interested by the original idea. 15:18:38 Is it something we would want to discuss at a future meeting, or should we drop it? 15:18:56 no specific followup other than that. drop it from the next agenda unless further discussion brings it back to the agenda. 15:19:26 #agree drop it for now. :) 15:19:49 #info ldw will looking into integrating neg. balance tests on test writing day 15:20:12 ldw: I think that happened more or less. 15:20:49 I did not get the neg balance tests personally. I do not know if someone else worked on it that day. 15:21:09 #info kmlussier is Kathy Lussier, MassLNC 15:21:16 There are some negative balance tests and more can always be added. 15:21:28 dbwells or remingtron anything to add? 15:22:29 I think the goal was to reconsider the way they were setup, but that doesn't need to happen with any particular urgency. 15:23:03 So, we'll call that one done, too. 15:23:07 #info done 15:23:25 #info berick will work with bshum on crafting more information about release maintaining and schedules 15:23:41 no progress to report. 15:24:00 Do we want to carry this one forward to the next meeting? 15:24:27 unless bshum still plans on tackling it, let's take it off the agenda for now 15:24:57 Ok. 15:25:18 I don't think bshum is here. He said something about another commitment. 15:26:00 #info gmcharlt will cut an OpenSRF release in the next 6 weeks-- Will cut on Tuesday, 2015-09-08 15:26:19 That looks good to me. Anything to add? 15:27:03 not from me 15:27:19 Ok. moving on. 15:27:23 #info kmlussier to update setting descriptions and then update the release notes to reflect consensus -- Done! 15:28:11 Don't think there is much to add there, so moving on.... 15:28:16 #info Dyrcona to investigate sprint2's integration with an alpha release -- Done: Sprint 2 was integrated for the beta release. 15:28:33 sprint2++ Dyrcona++ 15:28:42 Only thing I can add here is that the tarball install of the web staff client is broken in the beta. 15:28:56 You have to do the developer steps to make it work. 15:29:30 Which maybe leads to an action item for someone (me) to update the README with web staff client instructions. 15:30:35 #action Dyrcona to update README/INSTALL for master to include web staff client installation instructions for developers by 2.9.0 release date. 15:30:49 unless anyone objects. 15:31:42 The next item looks like the previous but touches on the alpha release schedule. 15:32:00 #info Dyrcona to determine if sprint2 can be merged into an alpha release, and will set a date for a release or skip the release depending on his findings. 15:32:22 #info Done: alpha release was skipped and beta was released on time. 15:32:46 Any questions or discussion of that decision? 15:33:51 Ok. It's pretty easy when most of the things get done. :) 15:34:20 #info dbwells will attempt to explode berick's Password Managment and Authentication improvements 15:35:02 I've started going over it, but nothing substantial to report at this time. I'll continue working on it. 15:35:31 dbwells++ 15:35:37 OK. Does this need to continue as an action item? 15:35:48 Indeed. dbwells++ berick++ 15:36:04 Dyrcona: I'd be fine with that. 15:36:21 All right. 15:36:26 #action dbwells will attempt to explode berick's Password Managment and Authentication improvements 15:36:43 Gee I could have fixed the spelling.... anyway. 15:36:57 So that is it for action items. 15:37:09 Moving on to release information. 15:37:20 #topic OpenSRF Release 15:37:50 pretty much already dicussed, I think 15:37:54 gmcharlt mentioned doing a release on 8 Sept. what version will that be? 15:38:12 gmcharlt: do you want an action item? :) 15:38:26 yeah, I'll take it.. and version will be 2.4.2 15:38:30 ok. 15:38:53 #action gmcharlt to release OpenSRF version 2.4.2 on 8 September 2015. 15:39:24 #topic Evergreen Release(s) 15:39:38 So, I'll take an action item right off the bat. 15:39:51 #action Dyrcona to release 2.9-rc after the meeting. 15:40:15 I just made the tarball this afternoon, loaded it on a test vm with concerto data, and all looks good. 15:40:38 I even got it to work with the web staff client. I think that ended up being bad ownership on a directory. 15:41:53 So, do we want action items for the maintenance releases in two weeks or is that overkill? 15:42:29 I guess that would include 2.9.0 as well. 15:44:10 since they're monthly, i don't see any need for an agenda item 15:44:42 though i don't think anyone would complain :) 15:45:46 I'm inclined to agree that they aren't needed, plus they're on the calendar. 15:46:40 Hmm. I kind botched the topic for the next item in the agenda, and I got my answers already. 15:47:20 Unless anyone has anything else to discuss/ask about Evergreen releases, we'll move on... 15:48:16 #topic Translations: Should we include metadata changes or not? 15:48:26 This is new business. 15:48:44 I added this to the agenda before I really understood the process. 15:49:06 I am pretty sure that I've had my questions answered on this topic. 15:49:48 Does anyone have any questions about translations? 15:51:11 Other than how do they work? No. ;) 15:51:19 :) 15:51:45 Well, I might have messed some up at the beta because I tried adding everything at once instead of in two steps. 15:52:07 Since dbwells updated that part of the 2.8 release instructions, things became clearer to me. 15:53:01 Since I'm just babbling... 15:53:07 #topic New Business 15:54:50 And, my server picks now to go nuts..... 15:55:06 Anyone feel railroaded by how I'm conducting the meeting? 15:55:14 servergonuts++ 15:56:48 No. (That I don’t have much input on any of the current topics is unrelated to running a tight meeting) 15:57:30 Does anyone have anything to discuss? 16:00:04 Just wanted to mention that I am behind schedule in scheduling a Bug Squashing Day. I usually try to schedule one between beta and full release, but I don't think that's happening 16:01:59 Ok. I'll adjourn the meeting hearing nothing else. 16:02:03 #endmeeting