According to the schedule, module releases will start from the next sprint. I assume we will resolve this issue till the that time, so yes, please postpone releasing module.

That is true. Thank you for confirming what folks want me to do. I will hold off releasing mod-inventory until this issue is resolved.

I wanted to understand the situation better and check what folks wanted me to do because the timing of this change surprised me (given it's after the development freeze) and I tend to want to start releasing modules as early as they tend to be at the root of some deep dependency chains in the system and so can delay other module releases.

Hi . According to the schedule, module releases will start from the next sprint. I assume we will resolve this issue till the that time, so yes, please postpone releasing module.

OCLC single import is broken (mod-copy-cat) because we added a new type for importing MARC authority records. This issue was caught on Friday. Our development had no extended development just that we missed this update to OCLC single import (mod-copy-cat).

Thanks for the extra context.

My understanding of what you said is: `a unrecognised breaking compatibility change was introduced during the MARC authority record word, this only became apparent on Friday. This work is to resolve this and needs to happen, irrespective of the development freeze`

How far off am I?

As the lead maintainer, what do I need to do, do I need to hold off releasing mod-inventory until this situation is resolved?

, OCLC single import is broken (mod-copy-cat) because we added a new type for importing MARC authority records. This issue was caught on Friday. Our development had no extended development just that we missed this update to OCLC single import (mod-copy-cat).

, ,

Please can any of you help me understand why we are making compatibility breaking changes after the development freeze for these modules?

Is it that there a critical feature that has extended development into that period (and hence, the initial release of the module needs to wait till after this work has been done)?

cc: