1.2.1 release schedule

If you follow Scott’s twitter, you’ve seen our plans for the 1.2.1 release. This weekend will see the last RC, and the final release will come as a Christmas gift to the community.

Share this Post:

8 Responses to “1.2.1 release schedule”

  1. Kevin Bowling Says:

    Excellent! Sometimes I think you guys are too timid on releasing, 1.2.1 has been in good shape for a while :-).

  2. Chris Buechler Says:

    I agree, Kevin, we could have released this quite some time ago. We’re very conservative with our releases, perhaps too much so in this case. We just want to be completely sure that there are no regressions when we label something as a stable release, and at this point we’re already confident of that from the wide scale deployments of 1.2.1 over the past several months. We decided to give it one more RC, though we’re already confident that RC2 is a stable release.

  3. Belthazar Says:

    Will be the best Xmas gift in years! Thank you for the relentless effort & dedication in growing pfSense.

  4. joseph karma Says:

    Keep the good work guys.
    Just a question from a newbie: RC-2 had a bug on the snort package. Is it corrected on RC-3?

  5. Jonathan Says:

    We use a large ERP suite that errs too far on the other side. We often see regressions, and things that surely couldn’t have passed basic testing. So for our part, we wholeheartedly support the pfsense approach!

  6. Chris Buechler Says:

    Joseph: Packages are not part of the base system, they are completely independent from any releases and are updated individually on their own.

  7. Dennis Says:

    Thank you thank you…

  8. Dominik Says:

    The checksum files at http://snapshots.pfsense.org/FreeBSD7/RELENG_1_2/ for the RC3 are a little bit damaged.

    You can find something like this:

    SHA256 (/usr/obj.pfSense/pfSense-1.2.1-RC3-20081213-0649.iso.gz)

    I think there should be no absolut path in this file.

    Now I am going to install the RC3 on my new Soekris net5501 and test pfSense before the final release.

Please don’t post technical questions or off-topic comments. It is far more likely that your questions and concerns will be addressed effectively through one of our support channels.

Leave a Reply