I'm gonna blow a gasket, I swear I am

[wblock]

Hm. I think we could add a big "Note" section before the trains pointing out that nightlies and other experimental trains are provided to allow people to get more testing time before switching to a new branch, and anyone running a non-production branch should be prepared to experience bugs or problems and preferably be willing to submit bug reports. It would be something that would be easy to point at. As far as getting people to read it... well, that's been a problem as long as there has been writing. :)

 

[wblock]

Here is what I just added:

 

[Dice]

Here is what I just added:
View attachment 18520

I find that note unfortunately confusing by introducing another concept: "Production trains".
Is this something else, wider than "STABLE" ? If so, what <explicit> trains does this include?

 

[Redcoat]

I find that note unfortunately confusing by introducing another concept: "Production trains".
Is this something else, wider than "STABLE" ? If so, what <explicit> trains does this include?

I second Dice's view and question above. Also, just where exactly has this note been "added"?

 

[BigDave]

From my perspective, the issue could be resolved by removal of the word STABLE
from the FreeNAS 11 RC train dropdown window and anywhere else it suggests
STABLE when it's NOT.

If this is not practical and more trouble than it's worth, it's probably best to just
do nothing, instead of adding additional verbiage or new terms that will cause further confusion.

 

[gpsguy]

I second Dice's view and question above. Also, just where exactly has this note been "added"?

It's a new commit for the 11.0 docs.

 

[Dice]

From my perspective, the issue could be resolved by removal of the word STABLE
from the FreeNAS 11 RC train dropdown window and anywhere else it suggests
STABLE when it's NOT.

If this is not practical and more trouble than it's worth, it's probably best to just
do nothing, instead of adding additional verbiage or new terms that will cause further confusion.

agree.

 

[wblock]

I find that note unfortunately confusing by introducing another concept: "Production trains".
Is this something else, wider than "STABLE" ? If so, what <explicit> trains does this include?

The Production/Non-production language has been in there for years. It was only a few days ago that I rewrote that table to be more explicit.

 

[wblock]

I second Dice's view and question above. Also, just where exactly has this note been "added"?

To the manual. Commits can be seen in the github repo before the release: https://github.com/freenas/freenas-docs/

 

[Dice]

The Production/Non-production language has been in there for years. It was only a few days ago that I rewrote that table to be more explicit.

Yes.
However, I was under the impression the edit was aimed at solving the confusion @BigDave pointed out. That is, what releases are considered included in <production> and which are not.
What "production" implies is clear, IMO.

 

[Redcoat]

To the manual. Commits can be seen in the github repo before the release: https://github.com/freenas/freenas-docs/

Thanks for the info. I'd forgotten where to look - now bookmarked.

 

[raidflex]

I am not sure whose idea it was to add stable to the 11.0 train, since it has never been at a "stable" point in its release history. Removing that verbiage would make the most sense, but at this point with 11 being released MAYBE in the next week or two this may not matter. But going forward stable should not be used unless it is production ready.

 

[danb35]

But going forward stable should not be used unless it is production ready.

Agreed.

 

[leonroy]

So been trying to figure out why a notice for 'RC4' appeared on my FreeNAS servers with no release notes or changelog listed. Some searching led me to this thread...

Here's what I've been using since @Kris Moore's post here:
https://forums.freenas.org/index.php?threads/freenas-11-0-rc-now-available.54228/

So from what I'm understanding from this thread, FreeNAS-11-STABLE is not a *stable* release train?!

 

[danb35]

So from what I'm understanding from this thread, FreeNAS-11-STABLE is not a *stable* release train?!

No, it isn't. Not yet, anyway.

 

[leonroy]

As a pretty savvy *ix user this caught even me. These aren't live boxes I've upgraded so I'm not hugely concerned about being on a RC train - that said I am pretty concerned about the development process behind FreeNAS. Creating separate trains for dev and stable isn't hard. If dev management can't be bothered to follow best practise (which is there for a reason) on such simple stuff then it certainly doesn't bode well for trickier stuff like the new Angular UI/Docker/bhyve integration.

 

[danb35]

...and they just went through this a couple of months ago. They released FN10, which they called Corral, as though it was production-ready. A month later, they realized it wasn't, and pulled the release, presumably with egg on their collective faces. This is not indicating that they've learned from that fiasco.

 

[gpsguy]

This is not indicating that they've learned from that fiasco.

To be fair, they have released 4 RC's for 11.0. As I recall, none were planned initially.

 

[danb35]

True, and I probably overstated the case--but at least at some point, they started putting RCs into the 11-STABLE train, as though they were stable releases. They may not have intended to indicate to the userbase that they were stable releases, but what else does the STABLE train mean?

I understand that deciding whether something is truly ready to release can be hard. But if you've already decided that it isn't (as shown by the RC indication in the version number), it doesn't seem too hard to avoid telling your users that it is.