From efd04ee86a2eb45a083dce5477e3bff2d5777ac9 Mon Sep 17 00:00:00 2001 From: copernicus-mogley <6251098+copernicus-mogley@users.noreply.github.com> Date: Thu, 31 May 2018 16:26:48 +0200 Subject: [PATCH] Change auto-senescence terminology --- _posts/2017-05-01-release-cycle-and-lifetimes.md | 6 ++++-- _posts/2017-09-22-release-cycle-update.md | 12 +++++++----- _posts/2017-11-20-new-release-1-0-13.md | 6 ++++-- _posts/2018-04-14-new-release-1-1-0.md | 6 ++++-- 4 files changed, 19 insertions(+), 11 deletions(-) diff --git a/_posts/2017-05-01-release-cycle-and-lifetimes.md b/_posts/2017-05-01-release-cycle-and-lifetimes.md index 9ab20c9..54b7e16 100644 --- a/_posts/2017-05-01-release-cycle-and-lifetimes.md +++ b/_posts/2017-05-01-release-cycle-and-lifetimes.md @@ -9,6 +9,8 @@ permalink: > published: true post_date: 2017-05-01 00:00:00 --- +*Edit 2018-05-31:* Auto-senescence terminology changed to "end-of-support halt". + Starting in May the Zcash development effort will institute a new release policy. There are a few immediate take-aways for users:
-

Auto-senescence & 1.0.9 Deprecation

-This change to the release cycle length affects how they line up with the auto-senescence feature we introduced in the 1.0.9 update and the 18 week schedule it runs on. We do not plan on updating the deprecation time frame so now a version will become deprecated at about the same time the 3rd subsequent version is released. For example, version 1.0.9 will be deprecated just as version 1.0.12 is released. A warning will appear for nodes running the official Zcash client about two weeks before the version they are running is set to become deprecated. +

End-of-support halt & 1.0.9 Deprecation

