Hei Matthew, On Wed, 12 Dec 2007, Matthew Carroll wrote:
> Why was that "fix" to the speed of the updateniceurls.php script applied > to stable immediately? If any comprehensive testing was done on the > functions of that script, it should have revealed straight away that it > wasn't working properly... it wasn't really a "stable" change, at least > the way I understand the word stable. branches like stable/3.9 are also just development branches. They are development branches of stable (already released versions), where as in trunk also new features are added. > Possibly there could be another "testing" level in svn before changes > migrate to stable, or maybe changes could be flagged somehow so that > non-trivial changes have a cooling-off period in trunk before being > applied to stable. I'm no svn guru, so I don't know how that could work, > but it seems to be a systemic problem with how ez svn works, so I'm > curious if you have considered these issues, and any possible solutions. It would mean another extra step while developing. At the moment fixes to trunk are immedeately merged to stable/*. Adding another testing branch would create considerable overhead. Instead on updating from SVN's stable branches between releases, you perhaps should consider doing it only when a release is made. However, you might then of course not always immediately have the latest fixes. Only in a release the "stableness" can be guaranteed at the moment. regards, -- Derick Rethans eZ components Product Manager eZ systems | http://ez.no -- Sdk-public mailing list [email protected] http://lists.ez.no/mailman/listinfo/sdk-public
