Changes between Version 8 and Version 9 of TracSynchronize
- Timestamp:
- Nov 8, 2006, 10:51:47 AM (18 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
TracSynchronize
v8 v9 1 1 = Move, Copy and/or Synchronize Parts or all of Trac Instance = 2 2 3 There are some use cases where moving, copying, synchronizing trac instances (or part of trac instances) might be benefitial:3 There are some use cases where moving, copying, synchronizing Trac instances (or part of Trac instances) might be beneficial: 4 4 * single persons working disconnected: 5 5 * they would need to get the latest information they have access right to onto a laptop. 6 * when reconnecting to the network they need to merge their changes into the central trac instance6 * when reconnecting to the network they need to merge their changes into the central Trac instance 7 7 * InterTrac: 8 8 * information is entered into the wrong instance and should be moved to another one. 9 9 * information should be moved to a newly created trac instance 10 10 11 related tickets are: #1465, #146511 Related tickets are: #1465, #1465 12 12 13 == some solution ideas grabbed from the mailing list and the tickets ==13 == Some solution ideas grabbed from the mailing list and the tickets == 14 14 15 15 * [attachment:csv2trac.py use import/export with csv] … … 17 17 * use (implement) synchronisation based on the xml-rpc based on timeline information 18 18 19 n.b. Here is a [http://tomster.org/geek/trac/csv2trac.3.py/view PostgreSQL compatible version] of the [attachment:csv2trac.py csv2trac.py] script. I couldn't add it to this page, as it was rejected as Spam. Anyone with sufficient privileges should feel free to add it here and remove the above link to my site. [http://tomster.org Tom Lazar].19 N.B. Here is a [http://tomster.org/geek/trac/csv2trac.3.py/view PostgreSQL compatible version] of the [attachment:csv2trac.py csv2trac.py] script. I couldn't add it to this page, as it was rejected as Spam. Anyone with sufficient privileges should feel free to add it here and remove the above link to my site. [http://tomster.org Tom Lazar]. 20 20 21 == challenges which may come up ==21 == Challenges which may come up == 22 22 23 23 * stable ticket numbering must be guaranteed (either provide prefixes or numbering ranges for the instance which created it or invent something else)