+This change to the release cycle length affects how they line up with the end-of-support halt feature (previously called "auto-senescence") we introduced in the 1.0.9 update and the 18 week schedule it runs on. We do not plan on updating the deprecation time frame so now a version will become deprecated at about the same time the 3rd subsequent version is released. For example, version 1.0.9 will be deprecated just as version 1.0.12 is released. A warning will appear for nodes running the official Zcash client about two weeks before the version they are running is set to become deprecated. -As we stated previously, once a version is deprecated via the auto-senescence feature, nodes running that version will automatically exit when they detect they've reached their deprecation phase. This feature will always have the ability to opt-out but it's important to note that for deprecated releases, the only help the Zcash Company user support team promises is in upgrading to the latest release. +As we stated previously, once a version is deprecated via the end-of-support halt feature, nodes running that version will automatically exit when they detect they've reached their deprecation phase. This feature will always have the ability to opt-out but it's important to note that for deprecated releases, the only help the Zcash Company user support team promises is in upgrading to the latest release. -At block 193076, all nodes running version 1.0.9 which do not have the -disabledeprecation=1.0.9 flag set to opt out of auto-senescence will automatically shut down. These nodes should already be receiving a related message about the upcoming version deprecation. +At block 193076, all nodes running version 1.0.9 which do not have the -disabledeprecation=1.0.9 flag set to opt out of end-of-support halt will automatically shut down. These nodes should already be receiving a related message about the upcoming version deprecation. -Of course we recommend that instead of using the configuration to disable deprecation of 1.0.9 that node operators update to the most recent version of zcashd or another well-maintained implementation. Client and network security improvements are often addressed in releases so it's a good idea to always stay updated with the most recent version. If there is a particular reason why you cannot update or do not want to, please reach out to us in the community chat or by email so we can better understand your needs. We're also happy to answer any questions about the release cycle or deprecation policy and will communicate any future changes to these processes we deem beneficial. \ No newline at end of file +Of course we recommend that instead of using the configuration to disable deprecation of 1.0.9 that node operators update to the most recent version of zcashd or another well-maintained implementation. Client and network security improvements are often addressed in releases so it's a good idea to always stay updated with the most recent version. If there is a particular reason why you cannot update or do not want to, please reach out to us in the community chat or by email so we can better understand your needs. We're also happy to answer any questions about the release cycle or deprecation policy and will communicate any future changes to these processes we deem beneficial. diff --git a/_posts/2017-11-20-new-release-1-0-13.md b/_posts/2017-11-20-new-release-1-0-13.md index 6caa25a..d55a651 100644 --- a/_posts/2017-11-20-new-release-1-0-13.md +++ b/_posts/2017-11-20-new-release-1-0-13.md @@ -8,11 +8,13 @@ permalink: https://blog.z.cash/new-release-1-0-13/ published: true post_date: 2017-11-20 00:00:00 --- +*Edit 2018-05-31:* Auto-senescence terminology changed to "end-of-support halt". + Today we're announcing the release of Zcash 1.0.13, introducing new features, performance improvements and bug fixes. Our new low-memory prover reduces memory usage by 43% when generating a shielded transaction, from 3 GB to 1.7 GB. An experimental feature, payment disclosure, can help services better manage their shielded payments. We also now fully support the z_shieldcoinbase RPC call to help miners sweep up and shield their coinbase rewards. Summary of the changes included in this release:
    -
  1. Auto-senescence cycle has been reduced from 18 to 16 weeks. (#2733)
    2. +
  2. End-of-support halt (previously called "auto-senescence") cycle has been reduced from 18 to 16 weeks. (#2733)
  3. Low-memory prover reduces JoinSplit creation memory usage from 3 GB to 1.7GB. (#2670, stats)
  4. Payment disclosure has been added as an experimental feature with new RPC calls z_getpaymentdisclosure and z_validatepaymentdisclosure (#2159). This feature enables a sender to prove that a payment was made to a recipient, which can help services better manage their shielded payments. See the documentation for a full explanation of this new feature.
  5. z_shieldcoinbase is now a fully supported RPC call (#2692). See an explanation of this command here .
    6. @@ -25,4 +27,4 @@ Summary of the changes included in this release:
We're encouraging all users and miners to update to this new version. See our download page and the 1.0 User Guide for more information. -For a more complete list of changes, see our 1.0.13 GitHub milestone. To follow our progress, watch the GitHub project and join the forum. \ No newline at end of file +For a more complete list of changes, see our 1.0.13 GitHub milestone. To follow our progress, watch the GitHub project and join the forum. diff --git a/_posts/2018-04-14-new-release-1-1-0.md b/_posts/2018-04-14-new-release-1-1-0.md index 6d5406f..4bd5249 100644 --- a/_posts/2018-04-14-new-release-1-1-0.md +++ b/_posts/2018-04-14-new-release-1-1-0.md @@ -8,6 +8,8 @@ permalink: https://blog.z.cash/new-release-1-1-0/ published: true post_date: 2018-04-14 12:09:17 --- +*Edit 2018-05-31:* Auto-senescence terminology changed to "end-of-support halt". + After several months of work, we are happy to announce the release of Zcash 1.1.0, the first Overwinter-compatible version of the Zcash node software!

Overwinter network upgrade

The first block of Overwinter will be block 347500, which is expected to be mined on the 25th of June 2018, just before noon EDT / 16:00 UTC. Please upgrade to this release, or any subsequent release, in order to follow the Overwinter network upgrade. See our previous blog post and the Overwinter Network Upgrade page for more information. @@ -29,7 +31,7 @@ In this version, it is only enforced for peers that send protocol versions Pulled in support for the NODE_BLOOM service bit. (#2814)
  • Fixed a bug in the block index rewinding code added in 1.0.15. (#3132, #3166)
  • Fixed a bug in z_mergetoaddress when running it several times in parallel. (#3106)
    • -
  • Fixed a bug where mainnet auto-senescence heights were applied to testnet and regtest. (#3069)
    • +
  • Fixed a bug where mainnet end-of-support halt (previously called "auto-senescence") heights were applied to testnet and regtest. (#3069)
  • Fixed bugs on several unsupported platforms. (#2820, #2965, #3089, #3117)
  • Made Rust compilation mandatory. (#3127)
  • Added support for Rust crates to the depends system. (#3096)
    • @@ -39,4 +41,4 @@ In this version, it is only enforced for peers that send protocol versions We’re encouraging all users and miners to update to this version. See the download page and 1.0 User Guide for more information. -For a more complete list of changes, see the 1.1.0 GitHub milestone. To follow our progress, watch the GitHub project and join the forum. \ No newline at end of file +For a more complete list of changes, see the 1.1.0 GitHub milestone. To follow our progress, watch the GitHub project and join the forum.