[Feedhenry-raincatcher] Documentation workflow change

[Paul Wright]

+1 Wojciech,

Not all users will upgrade whenever there is a release, so I'm hoping 
that there are version branches in the code repos as well as in the doc 
repo?

thanks,

Paul


On 10/23/2017 09:42 AM, Wojciech Trocki wrote:
> 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>
>
>
>
> _______________________________________________
> Feedhenry-raincatcher mailing list
> Feedhenry-raincatcher at redhat.com
> https://www.redhat.com/mailman/listinfo/feedhenry-raincatcher

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/feedhenry-raincatcher/attachments/20171023/e3a1f52c/attachment.htm>