Extension compatibility 3.1 - 3.2

[david63]

Wonder how the CDB will handle that

I'm not allowed to comment as doing so I would get my knuckles rapped (again)!

[John P]

Avatar drivers 3.2 need a - '@upload_imagesize' in their config file as this isn't required in 3.1.
I was hoping for an answer about rmcgirr83 question earlier.

[MattF]

Avatar drivers 3.2 need a - '@upload_imagesize' in their config file as this isn't required in 3.1.
I was hoping for an answer about rmcgirr83 question earlier.

If you want to write clean concise code, then in some cases where phpBB 3.2 has changes that break backwards compatibility, you will just have to start a new version/branch of your extension for 3.2.x, while maintaining a separate branch/version for 3.1.x....just like the way phpBB itself is maintained.

If you don't mind ugly code, then you could do version checks on the PHPBB_VERSION constant, and use conditions to generate code required for either 3.1.x or 3.2.x, depending on what the board version is. Sort of like the Quick Install. As for services, they can be made optional and null.

The best approach is if a simple tweak here and there can keep your ext B.C. then go for it. Otherwise, just go with 2 versions until 3.1 goes EOL. You're better off looking towards the future than trying to keep things well in the past (which is what has made a real mess of Quick Install's codebase).

As per Rich's question, I think it goes without saying that if you're developing an ext for both 3.1 and 3.2, you should be making sure it works on the current stable releases of each of those.