The current trackers are at
http://www.openehr.org/issues/secure/Dashboard.jspa
There are a few options:
- a single issue tracker, in which you track problem reports and
changes to the software. I am personally not a fan of this approach
because in my view a single issue can't properly act s documentation of
a user problem and also of teh software team's change... but it is easy
to do, and it means only one tracker
- a CR (change request) tracker, for recording the changes done to
the software base by the committer team
- a PR (problem report) tracker, for recording issues raised by
users of the software
- both CR and PR trackers, to do the job properly ;-)
there would be some admin time involved, but not too much. The
development team may also need to learn how to use these tools...
- thomas
On 29/06/2010 16:30, Moretti Leonardo wrote:
In my opinion, an issue reporting system would be very useful!!
Regards!
leonardo
On 23/06/2010 21:48, Rong Chen wrote:
if this group wants a Jira tracker, just say so, it can be set up.
- thomas beale
Currently there isn't any issue tracking system for the java project.
Issues or change requests are sent to this mailing list instead. We
could use one if the java group think the benefit will likely
over-weigh the administrative overhead of using Jira.
_______________________________________________
Ref_impl_java mailing list
Ref_impl_java@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_java
_______________________________________________
Ref_impl_java mailing list
Ref_impl_java@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_java
_______________________________________________
Ref_impl_java mailing list
Ref_impl_java@openehr.org
http://lists.chime.ucl.ac.uk/mailman/listinfo/ref_impl_java
|