On Jul 15, 7:59 pm, "steven higgan" <[EMAIL PROTECTED]> wrote: > 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
I failed miserably, we restored the backup, just going to wait. Had issues with the python subversion bindings, or so it seemed, but also the sspi module seemed to be a co-conspirator. This is a weekend project I think, so I have time to deal with issues like this and move to [resolved] so I can then move to [verified] 'status will be changed to closed' :D the worst part is, currently, the projects in question have NO source files in version control yet. So, the "impact" from that side is nil, it's getting it to work with trac and apache that's the bear. current system isn't broken, so....just really would like the merge tracking feature. will give it a go again in a few weeks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
