On Thu, Aug 8, 2013 at 9:42 AM, Thierry Carrez <[email protected]>wrote:
> Anne Gentle wrote: > > Let me know your input on "continuous release with bug tracking" for the > > guides in the list above. If you have additional ideas, I'd love to hear > > them. I'm definitely pondering the integrated programs doc strategies > > and open to ideas. We've been discussing on openstack-docs but want to > > bring the discussion to a larger group so please reply to openstack-dev. > > I think it makes sense, especially in a world where the actual code you > run may or may not be aligned with a "release" anyway. It's better than > the previous situation, where guides were "released" a few weeks after > the "release", creating a lot of confusion. Better designate a set that > you release together with the release and go continuous for the others. > > Thanks for the input! I've looked at the analytics data and nearly 1/4th of visitors are going to the /trunk/ docs anyway, which change continuously now. So I think a smaller "release" set of docs is the way to go. Thanks, Anne > So +1 from me! > > -- > Thierry Carrez (ttx) > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
_______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
