It is disappointing as I’ve previously only really posted in the private boards but the length of time to release such an important update to enable running HTTPS without a whole bunch of errors really does make it hard to justify continuing running SMF.

Hopefully it arrives before October when Chrome will declare all HTTP sites as insecure, login form or not.

Thank you for your thoughts. In the end we are a team, and everything we are going to do is previously discussed with everyone. We have some informative topics already done, but we have decided to wait for the best moment to publish them.

We beg you for patience. Please remember we're all volunteers. Probably 2.0.14 would have been published a long ago with all developers working altogether, but unfortunately is not like that because of real life matters.

And please stop asking about 2.0.14. This topic is about 2.0.13 and its release.

And please stop asking about 2.0.14. This topic is about 2.0.13 and its release.

Yes, yes it is, and people find the release lacking because the things that external forces deem necessary are finally pushing SMF to fix things.

If it helps rationalise it, every person who is pushing for 2.0.14 is expressing the fact that 2.0.13 has some major gaps in it.

The fact that people with the skills and time have indicated a willingness to help fix the problem only to be given a highly cryptic and unhelpful response is part of the problem.

And unfortunately the 'we're all volunteers' card doesn't carry enough weight when peoples' sites are losing members because of continuously deferring a problem until it's someone else's problem - this situation with 2.0.14 was a known issue in 2014 (hah). Every release from 2.0.8 onwards was an opportunity to lay the groundwork for dealing with this issue. Including 2.0.13.

You want to talk about 2.0.13 rather than 2.0.14? Why didn't SMF tackle this problem in 2014 or even throughout the bulk of 2015 before it would have been a problem? Why is it now, 18 months after 7.0 released, that it's finally being dealt with? Because no-one in that time could possibly have said 'maybe we should fix this'?

Logged

Don’t try to tell me that some power can corrupt a person. You haven’t had enough to know what it’s like.

Arantor... except the problem - in this case - is not something that needs to be addressed by those people...

The biggest delay in getting this out is the coordination necessary for 2.0.x releases at this time, given the systems involved - as has been evident with the problems (not with code, but with the release process itself) for the past 4 releases.

Logged

Please do not PM, IM or Email me with support questions. You will get better and faster responses in the support boards. Thank you.

Funny, the last update in this thread is that there was still an issue outstanding to be looked at, except when I asked what it was, I got only a cryptic link that didn't actually seem to be a relevant issue.

It's also interesting to note that as far as I know the release process hasn't changed in forever... why is that an issue now?

Logged

Don’t try to tell me that some power can corrupt a person. You haven’t had enough to know what it’s like.

It's an issue because the release process HAS changed... as evidenced by the issues with the release process in the last 4 releases.

To be clear, the remaining issue (solved) was regarding a specific situation with proxy avatars which we didn't note initially but encountered, identified and fixed after some additional testing. However, identifying and fixing that issue meant that we had to rebuild the release, retest and confirm that the release process would not "suck in" the previous candidate that had been replaced (which was what happened with more than one of the previous 4 releases)

Logged

Please do not PM, IM or Email me with support questions. You will get better and faster responses in the support boards. Thank you.

The proxy issue was fixed and we even silently updated the test patch we have here to keep testing. However a bug was discovered regarding search results and the proxy for https. Devs are busy with real life and haven't had a chance to dig into what caused that issue (and neither have I).

Again, this update changes a lot of stuff and we are wanting to carefully test it to not find any bugs, like said bug. The bug from my quick testing is only showing in 2.0, and hasn't affected 2.1.