Thanks for you explanation David, I was curious about this as well. Updating from 3.0 to 3.1 is a 'big deal' with the modifications I have. Been planning and testing for my update for a few months now. I wouldn't be happy if a update from 3.1 to 3.2 would be the same struggle as 3.0 to 3.1 So I'm glad to hear that this is not the case.DavidIQ wrote:In theory, yes. There might be some needed changes, especially if there are major style changes, but the underlying architecture that makes extensions work, including event existence and locations, should go unchanged from 3.1 forward.CarpCharacin wrote:so if i have a 3.1 board with a lot of extensions installed, does that mean i could upgrade 3.2 once it is released and everything would still work?
The one likely exception to this is if an extension is relying heavily on the legacy functions, which will obviously be removed from the core product at some point. Extension authors do well in moving away from using those functions, i.e. request_var() and some other functions, and using the available classes that perform the same actions. I don't think I've seen much of this however.
andSajaki wrote:I find this abit soon considering that alot of people haven't even started looking at 3.1 (myself included).Currently the planned schedule is as follows:
May 2015 - 3.0.x End of Maintenance
Nov 2015 - 3.0.x End of Life, 3.2.0 Release
Keep in mind that End of Life is not End of Support. As Naderman said:P_I wrote:Given the breakpoint between phpBB 3.0 and 3.1 and the inevitable lag to build up the extension and styles ecosystem, I'm wondering if the gap between 3.1 and 3.2 is a bit too close.
(emphasis mine)naderman wrote:End of Life - End of Life means, that no security patches will be provided anymore. Further this marks the end for extension and style updates. The Extensions and Styles Teams will not validate new updates for this version anymore.
End of Support - End of Support means, that the support forums for the respective version will be closed and questions will not be answered anymore. Currently there are no specific End of Support dates but the Support Team will support the versions at the very least until the End of Life of the respective version. Support may be provided past this point and the support team will give at least 6 months notice before the End of Support for a particular version.
Both extensions and styles face pretty much the same potential pitfalls when going from 3.1. to 3.2 as they do going from 3.1.x to 3.1.y. There are no "pre-validation" processes for those minor updates. And any author can easily grab a copy of the 3.2 branch off GitHub and test/develop their exts in it already, there really is no need for such thing.david63 wrote:In regards to extensions for future major versions of phpBB - would it be possible to have a "pre release validation" process? That way extensions could be developed/modified to work with the new version of phpBB and be ready to install almost on release day rather than users having to wait months for extensions to be developed and then validated.
The same would also be useful for styles
That version in composer.json is purely informational at the moment. It may come into play in 3.2 or later though.david63 wrote:One issue with extensions is that some (many?) have an upper version limit set in the composer file of less than 3.2 dev, which if my understanding is correct would mean that they would not work with any 3.2 version
That list, as it is now, is how it should be. The tracker is being used for versions that are being worked on or were worked on before. There isn't really a "set-in-stone" list of future versions. Your best guide is what was already announced.Popp Singh wrote:There was a list of future versions here thats now gone ---- > https://tracker.phpbb.com/projects/PHPB ... lease-page Can someone please point me at the new location ?