Page Comparison

Proposed timing:

Would March 24 be a good start date? (Holly will be out March 19-22 and then would need March 23 to create the "ballot.")  The original thought was that the process would last for 2 weeks, but we could go 3 weeks if necessary. Please keep in mind that that BugFest is March 29-April 9. We could start on April 12, after BugFest, if avoiding BugFest is preferred.

Holly needs to create the spreadsheet.  People prefer 3 weeks for the voting.  People also wanted to wait until after BugFest (since the POs will be so busy).

The voting will be April 12-30.

 Martina S - will the dev teams be named for particular features, to know which features are developed outside of capacity planning - as we agreed that we do not need to spend points on these?

Holly - hard to know in advance

Jacquie - can we know what outside teams are working on so we don't vote for them?  Want a holistic view of what we have pending.

Holly - by April 12 we should know what will be done in Iris and what is planned for Juniper.  You'll be voting on features that haven't been planned for a development cycle yet.  Will indicate the dev team where appropriate.  If there's something not in the ballot you can write it in.  If you find something that doesn't look right or shouldn't be on the ballot let her know.

She will pull the features from those ranked R1 or R2, so institutions still need to rank the JIRA features.

Tod - there's a lot of tickets.  At Chicago will look at what's missing and what they need most.  Or what do they want worked on first.

Holly - maybe only look at your institution's R1s

Bob Scheier - how does BugFest work?

Patty - need to be invited into BugFest channel and added to TestRails by Anton.  Currently have ~9 million records from Chicago as the test database

AMB - Here's the BugFest prep page: Iris (R1 2021) Bugfest environment preparation plan

Receiving workflow demos deferred until Honeysuckle -

Discovery demo - specifically VuFind - for April 6