zec
/
zcash-blog
mirror of https://github.com/zcash/zcash-blog.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Change auto-senescence terminology

This commit is contained in:
copernicus-mogley 2018-05-31 16:26:48 +02:00
parent c9b1c024ee
commit efd04ee86a
4 changed files with 19 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
_posts/2017-05-01-release-cycle-and-lifetimes.md
View File

@ -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:
<ul class="simple">
<li>We'll release monthly on the third Tuesday, starting with 1.0.9 on May 16th.</li>
@ -29,7 +31,7 @@ An essential change with this new policy is an explicit <cite>release lifecycle<
For <cite>active releases</cite> which have not yet reached their deprecation date, we make our best effort to provide security fixes, follow up to bug reports, avoid disruption on the production network, and help users to upgrade to the latest release. For <cite>deprecated releases</cite> the only help we promise is in upgrading to the latest release.
In order to codify this cycle, we even intend to introduce a feature called <cite>auto-senescence</cite> starting in 1.0.9 which will cause nodes to automatically exit when they detect they've reached their deprecation phase. This feature will always have an opt-out, since (as discussed below) our goal is to give users their own choice, not to coerce or control them.
In order to codify this cycle, we even intend to introduce a feature called <cite>end-of-support halt</cite> (previously called "auto-senescence") starting in 1.0.9 which will cause nodes to automatically exit when they detect they've reached their deprecation phase. This feature will always have an opt-out, since (as discussed below) our goal is to give users their own choice, not to coerce or control them.
An important side-note: this policy is defined entirely in the context of a single release, so a user does not need to know anything about our future releases or our new policies for those releases in order to understand this policy for their own installation.
<div id="user-autonomy-deprecation-vs-auto-upgrade" class="section">
@ -69,4 +71,4 @@ Please reach out to us with any feedback on this new release policy. You can fin
</table>
</div>
</div>
</div>
</div>

12
_posts/2017-09-22-release-cycle-update.md
View File

@ -9,6 +9,8 @@ permalink: >
published: true
post_date: 2017-09-22 00:00:00
---
*Edit 2018-05-31:* Auto-senescence terminology changed to "end-of-support halt".
Ahead of the 1.0.9 release a few months ago, the Zcash development team <a class="reference external" href="/release-cycle-and-lifetimes/">announced</a> a new monthly release cycle and deprecation policy. We learned a lot in the first month of the release cycle and decided to extend it to 6 weeks. We've discussed this openly in the <a class="reference external" href="https://chat.zcashcommunity.com">community chat</a> <cite>#zcash-dev</cite> channel and in the weekly <a class="reference external" href="https://forum.z.cash/c/dev-updates">forum developer updates</a>.
This cycle extension allows for several improvements:
@ -18,11 +20,11 @@ This cycle extension allows for several improvements:
<li>less frequent updating for users and third-party services.</li>
</ul>
<div id="auto-senescence-1-0-9-deprecation" class="section">
<h2>Auto-senescence &amp; 1.0.9 Deprecation</h2>
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.
<h2>End-of-support halt &amp; 1.0.9 Deprecation</h2>
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 <cite>-disabledeprecation=1.0.9</cite> 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 <cite>-disabledeprecation=1.0.9</cite> 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 <a class="reference external" href="https://z.cash/download.html">update</a> to the most recent version of <cite>zcashd</cite> 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 <a class="reference external" href="https://chat.zcashcommunity.com">community chat</a> or by <a class="reference external" href="mailto:info@z.cash">email</a> 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.
Of course we recommend that instead of using the configuration to disable deprecation of 1.0.9 that node operators <a class="reference external" href="https://z.cash/download.html">update</a> to the most recent version of <cite>zcashd</cite> 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 <a class="reference external" href="https://chat.zcashcommunity.com">community chat</a> or by <a class="reference external" href="mailto:info@z.cash">email</a> 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.

6
_posts/2017-11-20-new-release-1-0-13.md
View File

