If you find a bug during testing
1) Post description of bug to devlist
2) Submit a Sourceforge bug.
3) If the bug is deemed serious we'll mark it as 'Include-in-3.2RC1' category
4) Someone Fix the Bug!
5) When a fix is committed the bug should be retested by a third person
6) When fix is verified, the Sourceforge bug is marked as 'Solved'

Sounds good.


As of now there are two immediate bugs
1) Fixing head_before_get to be default true and override (to false)
   during a '-i' reindex

I volonteer for this bug. Is it ok?


Ciao ciao
-Gabriele
--
Gabriele Bartolini: Web Programmer, ht://Dig & IWA/HWG Member, ht://Check maintainer
Current Location: Melbourne, Victoria, Australia
[EMAIL PROTECTED] | http://www.prato.linux.it/~gbartolini | ICQ#129221447
> "Leave every hope, ye who enter!", Dante Alighieri, Divine Comedy, The Inferno




-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
ht://Dig Developer mailing list:
[EMAIL PROTECTED]
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-dev

Reply via email to