Hello, I'd like to request from the Subversion development schedule to consider raising the priority of implementing the feature of "server-side config which 'broadcasts' to clients" as described in:
http://subversion.tigris.org/issues/show_bug.cgi?id=1974 In our development environment, we found it necessary to use an autolinkification capability that is currently implemented by TortoiseSVN(http://tortoisesvn.net/) as properties(http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html) on each directory. However the existing implementation is not optimal due to this missing feature in Subversion. Additionally, the SCM-to-bugtracking integration system we are working on, called Scmbug (http://www.mkgnu.net/?q=scmbug), could also benefit from such a server-side configuration feature. We are developing Scmbug tools that need some configuration parameters from the repository itself, and as a result are limited in their capability. For example, our Version Description Generator tool (http://files.mkgnu.net/files/scmbug/SCMBUG_RELEASE_0-18-3/manual/html-single/manual.html#VDD) needs the bugtracker url in order to produce a release document in HTML format. This url is the same as the autolinkification url needed by TortoiseSVN. We are presently working on Merge tool that given a branch name and a list of bug ids, it can retrieve from the bugtracker the changeset applied in the bugs and merge it in the branch. Again, this tool needs configuration parameters stored in the repository. Our current solution to this problem is not optimal: we run these tools on the machine hosting the SCM repository. The situation is even more difficult in the TortoiseSVN solution storing properties in each folder: when new folders are added, the properties must be manually added by the user too. The existing discussion on bug 1974 indicates that absence of the server-side config feature is causing problems to a lot of people. I understand that Subversion development, and resources, may be steered in a different direction at this moment. Please consider implementing this feature soon when the opportunity arises. AT A MINIMUM: ************* If it's not possible to implement this soon, would it be possible to design this to some level ? For example, can 3rd-party integration tools, like TortoiseSVN and Scmbug, assume that this "server-side config" will be stored as a file inside the repository, and not as propsets ? Simply agreeing on this convention could speed-up the implementation of our integration to use this Subversion feature when it becomes available. Thanks, Kristis _______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
