Steering Committee 201801 Minutes

1. Status of 2.1 release

   • Tommy organized a developer call before the holidays, devs are merging the pull requests identified in the meeting for
   • Will spearhead a follow-up call to wrap everything.

2. Feature freeze proposed for mid-January

   • Yan asked if we can still add any features, consensus was ye if you can find a reviewer

   • Scott asked what needs documentation for 2.1 release. He will attend the dev meeting to get some feedback. Conversation about what needs documentation, user facing features versus install/admin?

   • Scott asked if the pull request that need doc could be tagged. Should we tag them before or after they have been merged? Consensus was that the issue should not be closed until it has documentation.

   • Committee agreed that once feature freeze has happened, it would be great to have a sandbox for testing and documenting new features.

   • We should also create some release notes once we are in beta.

   • Also, we need to be mindful of translations, should those be completed before beta?

   • Note that ER&L is beginning of March, we would like to have 2.1 in GA before ER&L.

3. Survey results

   • Scott reported on the survey results. So far we have 37 responses. First takeaway is that Resources and Organizations modules are most used, no surprise there.

   • Committee agreed to extend the deadline to Friday, January 19th. Heather will send an update, and Carla will post to one or more of the SirsiDynix listservs.

4. Other updates

   • Carla asked about the status of Cal Tech's grant to integrate with GOKb. Heather reported that they are cautiously optimistic, but they have been asked for some additional details.

   • Scott mentioned that the Web Committee continues to migrate data and fine-tune the presentation of content, they hope to have things in order for review by the end of the month, and have it in good shape before ER&L.