How do I get from production to git master?

[Tupsi]

I am was happily running the production version 20.1.3 until I had the questionable idea of adding ULAs to my lan, so I can have static addresses for accessing services like pihole in my LAN while still getting the not so static v6 addresses (grrr) by my provider german telekom.
After lots of trying and googling around I finally found out that virtual ip is the thing I can tag another ip address to my opnsense interfaces and things started to work, well until my provider throw a new ipv6 prefix at me. Took me a while to figure out, that I had not done anything wrong, but simply found a bug in how  opnsense handles the transition from one prefix to the next.

I thought that I am even on the bright side of live, when I found a lengthy git hub entry (#3310) already closed, with changes merged to master.

Then it struck me that git master != production when it comes to versioning git vs. opnsense and now I am wondering how I would get from my production version to master.
The firmware settings only have options "production" and "development" and I am now wondering if "development" is actually git master or something completely different.

Normally I would sit patiently until that change hit production, as a good clueless user should do :-), but the milestone named 20.7 and a date of july near it lets me worrying it could be quite a while until that change makes it way into the production branch.

TLDNR:
1) Is there an estimate time frame usually master gets to a production tag?
2) How can I configure my opnsense to use git master instead of production?

[Tupsi]

I just noticed last night, that the changes for #3310 got commited into the 20.1 label, so I would assume this will find its way through the normal distribution of biweekly updates into the 20.1 stream? Which should be 20.1.4, right?

So there is no point for me it seems to switch to a dev built, having patience for two weeks seems to be the theme of the time atm anyway 

[Maurice]

- "Development" in the firmware settings switches to the current development snapshot, which is not the same as git master.
- Upgrading to git master is only possible on the console (by pulling the sources directly via git). The details are in that lengthy #3310 discussion. :-)
- It seems the fix for #3310 should be in 20.1.4, right.

Cheers

Maurice

[franco]

Development already has the changes from #3310. And indeed 20.1.4 will have them as well. No need for git magic in the meantime.


Cheers,
Franco

[Tupsi]

Thanks guys for clarifying this, so I just sit tight for that next version.

Stay healthy!