A1 A2 A3 A4 A5 A6 A7 A8 A9 A1 A2 A3 A4 A5 A6 A7 A8 A9 A10 A1 A2 A3 A4 A5 A1 ...
B1 B2 B3 B4 B5 B6 B7 B8 B1 B2 B3 B4 B1 ...
RC1 RC2 RC1
R R
Test before you deploy! Always! No exception!1. People who make their systems unbootable on Current
What's wrong with this? How on earth another beta stream will make it better?2. Individual users like me who stay on Bugfix and never try Current because they are too scared of messing their setup (which means less people testing Current for smaller problems).
The forum is here for people to complain. Happy users rarely post success stories here. Having read some complains on the forum, clever people test twice before they deploy.3. Potential customers who read the forum and see the complaints of 1.
Yes, Bugfix release may still be broken for some users. There's nothing anyone can do. Period. Another beta stream won't guarantee that it will work for everyone as expected. Let me repeat again: test before you deploy.4. People who are afraid that a future Bugfix might be borked
That's just a question of naming. You just have to get used to it, since there's no single naming conventions that satisfy everyone. For me, for instance, as a long-term FreeBSD user, "CURRENT" means bleeding edge, but YMMV.Current is not supposed to be beta. People here still don't understand this. RC is a duplicate of a good beta, and Release is a duplicate of a good RC.
I don't know what you do for a leaving. My primary job is software development, and I surely know how this industry works. I may assure you that each additional branch that you need to keep stable and not outdated at the same time is a log of effort. And there IS additional development. To expose something, you need to have this something. And complexity grows exponentially with each additional release branch that you need to maintain.There's no additional development, just more controlled exposure.
Retiring Bugfix early is not necessarily a good thing. The current Bugfix branch is stable for (roughly) half a year already, and I won't find enough words to express how happy I am.If people feel safe enough about moving to Current, there will be more testing, and it will be possible to retire Bugfix versions earlier.
Again, that's just a matter of naming. If you don't like the current naming it does not mean the naming is bad. It just means you don't like it.Current is a bad name invented by Miktrok. It is supposed to mean Feature, not Beta.
Real RC and Release are not development cycles, they are distribution cycles.
Look at the Current threads, they cycle rapidly with serious errors. This is not the way it's supposed to be. This cycling is supposed to happen in a beta cycle, with the people subscribed to a Feature release being guaranteed of no drama.
Bugfix is not supposed to be stable compared to Current. Current is also supposed to be stable. The difference is that in Bugfix regressions to older functionality are unacceptable too.
If Current is guaranteed to be a safe release, then it will be a good name.
You said it all right there. Stick to the Bug Fix releases and quit whining. Or buy a Linksys or something that you can Tomato on. Then you can have a specific beta name.I don't have another Mikrotik, and as a home user I am not supposed to test in a lab first.
Bingo.MikroTik's RC = alpha/nightly/...
MikroTik's Current = beta/testing/RC/...
MikroTik's Bugfix = release/stable/...
This ... I need stability, not features. Just give me a bugfix. When a new feature has been out for year, okay, I'll bite then.There is supposed to be a release for people who need new features and another for people who need absolute stability.
when was that? last i can remember is 6.17some releases are completely broken.
With an attitude like that, no scheme will satisfy you.The problem is that you're not giving up a little stability with Current, some releases are completely broken.
LOL, have you been around this forum when V6 just become active? 6.0 -6.17 ?? Then it was problematic, now those topics are ideal. Since introduction of new release system, everyting is fine or ideal with current and bugfix, at least from my point of view.Look at the Current threads to see what I mean.