-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10.05.2013 20:58, [email protected] wrote: > Good Aftternoon, > > I am fairly new with managing/administering TRAC and subversion on my > project. I have been tasked with conducting an upgrade of TRAC from > version 0.12.1 to version 0.12.2. We use a subversion repository. What > is the best way to conduct this ugrade? I am starting by using a test > version that is running on a development server. My plan was to load a > subversion dump from the production server into subversion that is > running on the development server. Next, I planned to resync TRAC with > the repository and then conduct the upgrade of TRAC to version 0.12.2. > Is this a sound method for conducting this upgrade?
For this minor upgrade to another maintenance release I think it is super-careful. Sure, go ahead. Steffen Hoffmann -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlGP1KwACgkQ31DJeiZFuHdKWQCgkI6ACCmDfvSi12ZW0SAhy0nX 44sAoLxl+t/y0YOGPVn4J/UbnCRWPCyj =p1A5 -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
