2.4 vs. 2.6

[spacejanitor]

Hello,

I'm wondering whether there is a comprehensive (or non-comprehensive) set of differences published somewhere between the 2.4 branch and the 2.6 trunk.
I'm currently running 2.6 in production (even though it is a dev release and that is a little risky).

[williamconley]

Comprehensive? well ...

1) admin.php has a changelist in it (read the file! it's in text, but the explanations are very short).

2) SVN! find the "branch" moment when 2.4 broke off ... (and check all changes committed after the version changed to 2.6). That's comprehensive ... but now you're left to figure out what those changes "do". SVN comments can be helpful, but then again the actual SVN changed content is more helpful if you can read it.

Most of the time, however, the admin.php notations are enough.

[mflorell]

Using trunk(or 2.6) is not risky, most of our managed clients are running it, and we do testing before we commit code to it.

At this point there have only been a few features added to trunk that are not in branch 2.4, you can see the list in the UPGRADE doc.

[williamconley]

Do you keep your managed clients on the "latest" or upgrade them "at intervals"?

IE: If you upgrade SVN tonight, will the managed clients be on that version tomorrow (stable!), or will you wait and upgrade your managed clients later?

[mflorell]

We upgrade at intervals, usually a couple months depending on the client. There are times when we upgrade most of them at once if there is a security issue.