Open Stack

Thanks Anne, I follow the steps and submit.


Colin McNamara, CCIE #18233
Director, Cloud Practice / Chief Cloud Architect
Nexus IS, Inc.
5200 Franklin Drive
Pleasanton, Ca, 94588
SNR: 925-226-3298
Mobile: 858-208-8105
colin.mcnamara at nexusis.com<mailto:colin.mcnamara at nexusis.com>
www.linkedin.com/colinmcnamara<http://www.linkedin.com/colinmcnamara>
www.colinmcnamara.com<http://www.colinmcnamara.com>
www.nexusis.com<http://www.nexusis.com>


On Aug 7, 2013, at 9:37 AM, "Anne Gentle" <annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>> wrote:

 I think it makes sense for you to publish todocs.openstack.org/trunk/training<http://docs.openstack.org/trunk/training> for now, while you gather contributors and get feedback.

To do so, make a patch like this one:https://review.openstack.org/#/c/36102/ where you edit these two files to make a new Jenkins build job:
modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml<https://review.openstack.org/#/c/36102/4/modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml>
modules/openstack_project/files/zuul/layout.yaml<https://review.openstack.org/#/c/36102/4/modules/openstack_project/files/zuul/layout.yaml>

Use an existing build to get the gist of it. That patch in particular is helpful in that it only publishes from the master branch to trunk.

The team in #openstack-infra can help if you get stuck.

Anne


On Mon, Aug 5, 2013 at 4:37 PM, McNamara, Colin <Colin.McNamara at nexusis.com<mailto:Colin.McNamara at nexusis.com>> wrote:
I think this question is directed to Anne, but I am not exactly sure.

I am looking for specific details on doc releases to trunk. From what I understand of the current state, docs are merged into openstack-manuals and then a release is tagged which deploys them to trunk.

Part of the workflow that we are trying to achieve with OpenStack-Training is to get general users (users that are not capable of a full git workflow) reviewing via web page and submitting bugs on content through embedded links. Originally there was a thought to deploy this to trunk and have users review and submit bugs via docs.openstack.org/trunk/openstack-training/blah/foo<http://docs.openstack.org/trunk/openstack-training/blah/foo>

My questions

1. is it appropriate to release OpenStack-Training beta content to trunk
2. if so, is there a way to increase the release cycle without negatively impacting the rest of docs
3. if it is not appropriate, is there a second area to add as a deployment target that can be used to show beta content, and get feedback from end users.


Regards,

Colin

If you would like to schedule a time to speak with me, please click here<https://my.timedriver.com/L89ZG> to see my calendar and pick a time that works for your schedule. The system will automatically send us both an outlook meeting invite.

Colin McNamara
Chief Cloud Architect, Director Cloud Practice
CCIE #18233, VCP, OpenStack ATC
Nexus IS, Inc.
5200 Franklin Drive
Pleasanton, Ca, 94588
SNR: 925-226-3298<tel:925-226-3298>
Mobile:  858-208-8105<tel:858-208-8105>
colin.mcnamara at nexusis.com<mailto:colin.mcnamara at nexusis.com>
<mailto:colin.mcnamara at nexusis.com>www.<http://www.linkedin.com/colinmcnamara>linkedin.com/colinmcnamara<http://www.linkedin.com/colinmcnamara>
<http://www.linkedin.com/colinmcnamara>www.colinmcnamara.com<http://www.colinmcnamara.com>
<http://www.colinmcnamara.com>www.nexusis.com<http://www.nexusis.com/>
<http://www.nexusis.com/>

<http://www.nexusis.com/news_events/events.asp?ID=230&cmd=view>












_______________________________________________
Openstack-docs mailing list
Openstack-docs at lists.openstack.org<mailto:Openstack-docs at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs




--
Anne Gentle
annegentle at justwriteclick.com<mailto:annegentle at justwriteclick.com>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20130808/9af51488/attachment.html>