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

 > > 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`
 >
 > I'm inclined to go this direction.  I understand the difficulty though,
 I've been running into it over and over again with all of the changes
 going on. :)

 Doing it this way seems like it's harder for people working in `policy-
 scripts-new` to get active feedback on what the documentation will look
 like -- they'd have to switch branches to `doc-framework` to generate
 documentation.

 It's also likely that I'm going to be making minor tweaks to policy
 scripts with respect to documentation and it's going to be tedious to
 commit those changes to `policy-scripts-new`, switch to `doc-framework`,
 merge, test,  repeat...

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