[development] Suggestion for people releasing new modules and themes into CVS

Neil Drumm drumm at delocalizedham.com
Wed Sep 13 18:19:55 UTC 2006

Khalid B wrote:
> - Upon committing a new module or theme, add a concise description of
> what the module does or how this theme is unique (e.g. fluid/fixed, 
> tables/css,
> ...etc.)

What is more important is having a concise description in your .info file.

> - Try to not commit every issue separately. If you plan to fix three 
> issues,
> then do not commit three times. Better do one commit with the three fixes
> in it.

As stated earlier, this is wrong.

> - Make sure you have the -kkv and not -kk, specially if you use Eclipse

I'm guessing most people don't use Eclipse.

> - Use the format following format for commits that relate to an issue:
> #nodeid description-goes-here, by patch-contributor
> On Drupal.org, the commits will be automatically linked to the issue.
> - Do not post the entire URL of the issue on Drupal.org.

These seem somewhat arbitrary. Any sufficiently descriptive format is 
fine. What should be said is

Drupal's CVS messages are published at http://drupal.org/cvs
- '#n' will be converted to a link to http://drupal.org/node/n. Do 
provide a reference to the issue on Drupal.org.
- Drupal.org user names will be converted to links. Do give credit for 
- Anything else special that CVS module does.

Neil Drumm

More information about the development mailing list