Now that we have a decent infrastructure, we can use JIRA for
generating our changes report. This does mean that we need to do
everything through JIRA: additions, backports, etc.
Any ideas?
Martijn
--
a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a
for a
what about them do you find unreadable?
i would be +1 for this. keeping up changes.xml is a pain imho, and since a
good amount will already be entered into jira it will take work off us.
-igor
On 11/13/06, Erik van Oosten [EMAIL PROTECTED] wrote:
My 2ct:
JBoss does this. I find their change
What I don't like is that is a plain list without any notion on what is
important and what is not. Of course, its ok to maintain the changes in
a tracking system. But presenting the list of changes exactly as they
come from Jira is pretty hard on the reader. It should be fun to read
change
On 11/13/06, Erik van Oosten [EMAIL PROTECTED] wrote:
What the heck, I'll
volunteer to write those release notes if someone gives me that jira list.
https://issues.apache.org/jira/browse/WICKET?report=com.atlassian.jira.plugin.system.project:changelog-panel
:)
-igor
Erik.
Igor
Ok, let me know when its needed.
Erik.
Igor Vaynberg schreef:
On 11/13/06, Erik van Oosten [EMAIL PROTECTED] wrote:
What the heck, I'll
volunteer to write those release notes if someone gives me that jira
list.
