Forward-compatible development and the trunk

[freejoe76]

Hi all,

I'm in the early-middle stages of upgrading a phpbb2 forum to phpbb3.0 ( http://neighbors.denverpost.com ). I'm not big on going through this process again, thus, I'm making this install as "forward compatible" as possible.

This isn't easy, because I built some functionality into the phpbb2 core that I'd like to replicate in phpbb3 (things like turning the registration process into a one-pager, automatically logging members in after they register, writing topics to a flat javascript file for inclusion on another site, etc. etc. etc.).

I did have phpbb3.0 downloaded and added to a subversion repository I keep for the site. Then I saw you guys put phpbb3 on subversion too.

So, I'm wondering, is using the trunk version of phpbb3 the best way to keep as "forward-compatible" as possible? I'm not thinking it is (just ran a diff on the trunk vs. the phpbb3 on your download page)... so, well, is there any other better way to keep from having to significantly re-factor with every new release?

Joe

[Prince of area51]

Its never recommended to use the development (SVN) version in a live environment. When a new (and stable) release (phpBB 3.2.x) will be available, there would be an upgrade for it as well.

And I really don't think that a lot of functionality of the code would be changed for newer release of phpBB 3.x. So, as long as you keep everything >= PHP 5, things would be fine. Obviously, some of your added code might not work but you would have to do edits here and there to make the your own written code compatible with the new phpBB code.

[Techie-Micheal]

By definition, the trunk is not stable. phpBB uses the branches and tags model in SVN to flag different releases. However, the branches get committed to to update that version.