[xasop]

SMF released a new version a couple of weeks ago. I've pushed the changes to our upstream branch on GitHub, but after reading through them and the changelog, I've decided not to upgrade.

That diff should speak for itself, but in case it doesn't, it contains at least as many (probably accidental) reversions and errors as improvements, and there are no security fixes to worry about. Until SMF makes another release that is actually going to be beneficial to us, we're better off sticking to 2.0.7 with our own improvements.

[fappenhosen]

Why are you pushing code you dont want and wont use?

[xasop]

Why are you pushing code you dont want and wont use?

For two reasons: I like to keep our upstream branch up to date with upstream releases, even if it doesn't get merged into master right away; and since upstream has no public revision control, this is the only way I can easily share diffs between versions with others (such as pizaaplanet) so we can discuss what to do.

[fappenhosen]

upstream has no public revision control

OK. Wow.

[Pete Svarrior]

Welcome to SMF

[xasop]

Most of our concerns regarding SMF 2.0.8 have been fixed in 2.0.9, which was released just a few days ago. As such, we've now upgraded to the latest version.