Jeff Jensen a écrit :
I like the changes page as a "simplified, user-friendly" list of notable changes
made for each release. The defect/RFE tracking system has the details for the
initiated users when desired.
Quoting Stephane Nicoll <[EMAIL PROTECTED]>:
On 12/27/06, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I never really understood the changes.xml myself, as I don't want to
keep things in an issue tracking system and changes.xml or is this
for folks who don't employ an issue tracking system?
Yes and no. I've always seen it as a "technical" changelog of the
project. When end-users create issues, the summary is not always
understandable so we end up with a list of "things" beings solved.
The changes.xml allows to describe in more details what happened. It's
a good thing actually and it's certainly a good alternative for people
not using an Issue tracker that maven handles.
Stéphane
- Keeping it in a maven-changes-plugin brings M1 and M2 more in
sync than they were before, which eases migration pains.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi,
I agree with you and I think that the information should be in the scm
comments to refer to the bug tracking system.
We have developed such a maven plugin that parses subversion comments to
create a changelog page with only significant modifications displayed
and links to the corrected bugs if needed. So users can see in what
state each release and the trunk is.
I hope to be able to release it publicly.
If you feel this is something useful I would be able to convince my boss
more easily.
Emmanuel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
