[Bro-Dev] #435: topic/jsiwek/doc-framework

[Bro Tracker]

#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):

 Is there any objection to merging this branch into `policy-scripts-new`
 and picking up work there?

 I'd like to be able to more closely test the doc generation against real
 examples of the new policy scripts and logging.  I think there's going to
 be bugs to be worked out before things play nice together and it's hard to
 fix them when I'm off working in an isolated branch.

 Other choices:

 1) merge `policy-scripts-new` into `doc-framework` and continue to work
 separately from everything in `doc-framework`, which would have to be
 merged to `master` *after* `policy-scripts-new`
 2) merge current `doc-framework` into `master` for the final time and
 delete it; I'll pick up remaining doc-related work in `policy-scripts-new`
 afterwards

-- 
Ticket URL: <http://tracker.icir.org/bro/ticket/435#comment:18>
Bro Tracker <http://tracker.icir.org/bro>
Bro Issue Tracker