[Feedhenry-raincatcher] Documentation workflow change

[Wojciech Trocki]

Hi

I have proposition to avoid pushing new, unreleased content to the website.
When creating PR's against master for the new functionalities we can
accidentally push them to the website.
We will need to stage our changes to prevent from that issue.
Proposition is to use version branch for example 1.1.0 for development and
then merge things to master.
Hot fixes may be done in the master directly.

*Why?*
We recently done some fixes around start that will be part of the 1.1.0
release and they already landed on the documentation.

Regards
-- 

WOJCIECH TROCKI

Red Hat Mobile <https://www.redhat.com/>

IM: wtrocki
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20171023/87c27912/attachment.htm>