At 10:33 AM 8/22/2005, Ben Collins-Sussman wrote: >I see two differences: > >(A) New trunk releases happen often. A new minor version of >Subversion is released every 4-6 months. All new features, >optimizations, code rewriting happens on trunk. > >(B) We only backport *bugfixes* to our release branches -- nothing >else. No new features, no rewrites, nothing complex. It has to be a >bugfix, and it must be a very important one. Our STATUS file on the >release branch stays relatively small, and the changes are usually >easy to review. The RTC policy becomes an asset, not an annoyance.
Ben, I suspect this has more to do with the fact that we have *millions* of users of httpd-2.0, tens of millions of 1.3 users, and some, here, are devoted to supporting those legacy users. If 'just switching' was trivial then great(!) Switch! But 1.3 -> 2.0 is not simply plugging in a new httpd, nor is 2.0 -> 2.2, because httpd regularly changes the module names and directives between versions minor and major. Only on subversion bumps do we attempt to retain ABI and config-clean migration paths for administrators. Bill
