I think to would be good to have, but maybe this shouldn't be done as a forum topic but rather an article?
Also, I think having an issue/enhancement list would prevent from submitting the same stuff over and over again (this is why I asked about an issue tracker in the first place).
What we are thinking of doing here is something like http://www.squarefree.com/burningedge.
issues.ez.no has a changelog as an rss feed: http://issues.ez.no/Timeline.php?ProjectId=6&output=rss2
What we will do is read this and add it to as a blog entry with formatting/cleaning. In this fashion we should be able to discuss the changes too, and use the automated methods as much as possible.
How does it look? I can already see some possible refinements :)
Sure, that's a way of letting people that things are happening, even though I expect the more interested to go directly to the issue tracker. Still this is a nice "teaser" ;)
Maybe it would be just a little better if we added some "analytical formatting" to it, for example:
Issue #20001 - This functionality is not as good as I would like it
to be, this should be added by Someone Concerned
Changes:
- The status was changed by Someone Else
- The status was fixed...
Issue #20002 - It don't work! ;) by Someone Very Concerned
Changes:
- Xxxxxx
It could make it more readable, even though I would not consider this a major priority ;)