Hello,
Suggestion: group interfaces (for using these groups in Rules)
i.e.: put eth1 and eth2 to “Internet_interfaces” group, and put eth5 and eth6 to “Local_interfaces” group, and use groups in Firewall Filter Rules.
I’d love this as well - it’d make it much easier to define rules involving large sets of interfaces, which currently involves a ton of rule duplication.
Already implemented…
http://forum.mikrotik.com/t/v6-36rc-release-candidate-is-released-wireless-fp-package-is-discontinued/97337/94
And… the reason to switch from Bugfix to Current is here.
It depends on how brave and skilled are you. Like always stability and functionality could be very painful tradeoff.
As soon as this makes it in to “bugfix” we are going to upgrade all our routers from 6.19
This is a “killer” feature 
Seeing the 6.32.x to be still held as bugfix for the long time (that I personally do appreciate) and this feature to be firstly introduced in actual release candidate, I am afraid it will take some not short time till 6.36 becomes a bugfix… But with mikrotik none knows. Things can change very quickly..
This shows you why a real feature release branch is needed, in addition to the beta-level Current.
and here we go again… there are no such thing as version that is bug free and contains new features… Most of the bugs in software are introduced while introducing new features. Only way to ensure that this feature works correctly with your configuration when released in “Current”, is to install RC on some test network and check it.
If anyone could make bug-free releases all the time … what a world that would be
let me modify this explanation a little bit:
- bugfix contains no new features, therefore is very stable
- current does have new features, and even though we test hard, we can’t be 100% sure
- RC contains new features and was tested for a few hours before we release it, will absolutely contain some unexpected issues as well
IMHO, this is an excuse. Just look at the few comments above.
It is not that Current has some bugs, but that it is not considered safe enough.
The process is the problem.
Just look at it this way - You should stick to “Bugfix only” (aka Stable). New features come in alphas, betas, and other test versions. Ignore features that are not inside “Bugfix only”
The process is not so much bad. Just too many people don’t understand it well. Seeing normis writing that the bugfix is “stable” in comparison with current to be called officially as “stable” is also pointing at the nonunific meaning even on the side of mikrotik people. Or the things are slowly moving forward and this is just some transition phase? I hope so. From my point of view only the bugfix is stable enough to get the “stable” label.