> but.. isn't svn 1.5 final a stable release? ;) Yes, but there's going to be a 1.5.1, isn't it? ;-)
More seriously, take GCC: you're more likely to find bugs with a 4.Y.0 release than with 4.X.n (X < Y): the code is more mature. > I'd expect the (several) release candidates to have exposed any show- > stopper issues. Then again, i'm not that familiar with subversion's > development process. Really think I should wait? I'd rather upgrade it > all now, and not have to revisit this issue again in some week. It's not about SVN: it is a general remark. This applies to GCC, it applies to M$ ServicePacks or Apple Software Update and virtually to every piece of software. > I agree that crash you've found in 1.5 final is not very > inspiring... :( I think it is due to the new "serf" library, but I have no time for now trying to reproduce this issue. I moved back to SVN 1.5 with the old library (Neon) and it worked as a charm. Guess what: libserf has been introduced w/ SVN 1.5, so it's support is less mature. If you remember the "old" days of SVN, when FSFS has been introduced in an official release (maybe around SVN 1.1): the authors were confident in FSFS, but they wrote that the BDB backend was still more mature. Even if SVN code was 100% bug free, there may have compatibility issues coming from dependencies. There are tons of dependencies, which vary from one OS version to another, from one distribution to another, from one platform to another. The question is: do you really want to experience a compatibility issue with a brand new official version on your production system, or can you wait for a couple of weeks till someone else bumps (or not) into the issue and reports it ? You can be both guys, but I'm not sure you want to take the chance with a production system; however you can try it for yourself on a test system... Cheers, Manu --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
