# \[Bro-Commits\] \[git/bro\] fastpath: Redo the "how to upgrade" FAQ. (06d6277)

**URL:** <https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454>\
**Category:** Development\
**Tags:** development\
**Created:** [October 3, 2012, 9:29pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454 "2012-10-03T21:29:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Daniel\_Thayer](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@Daniel\_Thayer](https://community.zeek.org/u/Daniel_Thayer)\
**Post date:** [October 3, 2012, 9:29pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/1 "2012-10-03T21:29:46Z")

</div>

It seems to me that this info should be in the "Installing Bro"  
document, since upgrading from a previous version will be a  
very common scenario.

---

<div class="post-metadata">

**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\
**Post date:** [October 3, 2012, 10:03pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/2 "2012-10-03T22:03:24Z")

</div>

Good point, maybe we need an "updating" section there.

Robin

---

<div class="post-metadata">

**Author:** ![Daniel\_Thayer](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@Daniel\_Thayer](https://community.zeek.org/u/Daniel_Thayer)\
**Post date:** [October 3, 2012, 10:06pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/3 "2012-10-03T22:06:55Z")

</div>

If you want, you could just merge it into master, then I can  
change it later to point to the "Installing Bro" material  
(as part of my documentation work for 2.2).

-Daniel

---

<div class="post-metadata">

**Author:** ![robin](https://yyz1.discourse-cdn.com/flex011/user_avatar/community.zeek.org/robin/32/599_2.png) [@robin](https://community.zeek.org/u/robin)\
**Post date:** [October 3, 2012, 11:06pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/4 "2012-10-03T23:06:44Z")

</div>

Sounds good.

Btw, it's a bit unfortunate that we have put the FAQ document into the  
distribution as that means it won't update on the web server until the  
next release comes out. That's something I think we should chnage in  
the future: the FAQ shouldn't be tied to a specific version but  
maintained separately as a web page instead.

Robin

---

<div class="post-metadata">

**Author:** ![Vlad\_Grigorescu2](https://avatars.discourse-cdn.com/v4/letter/v/c4cdca/32.png) [@Vlad\_Grigorescu2](https://community.zeek.org/u/Vlad_Grigorescu2)\
**Post date:** [October 3, 2012, 11:24pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/5 "2012-10-03T23:24:37Z")

</div>

Github has an interesting approach to how it generates the optional "Github pages" documentation. It uses a specific branch ("gh-pages") from your repository, to generate them.

Assuming I'm understanding this properly, one potential option would be to have a specific branch that the documentation up on the web server is generated from.

&nbsp;&nbsp;--Vlad

---

<div class="post-metadata">

**Author:** ![Slagell\_Adam\_J](https://avatars.discourse-cdn.com/v4/letter/s/e9c0ed/32.png) [@Slagell\_Adam\_J](https://community.zeek.org/u/Slagell_Adam_J)\
**Post date:** [October 3, 2012, 11:29pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/6 "2012-10-03T23:29:13Z")

</div>

+1

---

<div class="post-metadata">

**Author:** ![Daniel\_Thayer](https://avatars.discourse-cdn.com/v4/letter/d/8dc957/32.png) [@Daniel\_Thayer](https://community.zeek.org/u/Daniel_Thayer)\
**Post date:** [October 3, 2012, 11:31pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/7 "2012-10-03T23:31:22Z")

</div>

But don't we have the same issue when, for example, someone corrects  
an error in the documentation? (the correction won't appear in the  
docs until the next Bro release)

As a sort of workaround, whenever I look at the documentation on the  
web site, I choose the "Development" option under the "Documentation"  
tab, so that I always see the most recent version of the docs.

-Daniel

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex011/uploads/zeek/original/1X/f09d732bc2cc7c7cc7e35db67cf4e1d5233ce7a7.png) [@system](https://community.zeek.org/u/system)\
**Post date:** [May 6, 2022, 3:40pm UTC](https://community.zeek.org/t/bro-commits-git-bro-fastpath-redo-the-how-to-upgrade-faq-06d6277/2454/8 "2022-05-06T15:40:36Z")

</div>


