[Openvas-devel] Change Requests: Formalized procedure for feature changes?

Jan-Oliver Wagner jan-oliver.wagner at intevation.de
Mon Feb 18 22:31:44 CET 2008

Am Sonntag, 17. Februar 2008 01:11:05 schrieb Tim Brown:
> The work flow should be as follows, IMO:
> Initial request via tracker or mailing list -> Request is discussed in
> tracker and debated on list with any substantial points imported into
> tracker -> Consensus reached, developer documented change request uploaded
> to http://www.openvas.org/ -> Work done to implement change, with updates
> to tracker and lists as appropriate

sounds good.

> I would also suggest that the change requests link back to the relevant
> tracker entry.

this is a very good idea. Also links to mailing list discussions. I've added
this to the CRs now.



More information about the Openvas-devel mailing list