What is it? 25.11.a.20250916.0600
-
@dennypage said in What is it? 25.11.a.20250916.0600:
Dev build for 25.11:
https://forum.netgate.com/post/1225827
The .a is an alpha release AFAIK.
-
It seems its an dev alpha test version for the upcoming November release.
Quite early, judging from previous experience, but its nice to see progress.
Most probably the alpha release was initially published as a stable channel update, thus we saw it everywhere.
Its now fixed and one needs to switch to dev snapshots to see it. -
Hmm, yes that is the first available dev snapshot for 25.11. It should not be offered as an upgrade unless you go hunting for it. Digging.....
-
Is anyone still seeing this? I can't replicate it on anything currently, I believe it's corrected.
-
@stephenw10
It was a transient.
It appeared for about an hour in 2-3 plus systems, and then it disappeared silently.I don't see it anywhere anymore
-
Cool. Thanks for the update.
-
Thanks for the report. It wouldn't appear on the dashboard by default. However it will show up there if the config had a previous development branch selected. An easy way to fix that is to go to System > Update > Settings and save the release branch selection.
-
@marcosm That was the concern, that branch wasn't selected. Unless you mean "ever," as in, maybe "years ago."
Edit: gosh I wonder how old this config is. QuickBooks has a file history going back to QB for DOS. Just sayin'. ;)
-
@SteveITS If devel was saved previously and then never re-saved with the release branch. Alternatively there was a period of time where the saved branch was ambiguous between releases and a saved branch during that period could potentially result in the same behavior - the fix being the same, just resave the release branch.
-
S SteveITS referenced this topic
-
D dennypage referenced this topic
-
@marcosm said in What is it? 25.11.a.20250916.0600:
@SteveITS If devel was saved previously and then never re-saved with the release branch. Alternatively there was a period of time where the saved branch was ambiguous between releases and a saved branch during that period could potentially result in the same behavior - the fix being the same, just resave the release branch.
Well, as far as I remember when latest stable was released, there was no other branch to select, (or save )
I do remember checking this.
So yes, if those instances where on beta (which they were) and then that changed to stable and upgraded, that caused the alpha to re-appear.
Now that there are two branches available, one can save on stable and not see devel versions.
It's a quirk affecting those fiddling with pre release versions, but then, those guys supposedly know what they are doing. (or maybe not
) -
S SteveITS referenced this topic
