RC1 is finally here

[cyber7]

WOW!

Does this mean I will be able to do a standard upgrade and the rc1 release will be installed/updated?

Kind regards
Aubrey Kloppers

[jimp]

shhh…. it's not quite official yet. Don't spoil the surprise. :)

Assuming this snap checks out OK there will be a signed copy, and an accompanying blog post, etc, etc. Needs some testing and an official blessing.

[Cino]

@jimp:

shhh…. it's not quite official yet. Don't spoil the surprise. :)

Assuming this snap checks out OK there will be a signed copy, and an accompanying blog post, etc, etc. Needs some testing and an official blessing.

I  notice the snapshot missed a couple of last minutes commits. This morning it booted up as Beta5… gitsync and its RC1 ;-)  built on Mon Feb 14 02:12:45 EST 2011

[jimp]

Nothing was missed here that I saw… my home router came up RC1, my amd64 VM came up RC1, my ALIX came up as RC1... no syncing needed.

Though I suppose if you're tracking the ipv6 branch that will still show beta5 until databeestje syncs his repo again.

[johnpoz]

Seem to be having some issues with unbound an RC1

2.0-RC1 (i386)
built on Mon Feb 14 02:12:45 EST 2011

You are on the latest version.

So as it booted up, it sticks on syncing unbound

So I could get into the web ui, and unchecked enable unbound – and web ui just kind of hung there...  I finally restarted via ssh shell, and booted up fine..  I tried to enable unbound -- and again web ui just hung, services says its running, etc..  But just kind of kills the box..  I had to reboot it again, this time disabled it again, rebooted yet again via ssh and this time left it off and just turned on the built in forwarder and clients working again.

I don't have time to play with it at the moment -- reminder do not upgrade to new snap, even if RC1 if leaving for work in a few minutes ;) hehehe

[Cino]

@jimp:

Nothing was missed here that I saw… my home router came up RC1, my amd64 VM came up RC1, my ALIX came up as RC1... no syncing needed.

Though I suppose if you're tracking the ipv6 branch that will still show beta5 until databeestje syncs his repo again.

Didn't even think of it.. That makes sense now… When I manually gitsync, I'm doing both at the same time. So i'm thinking they both merge together..

[jimp]

@Cino:

@jimp:

Nothing was missed here that I saw… my home router came up RC1, my amd64 VM came up RC1, my ALIX came up as RC1... no syncing needed.

Though I suppose if you're tracking the ipv6 branch that will still show beta5 until databeestje syncs his repo again.

Didn't even think of it.. That makes sense now… When I manually gitsync, I'm doing both at the same time. So i'm thinking they both merge together..

They'd probably be clobbering each other, really.

Looks like RC1 isn't happening, back to BETA5. Still having some reports of panics and we can't release an RC that panics.

[Bai Shen]

Bummer.  I was all excited to finally be running an official 2.0 :)

[jimp]

nothing is official until it's official :-)
It was just a normal snapshot labeled RC1… If it worked, it would have been signed and put up, then it would be officially RC1. But still not a -RELEASE

[Tamriel]

good job :)

[AhnHEL]

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/ad67f6af4b739d75e8a20e078a505b6aea9bbf51

Back to Beta5  :(

[Cino]

@onhel:

https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/ad67f6af4b739d75e8a20e078a505b6aea9bbf51

Back to Beta5  :(

note Beta5 but 2.0-BEAT5

there's a typo

[AhnHEL]

Easily fixed