@ -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 <tt class="docutils literal">z_shieldcoinbase</tt> RPC call to help miners sweep up and shield their coinbase rewards.
Summary of the changes included in this release:
<ol class="arabic simple">
<li>Auto-senescence cycle has been reduced from 18 to 16 weeks. (<a class="reference external" href="https://github.com/zcash/zcash/pull/2733">#2733</a>)</li>
<li>End-of-support halt (previously called "auto-senescence") cycle has been reduced from 18 to 16 weeks. (<a class="reference external" href="https://github.com/zcash/zcash/pull/2733">#2733</a>)</li>
<li>Low-memory prover reduces JoinSplit creation memory usage from 3 GB to 1.7GB. (<a class="reference external" href="https://github.com/zcash/zcash/pull/2670">#2670</a>, <a class="reference external" href="https://speed.z.cash/timeline/?exe=1&amp;base=1%2B178&amp;ben=memory+createjoinsplit&amp;env=1&amp;revs=50&amp;equid=off&amp;quarts=on&amp;extr=on">stats</a>)</li>
<li>Payment disclosure has been added as an experimental feature with new RPC calls <tt class="docutils literal">z_getpaymentdisclosure</tt> and <tt class="docutils literal">z_validatepaymentdisclosure</tt> (<a class="reference external" href="https://github.com/zcash/zcash/pull/2159">#2159</a>). 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 <a class="reference external" href="https://github.com/zcash/zcash/blob/master/doc/payment-disclosure.md">the documentation</a> for a full explanation of this new feature.</li>
<li><tt class="docutils literal">z_shieldcoinbase</tt> is now a fully supported RPC call (<a class="reference external" href="https://github.com/zcash/zcash/pull/2692">#2692</a>). See an explanation of this command <a class="reference external" href="https://github.com/zcash/zcash/tree/master/doc/shield-coinbase.md">here</a> .</li>
@ -25,4 +27,4 @@ Summary of the changes included in this release:
</ol>
We're encouraging all users and miners to update to this new version. See our <a class="reference external" href="https://z.cash/download.html">download</a> page and the <a class="reference external" href="https://github.com/zcash/zcash/wiki/1.0-User-Guide">1.0 User Guide</a> for more information.
For a more complete list of changes, see our <a class="reference external" href="https://github.com/zcash/zcash/milestone/63?closed=1">1.0.13</a> GitHub milestone. To follow our progress, watch <a class="reference external" href="https://github.com/zcash/zcash/milestones">the GitHub project</a> and <a class="reference external" href="https://forum.z.cash/">join the forum</a>.
For a more complete list of changes, see our <a class="reference external" href="https://github.com/zcash/zcash/milestone/63?closed=1">1.0.13</a> GitHub milestone. To follow our progress, watch <a class="reference external" href="https://github.com/zcash/zcash/milestones">the GitHub project</a> and <a class="reference external" href="https://forum.z.cash/">join the forum</a>.

6
_posts/2018-04-14-new-release-1-1-0.md
View File

@ -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!
<h2>Overwinter network upgrade</h2>
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 <a href="https://blog.z.cash/overwinter/">previous blog post</a> and the <a href="https://z.cash/upgrade/overwinter.html">Overwinter Network Upgrade page</a> for more information.
@ -29,7 +31,7 @@ In this version, it is only enforced for peers that send protocol versions <code
<li>Pulled in support for the <code>NODE_BLOOM</code> service bit. (<a href="https://github.com/zcash/zcash/pull/2814">#2814</a>)</li>
<li>Fixed a bug in the block index rewinding code added in 1.0.15. (<a href="https://github.com/zcash/zcash/pull/3132">#3132</a>, <a href="https://github.com/zcash/zcash/pull/3166">#3166</a>)</li>
<li>Fixed a bug in <code>z_mergetoaddress</code> when running it several times in parallel. (<a href="https://github.com/zcash/zcash/pull/3106">#3106</a>)</li>
<li>Fixed a bug where mainnet auto-senescence heights were applied to testnet and regtest. (<a href="https://github.com/zcash/zcash/pull/3069">#3069</a>)</li>
<li>Fixed a bug where mainnet end-of-support halt (previously called "auto-senescence") heights were applied to testnet and regtest. (<a href="https://github.com/zcash/zcash/pull/3069">#3069</a>)</li>
<li>Fixed bugs on several unsupported platforms. (<a href="https://github.com/zcash/zcash/pull/2820">#2820</a>, <a href="https://github.com/zcash/zcash/pull/2965">#2965</a>, <a href="https://github.com/zcash/zcash/pull/3089">#3089</a>, <a href="https://github.com/zcash/zcash/pull/3117">#3117</a>)</li>
<li>Made Rust compilation mandatory. (<a href="https://github.com/zcash/zcash/pull/3127">#3127</a>)</li>
<li>Added support for Rust crates to the depends system. (<a href="https://github.com/zcash/zcash/pull/3096">#3096</a>)</li>
@ -39,4 +41,4 @@ In this version, it is only enforced for peers that send protocol versions <code
</ol>
We’re encouraging all users and miners to update to this version. See the <a class="reference external" href="https://z.cash/download.html">download</a> page and <a class="reference external" href="https://github.com/zcash/zcash/wiki/1.0-User-Guide">1.0 User Guide</a> for more information.
For a more complete list of changes, see the <a href="https://github.com/zcash/zcash/milestone/70?closed=1">1.1.0</a> GitHub milestone. To follow our progress, watch <a class="reference external" href="https://github.com/zcash/zcash/milestones">the GitHub project</a> and <a class="reference external" href="https://forum.z.cash/">join the forum</a>.
For a more complete list of changes, see the <a href="https://github.com/zcash/zcash/milestone/70?closed=1">1.1.0</a> GitHub milestone. To follow our progress, watch <a class="reference external" href="https://github.com/zcash/zcash/milestones">the GitHub project</a> and <a class="reference external" href="https://forum.z.cash/">join the forum</a>.