26.1.r_9 -> to 26.1 official release move ?

[notspam]

Dear opnsense team,

I was interested in the new firewall look and feel  migrate to 26.1.r_1 and update to 26.1.r_9.
Need to manually add firewall rules, but all fine now.

Used the following patches from the other thread:

opnsense-patch ba8194de
opnsense-patch 94081fd82f
opnsense-patch d1519593
configctl webgui restart

opnsense-patch 67668828146e80de49bc6b607db06acb12da8a61
configctl webgui restart

Repository is development.

To get 26.1 final release i will switch the repo to community and get the new 26.1 release then ? Or need I to pay attention to other things ?

Thanks for your time.

[bamf]

Isn't exactly this explained here? https://forum.opnsense.org/index.php?msg=257544

[notspam]

I know this link. There is described the process how to move to the 26.1 pre-release version.
My question concerns the way from pre-release to the final 26.1.
If there is a need to pay attention to hotfixes or something ?
If i move the repo to community the 26.1_r9 is deleted and replaced with 26.1_r1.
So the question is if i should move the repo to community back if 26.1 final is available or is there a need to manually do something ?

[Patrick M. Hausen]

26.1 RC1 is the latest version soon to be followed by RC2 (tomorrow?) I guess. You just stay on "community" and will eventually end at 26.1 release.

This "r9" thingy is an older (!) development version necessary as an intermediate step to perform the switch. You don't want to actually run that. Upgrade to RC1 as outlined in the linked post, stay on community and the rest will be automatic.

[notspam]

Thanks for the clarification.
Switched now to 26.1_r1 and wait for the next releases.