So I would like to suggest a protocol for addressing the bug fixes and patches that are listed on the sourceforge site.

If a developer is going to take on one of the bugs or patches to review and update into CVS, I suggest that they assign the bug to themselves first. This lets everyone know that they are the owner of the issue for the time being.

Doing this will help to minimize duplicate effort, such as the update I was testing, prior to performing a cvs commit on the delete cookie bug which Ian just committed... ;-)

If the bug/patch is assigned to someone, and you want to see it fixed sooner than they seem to be getting to it, then just ask them about it.

Anyway, thanks Ian... ;-)

-Stuart-



-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Webware-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webware-devel

Reply via email to