Changes between Version 32 and Version 33 of TracMultipleProjects/ComprehensiveSolution

Timestamp:

Jul 2, 2007, 2:05:38 PM (17 years ago)

Author:

Dave Abrahams <dave@…>

Comment:

Move discussion out of main flow

TracMultipleProjects/ComprehensiveSolution

@@ -22 +22 @@
    issues on my local development server and am composing this page as I
    port my real Trac instances over to the new system.
-   - ''Just a quick feedback to mention that at this point, '''what''' your solution is isn't immediately clear  ;-). From the ''requirements'' section below it appears that it is based on !TracForge, so maybe this should be made more clear from the start. Note that !TracForge itself is probably implementing something quite close to what is discussed in TracMultipleProjects/MultipleEnvironments.'' [[br]]-- cboos
-   - ''Yes, I know.  As I said, "work in progress," which I hope to have finished in the next few days.  I'm actually combining stuff from !TracForge, various other plugins from TracHacks, stuff from TracMultipleProjects/MultipleEnvironmentsSingleDatabase, and some of my own code.  The approach for supporting cross-project queries is entirely different from what !TracForge does, so characterizing it as "based on !TracForge" won't really tell people what it is.'' [[br]]-- dave
-   - If you can tell me more than 3 persons who could understand how tracforge did this i pay you a beer, and based on tracforge is confusing. otherwise not ... --ThurnerRupert.
-   - Did what?  Also, sorry, but everything after "beer" doesn't parse for me ... and that's not just selective listening! [[br]]-- dave
 
  * This method '''requires the use of
@@ -36 +32 @@
 
  * Use [http://www.postgresql.org/ PostGreSQL] to collect all projects into a single database using separate PostGreSQL "schemas."
+ * Change the SQL of your ticket report queries
  * Use trachacks:MultipleProjectQueryFilterPlugin to fix up urls in those query results to point to the right tickets.
  * Use [trachacks:TracForgePlugin TracForge] to get:
@@ -91 +88 @@
  3. This approach has basically the same flaw as the alternative approach above using PostGreSQL, just one level removed: yes, if you click on a ticket in the report, it takes you to a ticket with the '''right content...''' but that ticket is still in the '''wrong context'''...  so any project-local links to wiki pages changesets, etc. that are embedded in the ticket will take you to the wrong place.  One could try to patch the subscription code to fix them up, but in my opinion that is a hopeless fight.  To handle all the possible wiki syntax, you'd have to do a reverse translation for all the macros, plugins, etc. that introduce new wiki syntax.  There are just too many to possibly account for all of them, and trying to keep up with new ones would be a maintenance nightmare.
  
+----
+
+== Discussion ==
+
+   - ''Just a quick feedback to mention that at this point, '''what''' your solution is isn't immediately clear  ;-). From the ''requirements'' section below it appears that it is based on !TracForge, so maybe this should be made more clear from the start. Note that !TracForge itself is probably implementing something quite close to what is discussed in TracMultipleProjects/MultipleEnvironments.'' [[br]]-- cboos 06/25/2007 11:02:46 AM
+   - ''Yes, I know.  As I said, "work in progress," which I hope to have finished in the next few days.  I'm actually combining stuff from !TracForge, various other plugins from TracHacks, stuff from TracMultipleProjects/MultipleEnvironmentsSingleDatabase, and some of my own code.  The approach for supporting cross-project queries is entirely different from what !TracForge does, so characterizing it as "based on !TracForge" won't really tell people what it is.'' [[br]]-- dave 06/28/2007 04:45:59 PM
+   - ''If you can tell me more than 3 persons who could understand how tracforge did this i pay you a beer, and based on tracforge is confusing. otherwise not ...'' [[br]] --ThurnerRupert 06/29/2007 05:14:04 PM
+   - ''Did what?  Also, sorry, but everything after "beer" doesn't parse for me ... and that's not just selective listening!'' [[br]]-- dave  06/30/2007 06:11:46 AM