From 1d8c35d889acd12ad16fa20e6dfee075ae8b2101 Mon Sep 17 00:00:00 2001 From: Pierre Vanduynslager Date: Mon, 31 Dec 2018 03:20:36 -0500 Subject: [PATCH] docs: update FAQ regarding initial release version --- docs/support/FAQ.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/support/FAQ.md b/docs/support/FAQ.md index 74ea3135..7bbac18c 100644 --- a/docs/support/FAQ.md +++ b/docs/support/FAQ.md @@ -222,7 +222,7 @@ If you need more control over the timing of releases, see [Triggering a release] This is not supported by **semantic-release** as it's not considered a good practice, mostly because [Semantic Versioning](https://semver.org) rules applies differently to major version zero. -In early development phase when your package is not ready for production yet we recommend to publish releases on a distribution channel (for example npm’s [dist-tags](https://docs.npmjs.com/cli/dist-tag)) or to develop on a `dev` branch and merge it to `master` periodically. See [Triggering a release](../../README.md#triggering-a-release) for more details on those solutions. +If your project is under heavy development, with frequent breaking changes, and is not production ready yet we recommend [publishing pre-releases](../recipes/pre-releases.md#publishing-pre-releases). See [“Introduction to SemVer” - Irina Gebauer](https://blog.greenkeeper.io/introduction-to-semver-d272990c44f2) for more details on [Semantic Versioning](https://semver.org) and the recommendation to start at version `1.0.0`.