Somehow I missed this post earlier. I'm pretty sure I can follow the directions in your post but I have a few questions:
1. What happens when I "submit" the sqlCVS diff? Is there someone who reviews it before it becomes available to others performing a sqlCVS update?
2. Is there some point in the process where a small group can be enlisted to test the newly available device template without the template being spread too far and wide? Despite that the template works great on my system, it seems that it ought to be tested on other people's systems before it should become mainstream. Otherwise there is a real chance of my new template actually being worse than the existing one.
3. Should I be changing the existing Denon receiver template or creating a new one with a new name and ID? It seems like there would be arguments for both options.
1. Once the sqlCVS diff is submitted, reply to your trac ticket and include the batch IDs. Then the best course of action is probably to jump onto IRC and ask someone with access to svn and sqlCVS to review and approve your batches and close the trac ticket. If the batch looks good, and there are no glaring problems, it will likely be approved.
2. After approval the updated template is available to everyone. New installations will automatically acquire the newest version of the template, including your changes. Existing installations may perform an sqlCVS update to get the updated version of the template. There doesn't currently exist a reliable way to move templates around without this process.
3. I think that you should only create a new template if it would break (or change) functions with existing receivers using the template. If this is something that existing Denon receivers, that currently use this template, should implement (and it sounds like it is) then modify the existing template.
Hope that helps.