[NFB-Web] Action Requested: Drupal 11 Upgrade Update

Kevin Pirnie kpirnie77 at gmail.com
Mon Aug 17 13:08:50 UTC 2026


Thank you for the update Erin. August 28 is noted for the date for Idaho's
site to be updated.

Best,
Kevin


On Mon, Aug 17, 2026 at 6:02 AM Rodney, Erin via NFB-Web <nfb-web at nfbnet.org>
wrote:

> Hello Affiliate and Division Web Coordinators,
>
> I’m writing to provide an update on the Drupal 11 upgrade, outline our
> current process, and share what to expect over the next several
> weeks. Thank you to everyone who has tested so far and to those who will –
> we appreciate your work to maintain the Federation websites. We also
> welcome your feedback on how we can improve the upgrade process moving
> forward.
> *Completed Upgrades*
>
> As of August 13, the following websites have been upgraded to Drupal 11:
>
>    -
>
>    NABS
>    -
>
>    Virginia
>    -
>
>    New Jersey
>    -
>
>    Montana
>    -
>
>    Texas
>    -
>
>    Missouri
>
> *Upgrades Coming Soon*
>
> The following websites are expected to be completed within the next three
> weeks. If you manage one of these websites, please continue to observe the
> content freeze until your upgrade is complete. The list includes expected
> production dates:
>
>    -
>
>    New Hampshire (Aug. 19)
>    -
>
>    North Carolina (Aug. 20)
>    -
>
>    West Virginia (Aug. 21)
>    -
>
>    Connecticut (Aug. 24)
>    -
>
>    Oklahoma (Aug. 27)
>    -
>
>    Idaho (Aug. 28)
>
> We appreciate your patience and cooperation during this process.
> *Next Batch for Testing *
>
> The following websites are included in the next upgrade batch and are now
> available for testing. Please review the website(s) you manage using the
> staging link provided below.
>
> Alaska: *https://nfbaff1d11stg.pumexcomputing.com/nfb-alaska/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-alaska/>
>
> Lawyers: *https://nfbaff1d11stg.pumexcomputing.com/nfb-blindlawyers/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-blindlawyers/>
>
> New York: *https://nfbaff1d11stg.pumexcomputing.com/nfb-new-york/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-new-york/>
>
> Oregon: *https://nfbaff1d11stg.pumexcomputing.com/nfb-oregon/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-oregon/>
>
> Pennsylvania: *https://nfbaff1d11stg.pumexcomputing.com/nfb-pennsylvania/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-pennsylvania/>
>
>  Performing Arts:
> *https://nfbaff1d11stg.pumexcomputing.com/nfb-performing-arts/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-performing-arts/>
>
> Seniors: *https://nfbaff1d11stg.pumexcomputing.com/nfb-seniors-division/*
> <https://nfbaff1d11stg.pumexcomputing.com/nfb-seniors-division/>
>
> If your website is not listed above, it will be included in an upcoming
> upgrade batch.
> *Testing and Content Freeze*
>
> If you manage one of the websites listed in the testing batch, please set
> aside 30–60 minutes to review your Drupal 11 staging site, including
> high-traffic pages and functionality by August 30, 2026.
>
> While the upgrade is in progress, please avoid making content changes to
> your live website starting today and until the upgrade is complete the week
> of August 31. We will share the anticipated live dates the week of August
> 24.
>
> Any content changes made during this period may be overwritten during the
> upgrade process. If that happens, the updates will need to be recreated
> after the upgrade.
>
> If you notice any content differences during testing, you are able to make
> edits on the staging site until August 30. We understand that not updating
> the live site is frustrating, as many affiliates are working on fall
> conventions and other activities. We all want to complete these upgrades as
> soon as possible so we can continue with Federation work.
>
> Please share your feedback or report any concerns by August 30 on the
> listserv or by emailing *web at nfb.org* <web at nfb.org>.
>
> For further information about testing and what to expect, please review
> our previous email about the Drupal 11 upgrade, which is attached.
> *About the Upgrade Process*
>
> We recognize that the upgrade process is taking longer than we originally
> anticipated. Each batch is taking about one month to complete. We
> appreciate your patience and flexibility as our team continues to work
> through the process.
>
> Our team thoroughly tests each upgrade for accessibility, functionality,
> and performance before deploying it to the live website. We follow website
> development best practices to ensure each site is ready before it goes
> live. Remember that you, as a web coordinator are a part of this team.
>
> If your affiliate or division currently has a live CiviCRM registration
> form, please reach out to us. We can work with you to schedule the upgrade
> to minimize disruption to your registration process while ensuring the
> long-term security, accessibility, and sustainability of your website.
>
> It is also important to note that Drupal occasionally releases new
> versions and updates. However, we don't anticipate that there will be these
> types of lengthy annual upgrades.
> *Feedback on Future Upgrades *
>
> As we plan for future upgrades, we would like your feedback on how we
> should approach the process. Below are two options for affiliates and
> divisions to consider and discuss.
> *Option 1: Upgrade Directly to Production *
>
> With this approach, the Drupal upgrade would be deployed directly to the
> live website, eliminating the content-freeze period.
>
> After deployment, affiliates and divisions would need to review their
> websites to confirm that content, functionality, and accessibility are
> working as expected.
>
> Any issues discovered after deployment would be identified on the live
> website and addressed afterward.
> *Option 2: Upgrade to Staging, Then Production (Current Process) *
>
> With our current approach, the development team first applies the upgrade
> to a staging website (a copy of the live website).
>
> Our website team and the respective affiliate or division then test the
> staging site. If issues are identified, the development team addresses them
> before the site is moved to production. Once the website is deployed to
> production, the website team conducts another round of testing.
>
> This approach provides an opportunity to identify and address issues
> before the upgrade is deployed to the live website. However, it requires a
> content freeze between the initial staging upgrade and the production
> deployment to prevent content changes from being overwritten.
> *Thank You *
>
> We would appreciate your feedback on these two approaches and any
> suggestions you have for making the upgrade process smoother.
>
> Please share your thoughts on the listserv or send them to *web at nfb.org*
> <web at nfb.org>.
>
> We appreciate your continued partnership and look forward to enhancing
> your website experience.
>
>  Erin Dowridge-Rodney
>
> Digital Communications Coordinator
>
> National Federation of the Blind
>
> 410-659-9314 ex 2245
>
> *Erodney at nfb.org* <erodney at nfb.org>
>
> Pronouns: She/Her/Hers
>
> *[image: National Federation of the Blind logo, Live the life you want
> tagline, nfb.org]* <https://nfb.org/>
>
>
> _______________________________________________
> NFB-Web mailing list
> NFB-Web at nfbnet.org
> http://nfbnet.org/mailman/listinfo/nfb-web_nfbnet.org
> To unsubscribe, change your list options or get your account info for
> NFB-Web:
> http://nfbnet.org/mailman/options/nfb-web_nfbnet.org/kpirnie77%40gmail.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nfbnet.org/pipermail/nfb-web_nfbnet.org/attachments/20260817/3c94a973/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 49649 bytes
Desc: not available
URL: <http://nfbnet.org/pipermail/nfb-web_nfbnet.org/attachments/20260817/3c94a973/attachment-0001.png>


More information about the NFB-Web mailing list