<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jul 25, 2016 at 10:57 AM, Emmanuel Hugonnet <span dir="ltr"><<a href="mailto:ehugonne@redhat.com" target="_blank">ehugonne@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br>
Should we have a maintenance branch for the current stable version documentation (maybe on gitbook) and a living documentation (using github<br>
rendering) or just the living doc ?<br>
<span class=""><br></span><div class="HOEnZb"><div class="h5"><br></div></div></blockquote><div><br></div><div>I think it kind of depends on the framework we choose. If we stick with Confluence I think we could just have a WFLY document id and then once we release we make a copy of that version. The downside is if you do find a mistake you might have to change it in a few different spots.</div><div><br></div><div>Regardless of the framework it could be a bit tricky for micro-releases if master has already changed when making a snapshot.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">
</div></div><br>_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div>
</div></div>