March 7, 20188 yr 9 minutes ago, 1812 said: I vote that we change the releases to be named after barn animals instead of numbers. It would allow for better clarity: "I'm currently on unRaid Rooster. Is it worth upgrading to unRaid Diary Cow or should I wait for unRaid Donkey?" Gets my vote! ROFL
March 8, 20188 yr If they can name Android after sweets why not. We would have to go in alphabetical order though. So starting with A, I guess instead of Donkey you would have...
March 8, 20188 yr 17 minutes ago, trurl said: If they can name Android after sweets why not. We would have to go in alphabetical order though. So starting with A, I guess instead of Donkey you would have... Antelope? Alligator? Aardvark? Seem to be plenty enough options.
March 8, 20188 yr 3 hours ago, 1812 said: I vote that we change the releases to be named after barn animals 47 minutes ago, 1812 said: Antelope? Alligator? Aardvark? Seem to be plenty enough options. You see many antelopes, alligators and aardvarks in barns?
March 8, 20188 yr 27 minutes ago, jonathanm said: You see many antelopes, alligators and aardvarks in barns? It’s a thing: https://www.istockphoto.com/photo/close-up-of-aardvark-in-barn-with-nose-near-the-camera-gm137943189-13522349
March 8, 20188 yr Can't wait for the Squid release [emoji3]I'd boycott it on principle....Sent from my LG-H815 using Tapatalk
March 8, 20188 yr as a suggestion it would be cool if the devs would write once a week a small "what we have done|on what are we working". Blog Style post like https://factorio.com/blog/ does every friday (i visit this site every friday just to check out whats new) Edited March 8, 20188 yr by nuhll
March 8, 20188 yr They dont have time to fix things on the product and you want them to write LiveJournal entries?
March 10, 20188 yr Wait, you keep adding new features with every new RC? Do you realise that you're chasing your tail that way? Also, I'd like to update the webGui without having to update the whole OS and restarting.
March 11, 20188 yr Is there a roadmap? or any place where the new features of 6.5 FINAL are written? Are you using agile or something?
March 11, 20188 yr Wait, you keep adding new features with every new RC? Do you realise that you're chasing your tail that way? Also, I'd like to update the webGui without having to update the whole OS and restarting.Gotta test those new features eventually. If they feel pretty solid about them then throw them in. I appreciate these new changes.
March 11, 20188 yr 1 hour ago, realies said: Also, I'd like to update the webGui without having to update the whole OS and restarting. How so you expect this to be done? The latest GUI features and updates are tied hand-in-hand with the latest version of the OS!
March 11, 20188 yr @limetech, good luck trolling. Let me know when you get bored of trying to reinvent the wheel. @Frank1940, which webGui features in particular are "tied hand-in-hand" with the latest version of the OS? As to how one would expect this to be done, look at software packaging.
March 11, 20188 yr 1 hour ago, realies said: @limetech, good luck trolling. Let me know when you get bored of trying to reinvent the wheel. @Frank1940, which webGui features in particular are "tied hand-in-hand" with the latest version of the OS? As to how one would expect this to be done, look at software packaging. To be honest, I wouldn't get too hung up on the terminology - it's been discussed and the naming scheme is unlikely to change. I like how Squid explained it here :
March 11, 20188 yr 2 hours ago, sureguy said: To be honest, I wouldn't get too hung up on the terminology We should be, when someone uses a very well defined terminology but to mean something completely different. There has been spent quite a lot of time into the major/minor/patch (major/minor/fix) versioning schema and into defining the difference between alpha, beta, rc just so that the user will know what to expect. It's all about expectations. Would you be surprised if the car salesman tells you the car has turbo but he means a turbo fan for the air conditioner? Or you buy a "lightly used" car and finds out it has 350,000 km and has been run as a taxi for a number of years? A RC - by definition - should be well tested and be quite safe to use. A RC - by definition - should not get code changes other than to fix important bugs and after having done a risk assessment of the implications of the intended bug fix. But there are many hundreds - or more probably many thousands - of examples in LT:s "RC" threads with people who have to roll back to previous versions because the just tested "RC" is not working. Quite often this hurts new users who haven't learned that RC doesn't mean release candidate and assumes it's rather safe to update - and doesn't know how to roll back. It's a question of honesty to use the label "beta" when publishing a beta version. The problem with LT:s labeling is that me and some other people never wants to test LT "RC" versions because we know they aren't RC and we don't want to invest time in hoping that they maybe will work. And since there are no true RC label available, we can't help out with the last testing before final release. The problem here is that LT knows their labeling doesn't match the normal use and regularly fools users into switching to "Release Candidate" software when they shouldn't have. But they are too proud to change their labeling because then they would indirectly admit to having used tricky labeling for a large number of years, and indirectly admit that they have tricked users into running unstable versions in the belief that the software was in a classical release candidate state.
March 11, 20188 yr 3 hours ago, pwm said: We should be, when someone uses a very well defined terminology Nothing of this is really set in stone and some companies use complete different names or strategies for their own purposes. Microsoft ditched the terms "beta" and "rc" altogether, they are now using the terms "insider preview" and "preview" releases, while a company like ZDnet makes use of "perpetual betas" meaning all their releases are always "beta". Confusing, unless you dive into what they really mean with their release strategy! Professionally I work a lot with Cisco equipment. Their release terminology is completely different. Does that make them wrong? Don't think so, but it requires understanding of what they do. If Limetech feels comfortable with their release strategy, so be it. Just my 2 cents. Edited March 11, 20188 yr by bonienl
March 11, 20188 yr 4 hours ago, pwm said: A RC - by definition - should be well tested and be quite safe to use. A RC - by definition - should not get code changes other than to fix important bugs and after having done a risk assessment of the implications of the intended bug fix. But there are many hundreds - or more probably many thousands - of examples in LT:s "RC" threads with people who have to roll back to previous versions because the just tested "RC" is not working. Quite often this hurts new users who haven't learned that RC doesn't mean release candidate and assumes it's rather safe to update - and doesn't know how to roll back. In the years I've been using UnRAID I've spent a good proportion of that time on RC versions, I'm fairly sure there is only one or two occasions where I had to roll back during v5 and not at all during v6. Only reason I'm not on 6.5rc now is I run a pfSense VM that makes updating more of a pain. I've got confidence in LTs processes that they don't release a RC that will screw up on my hardware. With Ryzen, the 'Stable' version had a number of issues with the chips and only the RCs started to solve some of them hence 'RCs' were better than 'Stable'... Quite honestly I don't really care how LT decide to number things - all that matters is they concentrate on the code. Edited March 11, 20188 yr by Interstellar
March 11, 20188 yr On 8/3/2018 at 1:01 PM, nuhll said: as a suggestion it would be cool if the devs would write once a week a small "what we have done|on what are we working". Blog Style post like https://factorio.com/blog/ does every friday (i visit this site every friday just to check out whats new) This would be a good idea Right now I think there is no clear view about the direction and future of unraid. Maybe not every week but at least every month
March 11, 20188 yr 4 hours ago, pwm said: Would you be surprised if the car salesman tells you the car has turbo but he means a turbo fan for the air conditioner? Since you like cars With a car we generally think of it as a transport with 4 wheels, while a motorcycle we generally think it has 2 wheels. Nobody would call a 'motorcycle' a 'car' or vice versa. Now we come with a 3 wheels transport, and yet it can be called either a car or a motorcycle.
March 11, 20188 yr 12 hours ago, realies said: Wait, you keep adding new features with every new RC? Do you realise that you're chasing your tail that way? I am pretty close to the development cycle, and honesty this never happened. There is enough "internal" debate about what goes into a RC. 12 hours ago, realies said: Also, I'd like to update the webGui without having to update the whole OS and restarting. This is something we had in the past, but turned out not a good idea. The few independent GUI updates which were released came haunting us down, because people do upgrades in the most unexpected ways. It is much safer to offer a complete upgrade package.
Archived
This topic is now archived and is closed to further replies.