personally I have setup my CI & Subversion enviroments on Virtual Servers.
here at work we use HyperV, on that box I have two Server 2003 VMs one for our CI enviroment, the other for Subversion. this makes 'testing upgrades' much easier. I take a backup of the virtual machines, do what i need to do - prove it - and finally document and migrate changes to the production enviroments. Downtime is minimized, and risk is completely mitigated. On Tue, Jul 15, 2008 at 9:21 AM, <[EMAIL PROTECTED]> wrote: > > So, > > It seems 1.5 really is stable, the binaries are out there now, a few > people have took the plunge and found the few issues. > > So, Here are my questions: > > Running apache 2.2, on windows > mod_pyhton > mod_sspi > trac 0.11b2 > python 2.5(.2 I think) > > Any warnings on the "upgrade" to 1.5? > > I am "assuming" I can download the binaries (apparently for the 2.2 > apache release you only get the .zip format for the windows subversion > binaries and apache bindings) and extract them over top my Apache > install. > Download the python 2.5 bindings (should I go with .zip, or the > windows installer here?) > Upgrade my repo's to 1.5 in subversion > and restart apache, and poof, I should be ok with respect to trac. > > all that's left then is to have the devs upgrade their respective > clients/commandline versions as needed for checkings and checkouts. > > I missing anything here? > > Thanks in advance > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
