What are the road signs we're getting close to a released version of 2.6?

[jsmiddleton4]

Being a new guy just wondering what do we look for in terms of road signs that indicate we're getting close to the beta becoming a "released" version?

Not asking for anything to be hurried. Patiently awaiting for the birth a "released" version.

I've not been along for the ride from a beta to a released so have no idea what the process looks like.

[fireodo]

@jsmiddleton4

https://redmine.pfsense.org/projects/pfsense/roadmap

[jsmiddleton4]

@fireodo

Thanks but there's no date for 2.6 and not exactly what I was looking for.

[johnpoz]

@jsmiddleton4 There has been an announcement that 22.01 would release this month via a tweet and via email newsletter. Which mentioned an upcoming blog about it. And well its kind of in its version number ;) They had to push back the schedule 21.09 release, I doubt they would be happy about pushing this release back, etc..

It would prob be not such a stretch to believe 2.6 would be somewhat inline with that release. And I would "guess" they will prob make mention when they do the blog post.

But as it has always been with pfsense, it will be released when its ready.

[jsmiddleton4]

@johnpoz said in What are the road signs we're getting close to a released version of 2.6?:

it will be released when its ready

Would expect nothing less.

I watch the bug report. Do they wait until all of them are squashed?

[emikaadeo]

https://github.com/pfsense/pfsense/commit/f1654805093967aafaa13705d13cc8ffd7d322d4

[jsmiddleton4]

And just like that, there’s 2.7.0……

[jdeloach]

@johnpoz

@jimp mentioned in another post here 2 or 3 weeks ago, that it was expected that 2,6 would be released shortly after the first of the new year which I interpreted to mean probably around the end of January. But as always I'm sure he meant when it was ready.

[NollipfSense]

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

And just like that, there’s 2.7.0……

I am expecting 3.0 next...

[Gertjan]

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

And just like that, there’s 2.7.0……

As 2.6.0 gets prepared and earns it's "RELENG_2_6_0" branch name, the new master is also created == the same code at that moment.
The "RELENG_2_6_0" code branch won't get touched any more, new development will get pulled in to 'master'. 'master' will be ahead of "RELENG_2_6_0" very soon.

[jsmiddleton4]

@gertjan

So 2.7.0 is not 2.6.0? 2.6.0 will be the next "released" version? If 2.6.0 has been stable stick with it and in a bit there will be a released 2.6.0?

If you want to continue beta testing "hope it doesn't crash", move up the food chain to 2.7.0?

[Gertjan]

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

So 2.7.0 is not 2.6.0? 2.6.0

See here : https://github.com/pfsense/pfsense

Click this button :

You find

and also entry called master - master is the working set, and could be 2.7.0 or, 2.6.x in the future.

Just a couple of seconds ago a new commit was applied to the master :

so 2.6.0 is now officially "in the past" :

[emikaadeo]

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

So 2.7.0 is not 2.6.0? 2.6.0 will be the next "released" version?

Yes.

[JeGr]

@nollipfsense said in What are the road signs we're getting close to a released version of 2.6?:

I am expecting 3.0 next...

I'm not. Why should it?

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

And just like that, there’s 2.7.0……

That was expected. Spoke with multiple customers the last day and was already telling them that with the impeding launch auf 22.01 targeted at the end of the month, we'll very likely see a timely release of 2.6 with it. We were already told last year, that with 21.09 or 22.01 there will be an update path introduced from CE to Plus and a possibility to run Plus on non-Netgate hardware so a "fast" 2.6 release is no surprise to anyone who paid some attention ;)

Only thing that is still missing is a 2.6-RC branch to switch those dev-boxes to, there's only development going to 2.7-dev now but we'll likely see it popping up the next few days I suppose.

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

So 2.7.0 is not 2.6.0? 2.6.0 will be the next "released" version? If 2.6.0 has been stable stick with it and in a bit there will be a released 2.6.0?
If you want to continue beta testing "hope it doesn't crash", move up the food chain to 2.7.0?

Huh? No, 2.7 is the new "rebased" devel tree. That moved to 2.7 as 2.6 gets ready for RC state. If RC is successfully tested and stable it gets released alongside or in the vincinity of 22.01-Plus. That's the normal dev flow. Devel goes to Beta goes to RC goes to live/prod. And 2.6 has left alpha/dev and beta now and obviously gone ReleaseCandidate state. As no one knows whats's the plan with 2.7 (rebase to FreeBSD 13? Stay on 12.3?) I'd not follow that Branch with a production box.

So nothing out of the ordinary here :)

Cheers
\jens

[jsmiddleton4]

@jegr

I didn’t say anything was out of the ordinary. I’m trying to clarify what IS ordinary.

I’ve gone to 2.7 thinking it was a 2.6.0 with improvements.

Apparently that is not exactly the case. 2.7.0 is a new family member.

[bmeeks]

@jsmiddleton4 said in What are the road signs we're getting close to a released version of 2.6?:

@jegr

I didn’t say anything was out of the ordinary. I’m trying to clarify what IS ordinary.

I’ve gone to 2.7 thinking it was a 2.6.0 with improvements.

Apparently that is not exactly the case. 2.7.0 is a new family member.

Yes, back some time ago 2.4.5 was the RELEASE branch (RELENG_2_4_5 was the official branch name) and 2.5 was the Development Snapshot (also known as "Master"). Then one day the 2.5 development branch ("Master") suddenly became the new RELEASE branch (RELENG_2_5_0), and the previous RELEASE branch, 2.4.5, became deprecated. And what was originally 2.5 (or the development snapshot "Master" at that point in time) was renamed to be "2.6", and became the new "Master" development branch.

So on the date and time the rename discussed in this thread happened, 2.6 and 2.7 were identical code branches. At the point of renaming, though, 2.6 becomes basically frozen as the new RELEASE branch (first as RC, or Release Candidate, and then finally as RELENG_2_6_0 when it goes full production). And the 2.7 branch becomes the next Development Snapshot and is where future development work continues to happen. So 2.7 is now the Development Snapshot, and 2.6 is about to become the new Release.

That's not to say a few additional changes won't get into 2.6. If RC testing finds a major bug, then obviously that would be fixed in 2.6. But by and large future software changes are going to be continuing in the 2.7 branch while the 2.6 branch is about to become the production CE RELEASE.

[jsmiddleton4]

I’m not finding any easy way to back out of 2.7.0 back to 2.6.0 other than save config.xml, local.conf file, etc. Install 2.6 clean, put config files back.

[bmeeks]

@jsmiddleton4
For now that is probably the only way. Eventually, once 2.6 officially becomes RELEASE, I think you will be able to swap back in the Update menu.

But if you want to revert now, I would go the reinstall and restore config route.

You sort of "upgraded" at a bad time as you got in the in-between period where 2.6 is becoming RELEASE and the DEVEL snapshot branch is getting renamed to 2.7. So 2.6 is going to be 2.6-RC (Release Candidate), and what was formerly called 2.6-DEVEL is now renamed to 2.7-DEVEL.

[jsmiddleton4]

@bmeeks

Thanks. It feels like 2.6.0 release coming soon so will wait a bit.

[NollipfSense]

@jegr said in What are the road signs we're getting close to a released version of 2.6?:

I'm not. Why should it?

Well, I had read awhile back (during 2.4.5 days) that the next release after 2.5 would be V3.0 and it makes sense currently at the pace things are going as FreeBSD 13 is now considered very stable and we have things that should have been or had been originally planned for v2.5 still in the table, such as REST API.