How will firmware 7 be distributed , manual installed or automatic

Hi

I have some routers that have a script that updates to the latest firmware, will this include upgrade to version 7.

//ToLi

You are asking whether your script will be able to upgrade? Only you can answer that question as an author of the script.

I would read this question as asking, if the following is run, will the router update to ROS7?

/system package update

Also unknown. It depends which channel you have selected.

[normis@Home] /system/package/update> set channel=
development  long-term  stable  testing

v7.1 is in development channel

Thanks Normis. OP asked how will v7 be distributed. I assume he’s asking if this will auto update after release, or if this will be a manual deployment.

For example, if update channel is set to long-term, will v7 at some point enter this channel and result in a v6 router updating to v7?

This is something that also interests me.
I am currently in long-term at home and I was considering moving to ROS7.
If I just set the channel from long-term to development, and click Download&Install will I get ROS7 with the same config as with the long-term, or the only way to do this is by netinstall?

Regards.

The same way as you upgrade v6. Select channel or upload packages manually and reboot.

Yes, but this is not exactly what the OP asked. He wants to know if a script that is set to “stable” or “long-term”, running on a router with RoS 6.x, will upgrade to version 7 automatically.

Put another way: will v7 become an automatic update (like 6.44.1 → 6.44.2)? Or will be created a new train, just for v7?

Something like:
stable (v6)
stable (v7)
long-term (v6)
long-term (v7)

What behavior should we expect from an automatic upgrade script, that updates the router to the latest stable version? Will it keep to v6? Will it jump to v7, when stable?

The question includes the answer. Of course, if there is a script, that automatically upgrades to the latest version in “stable” branch, it will also upgrade to v7.1.x whenever we put it into that branch. We will only put it there, when it’s stable enough. Not soon.

Hello
I suggest to make a separate train, example long-term7 stable7, etc
because we have thousand of deployed mikrotik with the long-term set.
many older devices may have issues upgrading to 7 so it should be an intelligent set, to make separate ros 7 channels.

Like I said, we will not put v7.1 in the stable branch any time soon, that is not the plan.

@Maggiore81, I would hope that with several thousands of deployed MikroTiks that you do not have them all set to upgrade automatically to the latest long-term. It is a much better option to use something like TR069 to handle updates in this case.