<div dir="ltr"><div>This seems like a reasonable approach. +1<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div> <p style="font-weight:bold;margin:0;padding:0;font-size:14px;text-transform:uppercase;margin-bottom:0"><span>Dana</span> <span>Walker</span></p> <p style="font-weight:normal;font-size:10px;margin:0px 0px 4px;text-transform:uppercase"><span>Associate Software Engineer</span><span style="font-weight:normal;color:#aaa;margin:0"></span></p> <p style="font-weight:normal;margin:0;font-size:10px;color:#999"><a style="color:#0088ce;font-size:10px;margin:0;text-decoration:none;font-family:'overpass',sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span><br><br></span></a></p> <table border="0"><tbody><tr><td width="100px"><a href="https://red.ht/sig" target="_blank"> <img src="https://www.redhat.com/files/brand/email/sig-redhat.png" width="90" height="auto"></a> </td> </tr></tbody></table> </div></div></div></div> <br><div class="gmail_quote">On Thu, May 10, 2018 at 4:35 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>To have docs to align with the 4 phases of development we would have 4 release streams: 'nightly', 'beta', 'rc', and 'stable'. The url structure of the site would be something like:<br><br></div><a href="http://docs.pulpproject.org/en/%7Bx.y%7D/%7Bbeta" target="_blank">docs.pulpproject.org/en/{x.y}/<wbr>{beta</a> | nightly | rc}/{tag}/<br><br></div><div>The {beta | nightly | rc} is literally 'beta' if beta, 'nightly' if nightly, 'rc' if rc, and that part is left out if it's stable. Travis will know if {tag} has a 'b' in it then it's a beta publish, 'rc' for release candidate, and nothing for stable. I believe the nightly one could run via cron which would know it was run by cron (and therefore nightly).<br><br></div><div>{tag} would be the tag the release is tagged as e.g. 3.0.1b2, 3.1.3rc1, 3.0.0 (the ga).<br><br></div><div>The docs pusher in Travis will also ensure that leaving off the tag gives you the "latest" from that release stream so: <a href="http://docs.pulpproject.org/en/3.0/beta/" target="_blank">docs.pulpproject.org/en/3.0/<wbr>beta/</a> would give you the latest beta and <a href="http://docs.pulpproject.org/en/3.0/beta/3.0.0b3/" target="_blank">docs.pulpproject.org/en/3.0/<wbr>beta/3.0.0b3/</a> would give you 3.0.0 beta 3.<br><br></div><div>What about ^ approach?<br><br><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 10, 2018 at 2:31 PM, David Davis <span dir="ltr"><<a href="mailto:daviddavis@redhat.com" target="_blank">daviddavis@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">+1 to moving to Travis. This fits in with the push-to-PyPI stuff I think.<div><br></div><div>What does the 'beta' come from in the URL and what would the URLs for say a tag like 3.0.1 look like?</div></div><div class="gmail_extra"><span class="m_6804674809384957741HOEnZb"><font color="#888888"><br clear="all"><div><div class="m_6804674809384957741m_-2673787337172813531gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><br></div><div>David<br></div></div></div></div></div></div></div></div></font></span><div><div class="m_6804674809384957741h5"> <br><div class="gmail_quote">On Thu, May 10, 2018 at 8:29 AM, Dennis Kliban <span dir="ltr"><<a href="mailto:dkliban@redhat.com" target="_blank">dkliban@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Wed, May 9, 2018 at 1:37 PM, Brian Bouterse <span dir="ltr"><<a href="mailto:bbouters@redhat.com" target="_blank">bbouters@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div><div><div><div><div>We have several problems w/ the Pulp3 docs currently, in decreasing order of severity.<br><br></div>1. We don't have docs per beta, we only have nightly docs [0]. This is a problem because during the beta cycle, when we make a backwards incompatible change in core's documentation, e.g. merging RQ work, plugins can't point there users to the core documentation that pairs wit the version of core they tested against. For example if we had core docs for beta1, beta2, beta3 ... and pulp_ansible was tested against beta2 only, pulp_ansible users should be able to browse the core docs at version beta 2. We currently can't do that.<br><br></div>2. The docs builder is uber complicated[1][2], strangely overlays content[3] from pulp-ci, and is still shared with pulp2. This is a hold-over from the pulp2 docs builders and we never cleaned them up. This has cost us some time recently.<br></div><br>3. The docs builder is on Jenkins which is not community accessible.<br><br></div>I think we should address this soon, but we need some ideas/discussion first.<br><br></div>I've thought of two ideas: move to Read The Docs or Move to Travis. After looking into it, RTD is a non-starter AIUI because RTD won't be able to install and start all of the services necessary like Travis can.<br><br></div>So to move to Travis we could: Enable a conditional publish so that any tag which publishes a build to PyPI also publishes the built docs to <a href="http://docs.pulpproject.org/" target="_blank">docs.pulpproject.org/</a> Additionally, we could configure Travis to publish with each merged commit as well so we would have continuous docs.<br><br></div></div></blockquote><div><br></div></span><div>+1 <br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>I want to check in on the urls. We need Travis to be able to build it from the tag or branch info. Would the url be like:<br><br><a href="https://docs.pulpproject.org/en/3.0/beta/3/" target="_blank">https://docs.pulpproject.org/e<wbr>n/3.0/beta/3/</a><br><br></div><div>Or like:<br><br><a href="https://docs.pulpproject.org/en/3.0/beta/3.0.0b3/" target="_blank">https://docs.pulpproject.org/e<wbr>n/3.0/beta/3.0.0b3/</a><br></div><div><br></div></div></blockquote><div><br></div></span><div>I prefer the latter URL. <br></div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div></div><div>Feedback and ideas are welcome. After some discussion I can incorporate all the ideas into a Redmine ticket.<br></div></div></blockquote><div><br><br> </div></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><div dir="ltr"><div><br></div><div>-Brian<br></div><br><div><div><div><div><div><div><div><div><br>[0]: <a href="http://docs.pulpproject.org/en/3.0/nightly/" target="_blank">http://docs.pulpproject.org/en<wbr>/3.0/nightly/</a><br>[1]: <a href="https://github.com/pulp/pulp-ci/blob/master/ci/jjb/jobs/docs.yaml#L72-L180" target="_blank">https://github.com/pulp/pulp-c<wbr>i/blob/master/ci/jjb/jobs/docs<wbr>.yaml#L72-L180</a><br>[2]: <a href="https://github.com/pulp/pulp-ci/blob/master/ci/docs-builder.py" target="_blank">https://github.com/pulp/pulp-c<wbr>i/blob/master/ci/docs-builder.<wbr>py</a><br>[3]: <a href="https://github.com/pulp/pulp-ci/tree/master/ci/docs" target="_blank">https://github.com/pulp/pulp-c<wbr>i/tree/master/ci/docs</a><br></div></div></div></div></div></div></div></div></div> <br></span>______________________________<wbr>_________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br> <br></blockquote></div><br></div></div> <br>______________________________<wbr>_________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman<wbr>/listinfo/pulp-dev</a><br> <br></blockquote></div><br></div></div></div> </blockquote></div><br></div> </div></div><br>______________________________<wbr>_________________<br> Pulp-dev mailing list<br> <a href="mailto:Pulp-dev@redhat.com">Pulp-dev@redhat.com</a><br> <a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/<wbr>mailman/listinfo/pulp-dev</a><br> <br></blockquote></div><br></div>