Thanks for all of the info. I suppose I could make things a bit simpler by doing an .11 install rather than bothering with a migration from .10 since we never were able to get .10 working properly. However, at this point, I have a feeling that things may be quite a mess on the server with .10. Therefore, is there an easy way(or even a need) to uninstall .10 before doing the install of .11. Also, what is the easiest method to then install .11? Our other alternative would be to get .10 or better yet Clearsilver installed on a 64bit CentOS box - which is the reason that we are looking at .11 in the first place. I'll leave it to the experts to let us know which path we should head down. We really think this product could be a perfect fit for organization and look forward to getting it up and running. As such, any help/advice would be greatly appreciated.
On Apr 11, 4:07 am, Christian Boos <[EMAIL PROTECTED]> wrote: > Jason Winnebeck wrote: > > Isn't this a little misleading? There are different requirements on the > > libraries used, aren't there? Also macros won't work anymore in 0.11 if > > I have heard correctly. I'm not sure a migration process for a > > non-trivial project is simple to go to and from Trac 0.10 and 0.11... > > No it's not misleading at all: I meant that if you have a running 0.10.x > project, even non-trivial with lots of plugins etc., you can give a try > to 0.11 on that project by installing the *additional* packages needed > by 0.11 (i.e. Genshi). If for some reason, you're not satisfied with > the transition, like some of the plugins you're depending on are neither > working with nor yet ported to 0.11, or you depend on the old-style > macros which won't work anymore, or you have some other problems, *then* > it's safe to go back to 0.10.x on the same environment, because you > presumably still have all the software needed to run 0.10, as nobody > told you that you should uninstall Clearsilver when switching to 0.11. > Quite to the contrary, Clearsilver based plugins are still supported in > 0.11. > > My comment was perhaps more understandable by people who experienced the > transition from 0.9.x to 0.10dev, as the database schema was changed > between those releases. So once you had upgraded an environment from 0.9 > to 0.10, there was no way back, unless you reverted to the backup. I > simply wanted to point out that there's no such difference between 0.10 > and 0.11, beside the caveat concerning 0.10.4. > > A successful migration should of course take care of converting the > old-style macros to new-style macros, and take care of selecting 0.11 > compatible plugins. There's still some time to go before a 0.11 release, > even a beta, so it's not necessarily a bad idea to have a try and see > what is the extent of work required. In some cases, you might see that > it "just works" and you could even happily run a Trac 0.11dev > installation like some happy few out there ;-) (e.g. > seehttp://trac.pocoo.org) > > -- Christian > > > -----Original Message----- > > From: [email protected] [mailto:[EMAIL PROTECTED] > > On Behalf Of Christian Boos > > > This means that if you had a Trac environment created with 0.10, you can > > use the 0.11 codebase with it. > > If for some reason this doesn't work for you, you can go back and use a > > 0.10 codebase with this environment. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" 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-users?hl=en -~----------~----~----~----~------~----~------~--~---
