pfSense Gold Subscription

Author Topic: Fix old SNMP bindlan setting - Redmine #3883  (Read 1793 times)

0 Members and 1 Guest are viewing this topic.

Offline phil.davis

  • Hero Member
  • *****
  • Posts: 4612
  • Karma: +550/-3
    • View Profile
    • International Nepal Fellowship
Fix old SNMP bindlan setting - Redmine #3883
« on: November 02, 2015, 11:09:54 pm »
A fix for this for RELENG_2_2 is in PR https://github.com/pfsense/pfsense/pull/2000 - has been there a few days. Maybe it has missed the boat for 2.2.5.
As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

Offline David_W

  • Sr. Member
  • ****
  • Posts: 386
  • Karma: +74/-0
    • View Profile
Re: Fix old SNMP bindlan setting - Redmine #3883
« Reply #1 on: November 04, 2015, 12:00:09 pm »
It looks like the decision has been taken to prepare 2.2.5 for release in the next couple of days: https://github.com/pfsense/pfsense/commit/b31b713d683ecda6940fdba1bd0c4717bcdc0f21 (though there have been some subsequent commits to pfsense and pfsense-tools).

As we both know, Phil, it's impossible to fix every bug. There are so many worthwhile improvements in 2.2.5 as it stands that it's worth releasing. I guess, too, that the pfSense team want to shift their focus onto accelerating the release of 2.3.-


cmb / anyone - is the plan that 2.2.5 is the last 2.2 release unless a serious security issue or erratum arises before 2.3 is ready to release? It would be useful to know, as there is little point submitting further pull requests against RELENG_2_2 once 2.2.5 has released if there is no intention to make any further 2.2 releases.

Offline jimp

  • Administrator
  • Hero Member
  • *****
  • Posts: 21378
  • Karma: +1431/-26
    • View Profile
Re: Fix old SNMP bindlan setting - Redmine #3883
« Reply #2 on: November 04, 2015, 01:34:16 pm »
cmb / anyone - is the plan that 2.2.5 is the last 2.2 release unless a serious security issue or erratum arises before 2.3 is ready to release? It would be useful to know, as there is little point submitting further pull requests against RELENG_2_2 once 2.2.5 has released if there is no intention to make any further 2.2 releases.

That is the plan, though for small but beneficial things we may still accept a PR or put a fix on RELENG_2_2, so long as it's not a binary change someone could use gitsync to pull in things fixed post-2.2.5 even if we don't roll an official release.
Need help fast? Commercial Support!

Co-Author of pfSense: The Definitive Guide. - Check the Doc Wiki for FAQs.

Do not PM for help!