Open Stack

but Document Team has so beautiful tables, and so convenient tools
<openstack-doc-tools>, it is a huge waste of resource if we manually write
it to release note in each project.

So I want to figure out what have happened to prevent Document Team
continuing previous workflow.

Thanks

On Sun, Apr 24, 2016 at 8:54 PM, Doug Hellmann <doug at doughellmann.com>
wrote:

> Excerpts from ZhiQiang Fan's message of 2016-04-24 08:00:10 +0800:
> > Hi Doc Team,
> >
> > I want to know the recent status of DocImpact tag, is it deprecated for
> > config option changes now? If it's true, then what the workflow for
> config
> > reference now, any hint or link?
> >
> > Previously, when a patch has impact to document, including config option
> > changes, I usually ask contributors to add a DocImpact, hence there will
> be
> > a bug track the document issue.
> >
> > Recently, a patch lands in Ceilometer which adds two new options, and
> > Ceilometer receives the auto created document bug. However, when I
> submit a
> > patch to openstack-manuals to fix it, I was told by a core that such
> change
> > is not needed any more, I searched latest merged patch in
> openstack-manuals
> > and found what he said is true, but still don't know why and what action
> I
> > should follow in Ceilometer/Aodh projects
> >
> > Thank you very much!
> >
> > ZhiQiang Fan
>
> I recommend at a minimum including a release note using reno in the
> patch changing any configuration options (adding, deprecating, changing
> defaults, etc.).
>
> Doug
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160424/b9232218/attachment.html>