Wedge

The main reason XF is 5.2.4 is because of its dependencies with respect to Zend Framework components. (Please, dear god, never let us go down that road. That road is the path to madness, from experience.)

Anyone using 5.2.x should be using 5.2.17 on a production environment unless they know for certain they're using a 64 bit build of PHP, otherwise they are at trivial risk of DDoS from floating point mishandling.

One of these days you're going to read what I've written and actually take note of the words I've used. If you admired our work half as much as you claim to,

1) you wouldn't have demanded access to the source code pretty much off the bat, but understood that this was us doing what we wanted to do first and foremost, and not building it to meet your goals,
2) you wouldn't have spent so much time trying to impose your ideas on how we want to build it and trying to tell us how to implement things, as though we're newbie programmers, and
3) you wouldn't have asked for a download just because SMF was out... no-one else has asked because everyone else took the time to read what's written and realised that there wasn't a download already.

Also, there's an implied 4) if we do give you a download, which we're not going to until we're ready, we will spend an awful lot of time catering to your questions about how it works, and how you want to change it, when how it works is in a state of flux and that your changes are specific to your site, which means that we're only going to be burning more time helping you instead of benefitting everyone.

As it is I've wasted far too much time and energy trying to explain to you what everyone else seems to have already understood.

I think in Unknown's case, he'd just moved on. Don't know about Jeff though, and I haven't spoken to him in ages (probably longer than when I last spoke to Unknown, really)

Ultimately, so do we have that uneasy feeling. The public image is that 2.0's finally out and they can get on with 2.1 but honestly, I'm not convinced that 2.1 will be anything special, likely it'll fix some of the bugs they pushed back from 2.0.

No, that's a long way of saying you left here in a huff, edited most of your posts, decried us for not making time just to sort your specific problems out, and now you're back, expecting something to have happened that benefits you.

Provided no SMF 1.1.x code were used in processing it and only SMF's BSD or Wedge code were used to read the database, it's cool.

I recently had to update one site I admin; I wrote a decent percentage of the custom coding and it was... interesting, I ended up doing the upgrade file by file from RC3 to RC5.He is kidding. The origins of that particular message date back to when we were much more 'off the grid' than we are now, when we didn't even mention we were an SMF fork. It was sort of like an unspoken code.Versions past final are package-manager based, meaning that upgrading is usually no more hassle than adding any mod - once you get past final.Of this I have little doubt.