pfSense Forum

Administrative => Messages from the pfSense Team => Topic started by: jimp on February 20, 2017, 08:37:09 pm

Title: pfSense 2.3.3-RELEASE Now Available!
Post by: jimp on February 20, 2017, 08:37:09 pm
https://blog.pfsense.org/?p=2325
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: Ecnerwal on March 09, 2017, 10:11:49 am
Oddity - I upgraded one of my two systems to 2.3.3-release and it has been saying it's on the latest version.

Today I noticed that it's saying:

Quote
2.3.3-RELEASE (amd64)
built on Thu Feb 16 06:59:53 CST 2017
FreeBSD 10.3-RELEASE-p16

The system is on a later version than
the official release.

Which puzzles me, rather.
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: arnoldo0945 on March 09, 2017, 10:56:39 am
https://forum.pfsense.org/index.php?topic=126523.0
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: pfSense4ME on March 09, 2017, 12:59:56 pm
Hi

Here's what I can't understand...

Previously when a version of pfSense reached release status, the version that was listed as a development snapshot was retired and moved to the retired section.  pfSense 2.3.3 has been released for some time now but the 2.3.3 Development Snapshots still remain in the pfSense English Support.  Is pfSense 2.3.3 released or still beta?


Not trying to cause a war, I'm just curious and confused.
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: jimp on March 09, 2017, 01:09:02 pm
2.3.3 has been released, which is obvious given we announced that publicly on the download page, blog, forum, social media, everywhere.

We just forgot to move and lock the board. That's been done now.
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: JorgeOliveira on March 16, 2017, 04:07:45 pm
Hi,

I've noticed 2.3.3-RELEASE-p1 has been released, but the GitHub repositories do not yet have a tag for that version.

Please fix! Thanks.
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: kpa on March 17, 2017, 08:04:05 am
Not sure why you need the tag but this is probably the commit:

https://github.com/pfsense/pfsense/commit/d149a31622ece53fb5c0a47a0133bf92a8daaef9 (https://github.com/pfsense/pfsense/commit/d149a31622ece53fb5c0a47a0133bf92a8daaef9)
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: phil.davis on March 17, 2017, 08:42:25 am
On my 2.3.3-p1 test VM:
Code: [Select]
[2.3.3-RELEASE][root@pfSense.localdomain]/root: cat /etc/version.lastcommit
5aa1ac92fddc845eb69d2283a5378b6231b4d1d6
So the actual last commit is:
https://github.com/pfsense/pfsense/commit/5aa1ac92fddc845eb69d2283a5378b6231b4d1d6 (https://github.com/pfsense/pfsense/commit/5aa1ac92fddc845eb69d2283a5378b6231b4d1d6)

Is it happens, there was a commit which was added then reverted after the one that @kpa has pointed to. So both tag points would make effectively the same code base.
Title: Re: pfSense 2.3.3-RELEASE Now Available!
Post by: jimp on March 17, 2017, 09:55:26 am
The tag was done locally but hadn't been pushed out yet. It's there now: https://github.com/pfsense/pfsense/tree/v2.3.3_1