Re: Kudos - keep up the hard work!

[Derek Neighbors]

On Sat, 2002-10-19 at 10:50, Jason Cater wrote:
> > 
> > One thing I would like to see is a tool for our DCL setup that creates
> > a BUGS file from outstanding tickets (or TODO, from the workorders).  
> > 
> > The DCL setup we have is fine for on-going stuff. But it sucks for
> > bug-smashing sessions. It also sucks since the outstanding bugs/todo
> > list isn't in any way sinced with DCL, so the end-users don't know
> > where things stand. 

I have always stated this as a long term goal. :)  Roadmaps should be
built out of DCL as well.  As soon as 'versioning' of products is better
supported.  This way file bugs with 'version' targets and workorders
with version targets.  Then run a report of what is slated for version X
and a roadmap falls out. :)

> > I would think it would work like the ultra-cool cvs2cl.py script that
> > creates the ChangeLog from CVS history.  Perhaps, dcl2bugs and
> > dcl2todo? 
> > 
> 
> After thinking about this for a minute, I realized this should be a GNUe
> Report example. Doh!

Yip I see this as a report. :)

-- 
Derek Neighbors
GNU Enterprise
http://www.gnuenterprise.org
address@hidden

Was I helpful?  Let others know:
 http://svcs.affero.net/rm.php?r=dneighbo

signature.asc
Description: This is a digitally signed message part