ZcashFoundation
docs: Update broken link in book/src/dev/release-process.md for "Keeping Up-to-Date"
What happened?
this PR https://github.com/ZcashFoundation/zebra/pull/4917/files committed a link to a document "Keeping Up-to-Date" which as far as I can see did not exist at the time of the commit and it does not exist now.
See [Keeping Up-to-Date](guide/updating "Updating your projects")
Document at time of commit https://github.com/ZcashFoundation/zebra/blob/085367fc372fa6dff77050b82320db9c179bd530/book/src/dev/release-process.md#supported-update-paths
I came across this issue while looking for a similar document in zebra regarding for https://zcash.github.io/zcash/user/release-support.html
What were you doing when the issue happened?
No response
Zebra logs
No response
Zebra Version
No response
Which operating systems does the issue happen on?
- [ ] Linux
- [ ] macOS
- [ ] Windows
- [ ] Other OS
OS details
No response
Additional information
No response
Also can you explain the following in the "Keeping Up-to-Date" document or in the release notes , if I understand correctly,
2.50 release expires on 21st November (3_021_400 + 105 days -> 7th of August + 105 days = November 21, 2025) 3.0 release on 17th of November, docker image on Nov 18, 2025 at 3:31 pm
so you have 56-90 hours to upgrade between stable releases, otherwise you get a panic (based on changes introduced in PR6351)
Zebra 3.0.0 release notes are available here: https://github.com/ZcashFoundation/zebra/releases/tag/v3.0.0
Thank you for reporting the broken link, we will look into this.
Also can you explain the following in the "Keeping Up-to-Date" document or in the release notes , if I understand correctly,
2.50 release expires on 21st November (3_021_400 + 105 days -> 7th of August + 105 days = November 21, 2025) 3.0 release on 17th of November, docker image on Nov 18, 2025 at 3:31 pm
so you have 56-90 hours to upgrade between stable releases, otherwise you get a panic (based on changes introduced in PR6351)
We would normally give more time to upgrade between stable releases, however this time we were limited by NU6.1 activation happening at block height 3146400 or sometime during November 24, 2025.
Certain releases not supporting network upgrades (in this case the 2.5.0 release) that would otherwise expire after the chosen activation height must have their EOL support changed from the usual 16 week support period so that they would expire ahead of that upgrade (see https://github.com/ZcashFoundation/zebra/blob/main/book/src/dev/release-process.md#supported-releases). Additionally we identified a panic in the 3.0.0 release candidate that we wanted to fix ahead of the 3.0.0 stable release and which delayed it, shortening the overlap in support between the 2 versions.
thanks @mpguerra for explaining some of the reasons here, but it would help to add a warning to the 3.0.0 release notes to give a sense of the urgency and specify this short time frame to upgrade. these are essentially mandatory upgrades and they should be called out as so.