Road to v1.0.0 - the first stable release! (Comments welcome until Monday October 26th!)

[2GT-Rich]

Hi all,

MikroTik Manager has grown fast over the last few months, and a lot of that is thanks to you: the bug reports, feature ideas, testing, and pull requests. Thank you.

Spurred on by some recent conversations, I think it's time for the first stable release. The scope below is set. What I'd like your help with is the timing: I'll set the dates once I've heard from you.

The following items will be completed BEFORE v1.0.0:

• VLAN interfaces on the VLANs tab, read-only (VLANs tab: show /interface vlan entries (VLAN interfaces on a physical parent), not only the bridge VLAN table #309)
• An IPv6 routes tab, read-only ((Feature Request) IPv6 routes & firewall #312)
• The legacy wireless security fix ((Bug) - Neighbor Network Security (Open) #295)
• Firewall Events (feat: add RouterOS firewall event monitoring #314), if it's ready and reviewed in time. If not, it's first in line after v1.0.0.

After v1.0.0

These are good ideas, and they're happening, just not in this release:

• Finer user roles and permissions ((LF Feature Reguest) Risk Mitigation #307)
• RoMON checks and setup ((Feature Request) - Setup RoMON on managed device #311)
• IPsec, PPPoE, EoIP and Netinstall views ((Feature Request) Network Services (IPSEC,PPPoE,EOIP,Netinstall)) #310)
• Editing the IPv6 firewall ((Feature Request) IPv6 routes & firewall #312)
• Major dependency upgrades

Before v1.0.0 there will be release candidates: test builds with no new features, only fixes. If you update from main, you'll get them automatically.

Three questions

1. Is there anything you'd consider a must-fix before you'd call MTM stable or run it in production?
2. Can you test the release candidates on your fleet? Roughly how many devices, and what kind?
3. How much time would you need to test a release candidate properly, and is there anything in flight that needs a bit longer?

Please comment here by Monday, 26 Oct.

Thanks again for everything you've put into this.

Rich

[2GT-Rich]

A scope update: RoMON (#311) is moving into v1.0.0.

The reasoning:

• It is a safety net rather than a convenience. RoMON is the way back into a router when its IP path breaks, and it only helps if it was switched on beforehand. The best time to catch devices where it was forgotten is before people trust MTM with their fleets.
• @dlemery said it would save his team a lot of time, which is exactly the kind of production need this release is meant to meet.
• It is small and low risk: it builds on pieces that are already done (sites, groups, the security checks and Change Guard), and it only changes a device when someone presses Apply.

It is already in v0.73.0 if you would like to try it: set a RoMON setting on the Sites page, and the Security page shows which devices differ.

Alongside it, two small additions: a warning when a device has no IPv6 input firewall (from @dlemery on #312), and making the Security page fast on large fleets. Everything else on the "after v1.0.0" list stays there.

[kraken-XIV]

1. Nothing particular to add right now.
2. Yes I can, my truenas custom app updates with every release (including beta's).

• RB5009UPr+S+ · ROS 7.25rc2
• CRS310-8G+2S+ · ROS 7.25rc2
• CRS305-1G-4S+ · ROS 7.25rc2

3. 4-5 days to be able to really sit down and go through things.

[2GT-Rich]

v1.0.0-rc.1 is out, and the feature freeze starts now.

Thanks for the input over the past week. Everything planned for 1.0 is already in, so I'm keeping this simple: one release candidate, a week of testing, then stable.

Timeline

Date	What happens
Sun 25 Oct	Feature freeze. v1.0.0-rc.1
Until Sat 31 Oct	Testing. Please report anything that looks wrong as an issue
Sun 1 Nov	v1.0.0, if nothing serious turns up

Small fixes go straight into 1.0. If something serious turns up, the date moves until it's fixed rather than shipping with it.

Updating

If you update from main or run the :latest images, you'll get the RC with your normal update. Take a platform backup first (Settings → Backup & Restore). What's in it and how to upgrade: release notes

After 1.0

main and :latest become the stable line: 1.0.x, fixes only. New features move to the dev branch and :beta images as betas of 1.1. If you want stable, there's nothing to do. Details: release channels

New feature requests are still welcome. Anything that comes in now gets the post-stable label and goes into 1.1.

Testers

@kraken-XIV, thanks for offering. @dlemery, @rvanderwouw, @trackersoft, @ronchan44: you all run real fleets, and an hour on the RC this week would help a lot. If anything looks off, open an issue.

Thanks, everyone.

Rich

[2GT-Rich]

v1.0.0 is out. It's the first stable release of MikroTik Manager.

Thanks to everyone who tested the release candidates this week. Nine went out, with fixes from real fleets: NetFlow behind NAT, client and CAP placement, CAPsMAN controllers, spanning tree across sites, and a few more. Special thanks to @azizfayziev for testing almost every one of them across his sites.

Updating

If you update from main or run the :latest images, your normal update brings 1.0.0. Take a platform backup first (Settings → Backup & Restore). What's in it and how to upgrade: release notes

What happens now

• main and :latest are the stable line. Updates on 1.0.x only fix things.
• New features go to the dev branch and :beta images as betas of 1.1. If you want stable, there's nothing to do. Details: release channels
• Everything labelled post-stable is the running list for 1.1. Pull requests for new features should target dev.

If anything looks wrong on 1.0, open an issue and it'll get fixed on the stable line.

Thanks, everyone.

Rich