Changes.xml or JIRA? (was RE: CactifyEar?)

[Vincent Massol <vm...@pivolis.com>]

Hi Magnus,

(moved to dev mailing list)

See below

> -----Original Message-----
> From: Magnus Grimsell [mailto:magnus.grimsell@idainfront.se]
> Sent: jeudi 30 juin 2005 12:57
> To: Cactus Users List
> Subject: RE: CactifyEar?
> 
> > Magnus, I was checking the changes.xml file and couldn't find
> > any reference
> > to the cactifyear task. Any idea? Has it been simply
> > forgotten to be added
> > there?
> 
> Yes, it has been forgotten. Or I wasn't really aware of it. Should all
> jira issues that are fixed in a release be added there or just the major
> ones?

So far, we have used the changes.xml to fully list all changes that aer
impacting in one way or another the user. So if we do an internal
refactoring it would show there for example.

That said, now that we have migrated to JIRA we have to make a decision I
think:
- either use JIRA for our changelog, which means that we need to have a JIRA
task for every user-impacting task (same as what we had in changes.xml)
- or continue using the changes.xml file

I would personally be in favor of using JIRA for the current version of
Cactus (i.e. 1.8) and do a JIRA changelog.

If others are ok, we can modify the changes.xml to explain that from now on
all changes are located in JIRA, and put a link to the JIRA roadmap in
changes.xml

What do you think? What do others think?

Thanks
-Vincent


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org