[GRASS-dev] Proposal bug management (old trackers - GRASS-trac)
Hamish
hamish_b at yahoo.com
Sat Feb 9 17:40:42 EST 2008
Markus:
> > Suggestion: create tickets in GRASS-trac for the important bugs
> > left in GForge or RT. This permits to assign milestones and renders
> > bug
Martin wrote:
> I would agree, since the automatized migration of bugs reported in
> GForge is unclear (and for RT almost impossible).
nothing's impossible. :)
Clarification+update of issues here would be interesting to know.
> > management more transparent (with little overhead). Communication
> > should continue in the old reports.
>
> I am not sure, I would vote to continue in communication in Trac.
> When reporting GForge/RT bug in Trac, to add link to the old tracker
> to see previous comments.
I would prefer to copy report text in full as perhaps one day the old
servers go silent for any reason and the links go cold.
Even a flat ASCII or HTML copy would be fine.
Hamish
____________________________________________________________________________________
Looking for last minute shopping deals?
Find them fast with Yahoo! Search. http://tools.search.yahoo.com/newsearch/category.php?category=shopping
More information about the grass-dev
mailing list