issue queue

The official! How to make an issue report, part of the official guide to using the issue queue.

See also Report a problem in the Troubleshooting guide.

And the Views issue queue guidelines which are comprehensive and rigorous and puts the entire process in one document, and almost everything can be directly or with minor adaptation applied to other projects.

This is in etc/trac/trac.ini. Note that each project can override in its own trac.inin (which for Agaric's system is in /srv/trac/PROJECTNAME/conf/trac.ini).

Visitors, please note that while Agaric-specific documentation may be informative to you, it is meant primarily for Agaric's internal use and is highly unlikely to work step-by-step without fulfilling an awful lot of dependencies first.

After setting up the project per Deploying the Agaric way, we can use our trac setup vlad task to do most of the work.

From within the project:

rake test vlad:setup_trac

Automatic Benefits:

Your clients learn to use an environment similar to the site you are building for them, rather than the different markup syntax and behaviors of trac or other system.

Features:

• URL fields for bug reports which would be able to replace (or generate) the base URL with a defined set of URLs for development, stage, or production sites in use.
• Time tracking?

Resources:

• How to package a profile on drupal.org