<div dir="ltr">We upgrade yearly at KCLS and generally stay about two releases behind. We'll upgrade to 3.14 this Fall, for example.<div><br></div><div>We also deploy patches throughout the year for fixes and features developed internally or from the community.</div><div><br></div><div>This cadence has served us well for a while.</div><div><br></div><div>-b</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Fri, Feb 21, 2025 at 1:52 PM Murphy, Benjamin via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org">evergreen-general@list.evergreen-ils.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class="msg699243583652466622">
<div dir="ltr">
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
Our consortium upgrades annually in the fall and we typically skip a version (3.11.3 to 3.13.5 for instance.) We usually install the target version on a test machine in early summer and then invite staff in consortium libraries to kick the tires over the summer
so we can make/seek patches to issues and prepare solid training of what to expect. We have a mailing list (Basecamp group) targeted specifically to testing that we invite people to join and discuss issues they encounter. (Let me add a plug for the session
at the upcoming conference about Collaborative Testing. This is something we're trying to wrap our heads around and I'm interested to hear what they have to say.) After testing over the summer, we then have webinars for the larger community to discuss and
prepare for upgrade changes. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="text-align:left;text-indent:0px;margin:0px;font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
We have our upgrade documentation here: <a href="https://nccardinalsupport.org/index.php?pg=kb.book&id=10" id="m_2698867447675477078OWA07f02116-eefd-10ab-721f-78aedd211a79" style="margin:0px" target="_blank">
https://nccardinalsupport.org/index.php?pg=kb.book&id=10</a> including our working list of known but unresolved bugs. </div>
<div style="text-align:left;text-indent:0px;margin:0px;font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
This past year we were chasing the latest version which I don't think we're going to do again. We weren't able to test the Reporter changes in 3.13, so we got hit with a lot of tickets for bugs once it went live. Some of them we were able to chase fixes for,
some we had to just report on Launchpad and hope someone took them on. This is frustrating for our users, so we're thinking about being more conservative about upgrading to the latest version. That's one of the challenges of an open source project, if you're
on the cutting edge, find a bug and don't have the resources to fix it yourself, you might be stuck with the problem for a while. Your user base doesn't always understand that. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
"Do you just load bug fixes as you need them?" We did one "mini-upgrade" in spring a few years back, but generally we have to be offline for ~36-48 hours for an upgrade, deal with training and all the other logistics so we usually just stick to once a year.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
"is there any frustration among your libraries about delays in getting new features?" We've heard some excitement about new features for member library staff that are plugged into the larger Evergreen community, but we hear more frustration when new things
don't work.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
After our most recent upgrade, we decided as a team that we're going to treat our upgrades more like a new library migration, where we're all focused on some aspect of the upgrade for a period of time and try to be more deliberate about testing, user engagement,
etc. </div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
I'm interested to hear what other folks have to say on the topic.</div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<div id="m_2698867447675477078Signature">
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black"><b>Benjamin Murphy</b></span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black">NC Cardinal Program Manager</span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black">State Library of North Carolina</span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:rgb(5,99,193)"><u><a href="mailto:benjamin.murphy@dncr.nc.gov" target="_blank">benjamin.murphy@dncr.nc.gov</a>
</u></span><span style="font-family:Arial,sans-serif;font-size:10pt;color:black"> |
<a href="https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal" id="m_2698867447675477078OWA808305d1-4c2c-d926-cb02-ec732df032a0" style="margin:0px" target="_blank">
https://statelibrary.ncdcr.gov/services-libraries/nc-cardinal</a></span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black">109 East Jones Street | 4640 Mail Service Center </span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black">Raleigh, North Carolina 27699-4600</span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255);margin-top:6pt">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:rgb(0,0,0)">The State Library is part of the NC Department of Natural & Cultural Resources.</span></p>
<p style="text-align:left;text-indent:0px;background-color:rgb(255,255,255)">
<span style="font-family:Arial,sans-serif;font-size:10pt;color:black"><i>Email correspondence to and from this address is subject to the North Carolina Public Records Law and may be disclosed to third parties.</i></span></p>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
</div>
<div id="m_2698867447675477078appendonsend"></div>
<div style="font-family:Aptos,Aptos_EmbeddedFont,Aptos_MSFontService,Calibri,Helvetica,sans-serif;font-size:11pt;color:rgb(0,0,0)">
<br>
</div>
<hr style="display:inline-block;width:98%">
<div dir="ltr" id="m_2698867447675477078divRplyFwdMsg"><span style="font-family:Calibri,sans-serif;font-size:11pt;color:rgb(0,0,0)"><b>From:</b> Evergreen-general <<a href="mailto:evergreen-general-bounces@list.evergreen-ils.org" target="_blank">evergreen-general-bounces@list.evergreen-ils.org</a>> on behalf of Lussier, Kathy via Evergreen-general <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>><br>
<b>Sent:</b> Friday, February 21, 2025 11:48 AM<br>
<b>To:</b> Evergreen Discussion Group <<a href="mailto:evergreen-general@list.evergreen-ils.org" target="_blank">evergreen-general@list.evergreen-ils.org</a>><br>
<b>Cc:</b> Lussier, Kathy <<a href="mailto:klussier@noblenet.org" target="_blank">klussier@noblenet.org</a>><br>
<b>Subject:</b> [External] [Evergreen-general] Tell us about your upgrade schedules!</span>
<div> </div>
</div>
<div style="text-align:left;line-height:12pt;background-color:rgb(255,235,156);padding:2pt;border-width:1pt;border-style:solid;border-color:rgb(156,101,0);font-family:Calibri;font-size:10pt">
<span style="color:rgb(255,0,0)"><b>CAUTION:</b></span><span style="color:black"> External email. Do not click links or open attachments unless verified. Report suspicious emails with the Report Message button located on your Outlook menu bar on the Home
tab.</span></div>
<br>
<div style="direction:ltr">Hi all and Happy Friday!</div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr">NOBLE is reevaluating its upgrade schedule and would like to hear how other libraries / consortia handle their upgrades. Since we moved to Evergreen, we've been on a schedule to do a major release upgrade twice per year, following
the community's schedule of two releases per year, and usually upgrade to the release that's one version behind the latest release. We don't typically do point release upgrades, but will load patches for bug fixes that are important to our libraries. We also
hold off on upgrades in cases where we see bugs that will cause too much of a hardship for our libraries. This typically happens when an entire interface is replaced before it supports all of the features used by our libraries.</div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr">We are considering a move to a one-upgrade-per-year schedule. Under this schedule, we would skip a release to ensure we stay on a release that still receives security fixes. </div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr">Tell us about your upgrade schedules.</div>
<ul style="direction:ltr">
<li style="direction:ltr">What is your current upgrade schedule for major releases? Do you typically upgrade one release at a time or do you skip releases?</li><li style="direction:ltr">Do you typically perform point release upgrades in addition to major upgrades? Do you just load bug fixes as you need them? Or do you do both (or neither)?<br>
</li><li style="direction:ltr">Has your upgrade schedule changed over the years that you’ve been on Evergreen? If so, how has it changed and what factors influenced your decision to make those changes?</li><li style="direction:ltr">If your upgrade schedule is annual or even less frequent, is there any frustration among your libraries about delays in getting new features?</li></ul>
<div style="direction:ltr">Feel free to add any information about what you like or dislike about your current schedule.</div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr">Adding a #CatTax in appreciation for your feedback.</div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr"><img alt="PXL_20231003_205444966.jpg" width="349" height="262" size="216593" style="width: 349px; height: 262px; margin-right: 0px;" src="cid:ii_1952a073c1fd126576c1"></div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr">Kathy</div>
<div style="direction:ltr">--</div>
<div style="direction:ltr">Kathy Lussier</div>
<div style="direction:ltr">she/her</div>
<div style="direction:ltr">Executive Director</div>
<div style="direction:ltr">NOBLE: North of Boston Library Exchange</div>
<div style="direction:ltr">Danvers, MA</div>
<div style="direction:ltr">978-777-8844 x201</div>
<div style="direction:ltr"><a href="http://www.noblenet.org/" id="m_2698867447675477078OWAd1fddfa5-9077-aa70-6a7e-8ba9e81e5e1c" target="_blank">www.noblenet.org</a></div>
<div style="direction:ltr"><br>
</div>
<div style="direction:ltr"><br>
</div>
<br>
<hr>
<font face="Arial" color="Gray" size="1"><br>
Email correspondence to and from this address may be subject to the North Carolina Public Records Law and may be disclosed to third parties by an authorized state official.<br>
</font>
</div>
_______________________________________________<br>
Evergreen-general mailing list<br>
<a href="mailto:Evergreen-general@list.evergreen-ils.org" target="_blank">Evergreen-general@list.evergreen-ils.org</a><br>
<a href="http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general" rel="noreferrer" target="_blank">http://list.evergreen-ils.org/cgi-bin/mailman/listinfo/evergreen-general</a><br>
</div></blockquote></div>