Maybe you need to stop being a bully.Pot needs to meet kettle.
Some people will be on the thread reply ban train soon enough.
Some people will be on the thread reply ban train soon enough.
Thank you so much @Chris D : )I’m going to keep this brief for now but underline that work on 2.3 continues and we will work towards a more extensive communication update soon.
We hear you and we are listening but I am imploring that you listen to us very carefully when we say that there are no conclusions to be drawn other than we are working hard to bring you XF 2.3 as soon as possible and we are simply taking our time to get things just right.
There are some good things coming in 2.3 and to an extent some amount of work has already been completed towards future versions.
I feel like some of these have been addressed before but I think it’s reasonable to address some of the specific theories from this or the other thread:
* We have no plans to redirect focus to become a Cloud only product. Our product is XenForo, the software, and that is a prerequisite regardless of how it is delivered
* Work continues on XF with the same uncompromising quality as ever
* The business is doing well, with year on year sales increasing
I hope we can bring you a more significant update soon but in the meantime I’d just like to reiterate that work continues, and @Kier, @NixFifty, @Jeremy P and I are excited to show you what we’ve been working on.
Can everyone just ignore and pretend that certain someone doesn't exist so we can keep this thread on topic?
I’ll grow up Aussie, I’m just not as mature as you’re yet! Please give me some time to grow up and become a big boy like you
![]()
Pot needs to meet kettle.
I figure Chris bought them about a month before the pitchforks come out again, so hopefully they'll be able to release some more info by then and stave off the angry villagersThanks for calming the waves Chris.
Now, anyone for tea and biscuits?
It's funny, i'm in lets support the support the team that run the forum and give us this awesome software, whilst the angry mob are making the staff here angry.I figure Chris bought them about a month before the pitchforks come out again, so hopefully they'll be able to release some more info by then and stave off the angry villagers![]()
Thanks for calming the waves Chris.
Now, anyone for tea and biscuits?
* The business is doing well, with year on year sales increasing
Thanks for the update!! I’m glad you explained why you had to push back the new style and switch up the update model. I’m super curious to see the new design. You guys are the best making a solid and reliable forum software.Following @Chris D's comments yesterday, I'd like to briefly explain some of what's been going on.
Along with a bunch of major performance improvements and new features that are on the slate for 2.3, one of the main things on our list to do was a totally new master style. This has been largely my domain, and I have to say I'm really looking forward to unveiling it.
However, as the design was finalised and the technology behind it was being integrated, we turned our attention to how to migrate existing styles over to the new system in as much as would be possible. It was at this point that we realised that the new style is so dramatically different in its approach that we would need to spend a disproportionate amount of time producing some sort of migration system, and that it would be unlikely to be able to do a decent job given the vast gamut of customisation options available in the existing style system.
As you will know, because we place enormous value in our ability to provide a stable and reliable architecture upon which third parties can build plug-ins, extensions, applications and also styles, we make huge efforts to retain backward compatibility wherever possible when putting out a second-point release (2.1, 2.2 etc.).
It became clear that the new style would unavoidably introduce significant breakage to third party integrations, and reluctantly we decided to hold it back so that customers can benefit from the rest of what 2.3 has to offer, without needing to do extensive work to make existing third-party functionality and styles work with the new system. Some of the back-end customisation tools of the new style have been retained as they don't require drastic changes to templates or third-party styles, but the new style itself won't be released with 2.3.
That said, we have decided to switch to a different model for the way we release XenForo updates. While previously we have targeted fairly massive releases packed with new features, this has led to extended periods between those releases. I think it's fair to say that we are as fed up with that model as many of you are. There are features we finished ages ago that are slated for 2.3 release but have been held up waiting for other things to be completed.
After 2.3, we will introduce our new release model, where we will target a single major new feature with each release. That's not to say that other features definitely won't make it because of course they will, but instead of having a big slate of functionality to introduce with each x.y release, we'll get that one major feature done and hit the release button. The intention is that we'll have much more regular feature releases.
The first of those releases will be XenForo 3.0. Right now, the only feature we are definitely pursuing for that release will be the new style and as such, we hope that 3.0 will follow 2.3 in a relatively short time, as it should be effectively 2.3+style. Once 2.3 is out, we'll be getting in touch with major XenForo style producers to help them get ready for the 3.0 style, so that by the time it's ready for release there should be good third party support ready to go.
So, sorry for the delay, but rest assured we are working hard behind the scenes to bring you great software in the near future.
That’s a brilliant update.Following @Chris D's comments yesterday, I'd like to briefly explain some of what's been going on.
Along with a bunch of major performance improvements and new features that are on the slate for 2.3, one of the main things on our list to do was a totally new master style. This has been largely my domain, and I have to say I'm really looking forward to unveiling it.
However, as the design was finalised and the technology behind it was being integrated, we turned our attention to how to migrate existing styles over to the new system in as much as would be possible. It was at this point that we realised that the new style is so dramatically different in its approach that we would need to spend a disproportionate amount of time producing some sort of migration system, and that it would be unlikely to be able to do a decent job given the vast gamut of customisation options available in the existing style system.
As you will know, because we place enormous value in our ability to provide a stable and reliable architecture upon which third parties can build plug-ins, extensions, applications and also styles, we make huge efforts to retain backward compatibility wherever possible when putting out a second-point release (2.1, 2.2 etc.).
It became clear that the new style would unavoidably introduce significant breakage to third party integrations, and reluctantly we decided to hold it back so that customers can benefit from the rest of what 2.3 has to offer, without needing to do extensive work to make existing third-party functionality and styles work with the new system. Some of the back-end customisation tools of the new style have been retained as they don't require drastic changes to templates or third-party styles, but the new style itself won't be released with 2.3.
That said, we have decided to switch to a different model for the way we release XenForo updates. While previously we have targeted fairly massive releases packed with new features, this has led to extended periods between those releases. I think it's fair to say that we are as fed up with that model as many of you are. There are features we finished ages ago that are slated for 2.3 release but have been held up waiting for other things to be completed.
After 2.3, we will introduce our new release model, where we will target a single major new feature with each release. That's not to say that other features definitely won't make it because of course they will, but instead of having a big slate of functionality to introduce with each x.y release, we'll get that one major feature done and hit the release button. The intention is that we'll have much more regular feature releases.
The first of those releases will be XenForo 3.0. Right now, the only feature we are definitely pursuing for that release will be the new style and as such, we hope that 3.0 will follow 2.3 in a relatively short time, as it should be effectively 2.3+style. Once 2.3 is out, we'll be getting in touch with major XenForo style producers to help them get ready for the 3.0 style, so that by the time it's ready for release there should be good third party support ready to go.
So, sorry for the delay, but rest assured we are working hard behind the scenes to bring you great software in the near future.
This is hugely helpful! Thank you so much for the additional information.Following @Chris D's comments yesterday, I'd like to briefly explain some of what's been going on.
I like the new approach. Looking forward to a new style.Following @Chris D's comments yesterday, I'd like to briefly explain some of what's been going on.
Along with a bunch of major performance improvements and new features that are on the slate for 2.3, one of the main things on our list to do was a totally new master style. This has been largely my domain, and I have to say I'm really looking forward to unveiling it.
However, as the design was finalised and the technology behind it was being integrated, we turned our attention to how to migrate existing styles over to the new system in as much as would be possible. It was at this point that we realised that the new style is so dramatically different in its approach that we would need to spend a disproportionate amount of time producing some sort of migration system, and that it would be unlikely to be able to do a decent job given the vast gamut of customisation options available in the existing style system.
As you will know, because we place enormous value in our ability to provide a stable and reliable architecture upon which third parties can build plug-ins, extensions, applications and also styles, we make huge efforts to retain backward compatibility wherever possible when putting out a second-point release (2.1, 2.2 etc.).
It became clear that the new style would unavoidably introduce significant breakage to third party integrations, and reluctantly we decided to hold it back so that customers can benefit from the rest of what 2.3 has to offer, without needing to do extensive work to make existing third-party functionality and styles work with the new system. Some of the back-end customisation tools of the new style have been retained as they don't require drastic changes to templates or third-party styles, but the new style itself won't be released with 2.3.
That said, we have decided to switch to a different model for the way we release XenForo updates. While previously we have targeted fairly massive releases packed with new features, this has led to extended periods between those releases. I think it's fair to say that we are as fed up with that model as many of you are. There are features we finished ages ago that are slated for 2.3 release but have been held up waiting for other things to be completed.
After 2.3, we will introduce our new release model, where we will target a single major new feature with each release. That's not to say that other features definitely won't make it because of course they will, but instead of having a big slate of functionality to introduce with each x.y release, we'll get that one major feature done and hit the release button. The intention is that we'll have much more regular feature releases.
The first of those releases will be XenForo 3.0. Right now, the only feature we are definitely pursuing for that release will be the new style and as such, we hope that 3.0 will follow 2.3 in a relatively short time, as it should be effectively 2.3+style. Once 2.3 is out, we'll be getting in touch with major XenForo style producers to help them get ready for the 3.0 style, so that by the time it's ready for release there should be good third party support ready to go.
So, sorry for the delay, but rest assured we are working hard behind the scenes to bring you great software in the near future.
I can see where you're coming from, jaded and skeptical, but I do think we'll get something this time. We'll see who's right soon enough.Honestly.... at the current level of "providence"... I'll believe it when I actually see it shown.. talk is cheap., and XF has a LARGE history when it comes to 2.3 discourse.... and none of it has been proven yet.
Not really - each second point release (3.1, 3.2 etc.) will have at least one major new feature or improvementAm I right in saying that your new release schedule is going to be a little like iOS ? Big number increment with some features then smaller point with feature releases that didn’t quite make it?
We use essential cookies to make this site work, and optional cookies to enhance your experience.