Just a polite reminder that the bugtracker exists, and is where all things that you think of as bugs (or rough corners) should go. E-mail, IRC and other mediums are always tempting as being “faster” or more readily available to gain responses, but they are absolutely hopeless for scheduling things and keeping track of what actually needs to be done.

Don’t be too afraid of reporting something unnecessarily: it’s easy to close a bug. It’s a lot more worrying that a bug might be going unnoticed because someone forgot they saw a mention of it on #inspircd.

Thanks!

Hi all,

After a bit of discussion, we’ve decided to close the 2.1 branch, as the general consensus is that we aren’t comfortable with the state it is in regarding release-readiness, and unfortunately, the people working on it have more or less been eaten up by the real life monster.

As a result of this, we’re closing the 2.1 branch, and won’t be working on it anymore (it’s been renamed obsolete/insp21 in git), and we suggest you don’t use it.

Not much more to say here. Downloads are available from the usual location. A big thanks to Robby and Attila for their contributions to the release, thanks to other authors also.

Users of the 1.2 series are suggested to upgrade.

InspIRCd v2.0.6rc1 has been released, fixing the CERT DNS vulnerability, amongst other things. All v2.0 users are strongly recommended to upgrade. v1.2 users should start considering the 2.0 branch, as 1.2 is now entering the last phase of support.

InspIRCd 1.2.9rc1 released!

InspIRCd 1.2.9rc1 has been released. Networks running the 1.2 branch are advised to upgrade immediately; as it fixes a number of potentially serious issues, including the recent CERT DNS vulnerability. Please note that, unless severe issues are found in the future or a new maintainer found, 1.2.9 will be the final release in the 1.2 series. If you are interested in maintaining it, please get in contact, or start to consider upgrading to 2.0.