Attending
...
- Check out the GitHub Board Review Column
- Consider updating LICENSE to Apache2 #227
- DONE
- Deprecate Solrizer #19
- Is it worth putting out a final call for Solrizer deprecation before next Wednesday's Samvera Tech call, or just let it quietly fade away?
Only 1 response to the e-mail thread giving a qualified thumbs up.
- Is it worth putting out a final call for Solrizer deprecation before next Wednesday's Samvera Tech call, or just let it quietly fade away?
- Consider updating LICENSE to Apache2 #227
- Sprint in a little over a week
...
Product Owners aren't necessarily responsible for ensuring that the code coverage is high enough for a component
Noah:
Agrees with holding the sprint, should we always wait for the Product Owners to identify issues?
Trey:
Product Owners will or will not add the issues, but we may end them early
Mark:
At last Partners' Meeting, ensuring that components adhere to the latest Rails and Ruby releases was quite well received
If this does not consume the entire sprint, that's still sufficient
Should still be used to indicate where the community might need to add more effort
Trey:
Are there Ruby releases coming up which we should be ready for? Rails 6 is still in beta, but will there be a stable release soon?
Created maintenance/issues/20