[Bro-Dev] #435: topic/jsiwek/doc-framework
Bro Tracker
bro at tracker.icir.org
Wed May 4 10:10:14 PDT 2011
#435: topic/jsiwek/doc-framework
---------------------+------------------------
Reporter: jsiwek | Owner: jsiwek
Type: Task | Status: assigned
Priority: Low | Milestone: Bro1.6
Component: Bro | Version: git/master
Resolution: | Keywords:
---------------------+------------------------
Comment (by jsiwek):
> Fine with me, but let me merge doc-framework once into master before
> we start doing changes to the doc stuff directly in
> policy-scripts-new. That reduces what will be merged later when
> policy-scripts-new is ready.
Ok, I can change this to a merge request.
But first, one more worry I thought of: we don't really have a
robust/stable test suite for policy-scripts-new, right? The current btest
suite has 15 failures for me with a fresh checkout. What should I be
using to make sure new doc changes in policy-scripts-new doesn't cause
regressions?
--
Ticket URL: <http://tracker.icir.org/bro/ticket/435#comment:23>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker
More information about the bro-dev
mailing list