Status of reported bugs
Bill Erickson (berick) will deal with the reported ACQ bugs in the near future. He mentioned that some of the bugs were, probably, already fixed in post-1.6 (trunk). ACQ in 1.6 is not meant to be production ready, we're still collecting bug reports, suggestions, etc. Most ACQ features are/will be ported to rel_1_6 and anything that is critically broken will also be backport to rel_1_6_0.
Authority record import. [ http://markmail.org/message/fu7lvbft5ku3grip ]
This issue has been addressed, dbs/berick will test on rel_1_6_0_0-as-of-today and will confirm that it's fixed (or not).
Importing MFHD monographic holdings records separate from bibliographic records.
This is a post-1.6.0.0 feature request and should be filed as such.
This bug was deemed low priority since you almost have to be trying to break things to encounter the issue. Galen Charlton (gmcharlt) will be given ownership of the bug since he did mention that he might try his hand at a fix.
Warren Layton (wlayton) submitted a patch, which was applied but it wasn't a complete fix since addresses aren't hooked up. Warren volunteered to fix it this weekend and requested other's have a look/test it also.
It was suggested/decided that whoever works on a ticket should notify the list, about having taken ownership of the bug and followup once it is resolved (or not), a link to the pertinent bug+commit would also be a good idea in the mail.
Translations/RC2/1.6.0.0
We will not have a RC2 release even though there have had a number of changes since RC1. Any remaining bugs will be addressed by 1.6.0.1. Mike Rylander (miker_) will build the tarball and have a look through the release notes, upgrade notes, etc. He requested that we look through the release notes and confirm all fixes, updates, etc are included. [http://evergreen-ils.org/dokuwiki/doku.php?id=release_notes_1_6_0_0_rc1 ] Jason Etheridge (phasefx_) mentioned that there are two things he'd like to/will backport to 1.6.0.0 * a more relaxed "key" for oils_persist so that sticky settings will survive upgrades * a bug with fleshing un-rendered list rows when they're scrolled into visibility) As mentioned earlier, most ACQ features are/will be ported to rel_1_6 and anything that is critically broken will also be backport to rel_1_6_0.
OpenSRF we need to cut an OpenSRF release to match Evergreen 1.6 (but wait… shouldn't that be tested first? OH NOES!)
Dan Scott has volunteered to test Warren Layton's patch that enables bookbags to be exported to Refworks. It will probably be shepherded into the first feature release after 1.6.0.0, say 1.6.1.0 & will also be added to branch_1_6. Note: We might take advantage of this patch to push the bookbag from Evergreen to Syrup in the future.
Note: Jeff mentioned (later) that he had quite a few of miker's "here's the deal with FOO" emails filed away for reference, which might be a good thing to use for the technical documentation pages. Note: natschil mentioned the document "How to participate in development" but that it is often quite broad, maybe it should be revised or replaced. [ http://evergreen-ils.org/documentation/contributing.html ]
Yes, Shawn Boyette (sboyette) will put out a call for a QA team: bug testers & wranglers. He has also volunteered to be "bug tracker oversight guy" since he is current "the QA guy" at ESI so has been concentrating on the test suite and will also be working on tools to support the development process in general. Dan Scott agreed that there's a natural relationship between converting bug reports & fixes into tests. Also noted that there could always be more than one person tracking the bugs. So Shawn would be point person for the wranglers (at least for now).
Yes. After much discussion it was decided that we will try out Launchpad and see how it works out. Or as Dan put it "For a trial period of three months, try out Launchpad as the writable-by-anyone bug system/translations system/feature request/code review/FAQ-development thingy" etc.
Dan has requested a transfer of the inactive launchpad.net/evergreen and is confident it will happen based on precedent. [ https://answers.edge.launchpad.net/launchpad/+question/85776 ]
Note: David Fiander (djfiander) talked about handing out bug-filing privileges like candy would work, sort of: once you've reported a problem via email/irc that's real, then you get to file your own. which was received well but we need to see how we will end up using Launchpad.
Shawn Boyette has been working on a buildbot which is nearing completion of its first phase of development. It will get its own box and will be public (both output and source) towards the end of the month. The goal is to have it not just acting as a continuous integration server but to also use it to build anything that uses a GNU toolchain. The eg-specific parts exist sort of on the side -- like the tarball building part will be using the buildbot's libraries to introspect the bot's db. So this pretty much takes care of the automated build section, although Shawn could always use more eyes once it's ready and rolling. It will probably be made available under ils-contrib or "a git repository, somewhere" we will have a better picture towards the end of the month. Note: Dan asked if parts of the system that are not currently part of the GNU toolchain will need to either be added to it, or made available in some form of pre-built output? For example the openils_dojo layer, translations, etc. Not sure if that got answered.
As of now we have a somewhat working ACQ in 1.6.0.0 but it is regarded as a preview release, so no bugs in ACQ in 1.6.0.0 are considered showstoppers. Bug fixes get added to rel_1_6_0, any new features will be included in rel_1_6 and above.
Or as the release notes say:
Acquisitions Preview includes a sneak peek at the preliminary work for manual funding management, PO creation, cataloging and receiving processes. These are functional but are not intended for insertion into current workflows. This feature was specifically included to solicit feedback from the community on this important feature.
It was regarding a document, Karen Schneider (kgs) had sent to him a while ago with a long list of bugs in craftsman which need to be entered as actual bugs into Trac. He wasn't sure if this list was ok to release to public or not because Karen hadn't posted it anywhere. Mike Rylander saw no reason with getting the list of problems out on to bug tracking.
Since the meeting was extending to 2.5 hours it was decided to defer oils_i18n_gettext & scheduling the next IRC meeting to the lists.
What's shaking in the near future? & Any long term projects that we need to start laying the groundwork for now? were also tabled to the list and/or will be included into the next meeting's agenda.