WIP: Translating react-16-7 article

Author: alejandronanez

content/blog/2018-12-19-react-v-16-7.md

@@ -1,13 +1,13 @@
 ---
-title: "React v16.7: No, This Is Not the One With Hooks"
+title: "React v16.7: No, Este es el que no tiene hooks"
 author: [acdlite]
 ---
 
-Our latest release includes an important performance bugfix for `React.lazy`. Although there are no API changes, we're releasing it as a minor instead of a patch.
+Nuestro último release incluye un imporante bugfix de performance para `React.lazy`. A pesar de que no hay cambios en la API, estamos lanzandolo como un minor en vez de un patch.
 
-## Why Is This Bugfix a Minor Instead of a Patch? {#why-is-this-bugfix-a-minor-instead-of-a-patch}
+## ¿Por qué este bugfix es un minor en vez de un patch? {#why-is-this-bugfix-a-minor-instead-of-a-patch}
 
-React follows [semantic versioning](/docs/faq-versioning.html). Typically, this means that we use patch versions for bugfixes, and minors for new (non-breaking) features. However, we reserve the option to release minor versions even if they do not include new features. The motivation is to reserve patches for changes that have a very low chance of breaking. Patches are the most important type of release because they sometimes contain critical bugfixes. That means patch releases have a higher bar for reliability. It's unacceptable for a patch to introduce additional bugs, because if people come to distrust patches, it compromises our ability to fix critical bugs when they arise — for example, to fix a security vulnerability.
+React sigue [versionamiento semántico](/docs/faq-versioning.html). Tipicamente, esto significa que usamos versiones patch para bugfixes, y minors para nuevos (non-breaking) features. Sin embargo, nos reservamos la opción de lanzar versiones minor aun si no incluyen nuevos features. The motivation is to reserve patches for changes that have a very low chance of breaking. Patches are the most important type of release because they sometimes contain critical bugfixes. That means patch releases have a higher bar for reliability. It's unacceptable for a patch to introduce additional bugs, because if people come to distrust patches, it compromises our ability to fix critical bugs when they arise — for example, to fix a security vulnerability.
 
 We never intend to ship bugs. React has a hard-earned reputation for stability, and we intend to keep it that way. We thoroughly test every version of React before releasing. This includes unit tests, generative (fuzzy) tests, integration tests, and internal dogfooding across tens of thousands of components. However, sometimes we make mistakes. That's why, going forward, our policy will be that if a release contains non-trivial changes, we will bump the minor version, even if the external behavior is the same. We'll also bump the minor when changing `unstable_`-prefixed APIs.