James E Weaver wrote:

Hi,

I've been trying to clean up the Trackers a bit in jWebUnit, as you've
probably noticed by the barrage of auto-emails caused by the status
updates.


Very good!!!

Here are some things that I think will help us keep some order, please let
me know if you disagree.


No disagreement, just additions!

When you fix a bug in the CVS tree, Mark the status of the tracker item as
CLOSED and put it in a group for the next release. We already have a group
set up for "Release 1.3" that we can use for this. This way, if you want
to see what has been fixed but still pending release, it's easy to do so by
selecting the status of CLOSED and the group corresponding to the next
release.


Also, in the xdocs directory, there is a file called 'changes.xml'. Its purpose is to track fixes, additions etc. in a concise manner, so that I can generate the new website including links to the sourceforge trackers, generate an announcement email and message to post to the various news sites (i.e. theserverside.com). So when you fix something, patch something, please put a line in the changes.xml file. If a tracker item was involved, please also include that number in your line. If someone else was to blame (or thank) for the bug, then please also include their name. Use a short description (or the title of the tracker item) to describe the fix/bug/patch/etc.
There are some examples already present, so normally one shouldn't have to have any problem adding ones fixes. When in doubt, look at the following link for more information about the changes.xml file: http://maven.apache.org/reference/plugins/announcement/


If you wish to see how this look in a website, look at: http://jwebunit.sourceforge.net/changes-report.html

If you wish to see how your additions look like, run 'maven site' in the project root directory, and point your browser to the index.html file in the target\docs\ subdirectory of the project root.

BTW, when you've updated the changes.xml, *DON'T* forget to commit it back into CVS!

Also, are the automatic emails on update of tracker items adding to much
noise to the development list?


Not in my opinion. I use the list(s) to monitor activity on the project. While I don't answer too many questions, or follow up on tracker items, I will try to answer those I can do quickly.
But it might be better to not do all at once, but one every other day... :-)


But thanks for doing this much work!!!!!!!

Martijn


------------------------------------------------------- This SF.Net email is sponsored by: thawte's Crypto Challenge Vl Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam Camcorder. More prizes in the weekly Lunch Hour Challenge. Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m _______________________________________________ Jwebunit-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jwebunit-development

Reply via email to