# Where is Node-RED 1.0?

**URL:** <https://discourse.nodered.org/t/where-is-node-red-1-0/13482>\
**Category:** News\
**Created:** [19 July 2019 12:32 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482 "2019-07-19T12:32:18Z")\
**Posts on this page:** 8\
**Page:** 2

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [20 July 2019 14:34 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/21 "2019-07-20T14:34:51Z")

</div>

> [@Colin](#):
>
> It does really depend on what the 'system' is doing. If it is, for example, a Pi with no access to the internet, doing a defined job satisfactorily, then there is no need to update anything.

🙂 as my edit also points out.

However, even there it is work staying not too far out of step because it will eventually become necessary to update and then you find that you virtually have to start from scratch if you are too far behind.

That's why I always try to keep documentation of what I've installed, why and how. I will often try to automate that but, in reality, changes over time can be so drastic that it is easier to go back to the documentation and install by hand than it is to try and keep any automation script up-to-date - again, we are talking about home systems now, not commercial production systems.

The other advantage to the "by hand" approach is that it forces a clean install rather than carrying forward any cruft that is no longer needed. I tend to do this on my main PC as well, I do have a script to reinstall but generally only ever run a few parts of it on a new PC and it is designed to only tweak the settings and install core software that I know I will need.

---

<div class="post-metadata">

**Author:** ![drmibell](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/drmibell/32/8424_2.png) [@drmibell](https://discourse.nodered.org/u/drmibell)\
**Post date:** [21 July 2019 22:01 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/22 "2019-07-21T22:01:22Z")

</div>

> [@wb666greene](#):
>
> "if it ain't broke, don't fix it!"

Have we perhaps lost sight of the fact that NR is at version 0.2.x? I think that we have been spoiled by the tremendous stability of NR despite nearly continuous revision (and improvement).

Quoting from the [Semantic Versioning Specification](https://github.com/semver/semver/blob/master/semver.md):

> Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

In other words, breaking changes can be made at any time for any reason. The good news is that a 1.0 release represents a commitment to future stability that a version 0.x.z absolutely does not.

I'm not sure I agree entirely with this from the Semantic Versioning FAQ, but it does seem to be time to go for 1.0.

> If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you're worrying a lot about backwards compatibility, you should probably already be 1.0.0.

---

<div class="post-metadata">

**Author:** ![krambriw](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/krambriw/32/5429_2.png) [@krambriw](https://discourse.nodered.org/u/krambriw)\
**Post date:** [22 July 2019 05:14 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/23 "2019-07-22T05:14:48Z")

</div>

Isn't NR really still in alpha versions? Since functionality is still being added? As once defined by IBM

> **[Software release life cycle](https://en.wikipedia.org/wiki/Software_release_life_cycle)**
>
> A software release life cycle is the sum of the stages of development and maturity for a piece of computer software: ranging from its initial development to its eventual release, and including updated versions of the released version to help improve software or fix software bugs still present in the software.
> Usage of the "alpha/beta" test terminology originated at IBM. Similar terminologies for IBM's software development were used by people involved with IBM from at least the 1950s (and probabl...

So far, as being alpha as I see it, I think NR is very stable, personally I have had no issues at all, it just runs. Anyway, being an old fox, I will most likely wait for 1.1, never use a 1.0 😉

Have a great summer 🏖

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [22 July 2019 06:13 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/24 "2019-07-22T06:13:54Z")

</div>

Given that it has existed and been successful for quite a few years now, I hardly think that we can consider it beta let alone alpha. In terms of Node.js style versioning, the alpha/beta thing doesn't really apply anyway and many people (myself included), tend to add "-alpha1" or "beta1" etc to the end of the version string to indicate if the version should be considered alpha/beta quality.

A sub-1.0 version number generally just indicates that it still isn't very stable. Once you hit v1, there is an expectation that breaking changes will reduce in volume and that when they happen, you will continue to support the previous stable version at least for a while. An n and n-1 support model is very common and indeed is built into the contractual arrangements for many organisations including much of the UK's NHS.

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [19 August 2019 08:50 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/25 "2019-08-19T08:50:54Z")

</div>

I'm not up to speed with doc changes... I guess then my best plan is to wait for the September 1.0 release or at least beta 2, check out new documentation (wherever that is) and I'll do a write-up. Anything to help as NR is my favourite tool. I can see that response was written a while ago as it is already mid-August.

---

<div class="post-metadata">

**Author:** ![scargill](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/scargill/32/1118_2.png) [@scargill](https://discourse.nodered.org/u/scargill)\
**Post date:** [7 September 2019 07:21 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/26 "2019-09-07T07:21:41Z")

</div>

Did everyone go on long holidays? It's September 7 already.

---

<div class="post-metadata">

**Author:** ![dceejay](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/dceejay/32/38_2.png) [@dceejay](https://discourse.nodered.org/u/dceejay)\
**Post date:** [7 September 2019 07:33 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/27 "2019-09-07T07:33:38Z")

</div>

Yes we did ! Very nice they were too.  
1.0 Beta 3 (release candidate) was released a short while ago

---

<div class="post-metadata">

**Author:** ![kuema](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/kuema/32/6542_2.png) [@kuema](https://discourse.nodered.org/u/kuema)\
**Post date:** [7 September 2019 07:59 UTC](https://discourse.nodered.org/t/where-is-node-red-1-0/13482/28 "2019-09-07T07:59:52Z")

</div>

Good things take time. I wouldn't want to rush a v1.0.0 release either. 👍

And for now we have betas to test. 😀

[Previous page](https://discourse.nodered.org/t/where-is-node-red-1-0/13482.md?page=1)
